Hello, I have wrongly enabled the class C capability when I declared my device (OTAA). As a result, any attempt to downlink a message fails. I have unchecked the Class C setting through the TTN console and by the CLI, but downlink messages are still sent by TTN as if it was a class C device. What can I do to properly downlink a message to my device ?
Many thanks for your answer.
You need to restart the device to reset the state in TTN. (Or try to use ttncli command line tool to manipulate active configuration if possible)
Thanks for your answer. My device is difficult to reach (and to reset), so the reset is not really an option. What sort of CLI command should I use ?
Many thanks.
It is ages since I last used the cli, may-be @descartes can help out.
If you are in a hurry. There are commands to list the current setting and there should be a configuration tree and an operational tree, you need to set a value in the second one.
I used the CLI to send a downlink command but it doesn’t change anything, TTN handles it as a class C device.So, I have no solution so far.
That is to be expected because it uses the same back-end and logic the web interface uses. You need to change the device state to resolve this.
Have you looked at the device state information the cli can provide you with? And the potential state setting that could resolve the issue?
To save you some time digging in the documentation this time, try:
ttn-lw-cli device set <appname> <device> --mac-state.device-class "CLASS_A"
Thank you so much Jac, it works perfectly. Since I have other Class A devices wrongly declared as Class C, do you think it’s worth applying this command to all of them ? I mean, could they be impacted in one way or another if they are handled as Class C devices, even if I don’t need to send any command ? Again many thanks.
Yes
You might not but the network will need to be able to send control (MAC) packets to the device so please update settings for all your wrongly configured devices.
I agree it’s worthwhile (and absolutely necessary if one wants to avoid mysterious problems cropping up long after one has forgotten about this discussion), but I wonder whether or not the (Things) network (server) will send MAC commands via class C downlinks. It’s forbidden under LoRaWAN 1.0.4, and although it’s (implicitly) permitted under earlier versions, it’s problematic (hence the restriction in LW 1.0.4).
Note: If by “control (MAC) packets” something else was meant, my apologies for clouding the issue. Otherwise, it seemed useful mentioning this minor caveat for completeness/educational purposes.