class_b=true flag appearing in downlinks for Class-A-only device

Viewed 7

I need help stopping ChirpStack from setting the class_b flag to true in downlinks to my device.

ChirpStack version: [4.11.1]

Device profile: Class A only (Class B disabled in profile)

Device firmware: Class A only

Gateway: RAK7289CV2-8CH [v2.2.16], Class B disabled

Could this be caused by the device advertising Class B during join? If so, can ChirpStack be configured to ignore the device's Class B capability and enforce the device profile instead?

1 Answers

This is not a bug but the class_b bit is shared with the f_pending flag. On uplink you should look at the class_b flag, on downlink at the f_pending.

There is nothing to worry about, ChirpStack is indicating to your device that there is more data in the queue.