- Sylvain Prost (Unlicensed) TODO
- https://thethingsindustries.atlassian.net/projects/TTS/queues/custom/1/TTS-85
If the device wakes up from deep-sleep every 15 minutes does a join, it is indeed not strange that this happens. Every join must use a unique random 2-byte nonce, so if a device joins very often, it will eventually become more and more difficult to randomly select a nonce that has not been used before.
...
In the meantime, you could try changing the AppKey in the console, and then change it back to the old value. This will clear the list of used nonces, and should allow your device to join again.
First of all, this is not how LoRaWAN devices should operate.
Second, I see about 93 used app and dev nonces now. Is this consistent with how many there should be based on the retry count? I'm looking at device 00000817.
Are you wiping the whole end device state? I.e. could the device be refusing the join accept based on a used app nonce?
Also, do you see the gateway emitting the join accept in the first place?
Finally, can you confirm that RX2 DR is 5 (SF12) and Eric, can you confirm that this is 5 on this private network as well? Otherwise the success rate may be related to the RX1/RX2 decision
Problem
Device send a join request but it is never accepted or randomly fails.
Solution
Panel
- Downlink issue
- Overused App nonce. Those are unique identifiers used during the join request and if the the device perform join request too often, it will eventually run out. If your device join the network with a high frequency, you need to review your device join policy as it is not LoRaWAN compliant. For example should the device be in deep sleep during between each message it can do the join request once and store the network keys ("mac save" for RN2438 module).
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...