TLDR: I think the ability to toggle an OTAA end device into a development mode, or reset devNonce would be very beneficial.
I’m developing an end node using the Microchip WLR089U0, and am currently using the devboard. I’m using OTAA and have successfully connected and been able to transmit data.
However, each time I modify my firmware I need to rejoin to the application. This then results in devNonce “is already in use” and “is too small” errors. I have occasionally been able to get around this by changing the LoRaWAN version from MAC v1.0.4 back to 1.0.3, but that doesn’t always work. The LoRaWAN stack supplied by Microchip is v1.0.4 compatible.
In my searching I’ve come across a few recommended solutions for this, however I think that I’m missing information.
- Discussion around disabling the frame counter Disable Frame Counter Checks in V3
- Nonce attributes End Device APIs | The Things Stack for LoRaWAN
- CLI reference Command-line Interface | The Things Stack for LoRaWAN
Is it possible to access the console for the au1 community console? I know what I need to change, but I just can’t figure out how to do it. Is this something that could be included as an attribute option?
Some additional links:
- Any experience with WLR089? Having some trouble - #8 by cslorabox
- OTAA shows "Activation DevNonce not valid: already used" - #2 by htdvisser
Currently trying to find where to ‘manually’ set the devNonce value. A search through the demo mote example project for nonce gives no indication of where it’s set. There are 3 references. 2 error messages and an output variable within secure application layer code. The comment is “If the output is encrypted, a 32 byte random nonce generated by the device is returned here. If output encryption is not used, this can be NULL.”
The search continues.