On TTN, with an application set as LoRaWAN Specification 1.0.2, end device as options
Resets join nonces:Enabled
Reset used DevNonces
but it seems that for Spec 1.0.2 this is irrelant, but it is for 1.0.4/1.1.0.
Page 56:
At each OTAA Join, the frame counter is reset on the end-device AND on the server side.
Page 57, section 4.5.5, resumed:
version 1.0.4 : counter DevNonce: end-device in OTAA must save it in a non-volatile memory,
or the Join-Request will not be accepted if the end-device is reset
Questions:
- It is not needed to use a non-volatile memory on End Device when application is set as
LoRaWAN Specification 1.0.2, correct ? - Set End device ‘Resets join nonces:Enabled’ or ‘use Reset used DevNonces’ is not necessary when application is set as LoRaWAN Specification 1.0.2, correct ?
- Set End device ‘Resets join nonces:Enabled’ or ‘use Reset used DevNonces’ has no
effect when application is set as LoRaWAN Specification 1.0.2, correct ?
Thanks
