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?
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.
Not from the top of my head. My RAK gateway is currently running the Gateway OS for testing.
RAK7289 need to be upgraded to the latest version then there will be option to disable it.
Thanks Orne, do you happen to know where to disable this in the RAK7289? Can you do this in the Web UI of the gateway?
I do not have one here and need to send instruction to someone to fix this remotely.
