COLLISION_BEACON When sending downlink to Class A device

Viewed 16
gateways chirpstack

I was sending downlinks to a Class A device. Sometimes I get errors "COLLISION_BEACON".

My gateway is a RAK7289
Chirpstack version is v4.14.1
In my device profile Class B & C are disabled.

The error is described as "Rejected because there was already a beacon planned in requested timeframe." But why would this conflict? This is only relevant for Class B devices, right?

1 Answers

Even if your devices do not use Class-B, the gateways might still send Class-B beacons (which are sent every 128 seconds). If you would like to avoid COLLISION_BEACON errors, you should turn off the sending of Class-B beacons in your gateway configuration.

Orne Brocaar367
Related
COLLISION_BEACON When sending downlink to Class A device
1 answers
Questions on Multi-Region ChirpStack v4 Deployment — AS923-1 and AS923-3 Configuration
1 answers
Femto gateway to Chirpstack support
2 answers
IWM-LR5 Device not sending any info
2 answers
How to modify the algorithm or strategy for selecting the gateway in ChirpStack
1 answers
ChirpStack Node Limit
2 answers