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?