We encountered an issue with a LoRaWAN device during provisioning and would like to understand the behavior.
Initially, a sensor was registered in ChirpStack with an incorrect DevEUI, which resulted in the error:
Invalid MIC, make sure keys are correct.
Later, the device entry was corrected by adding a new device with the correct DevEUI and AppKey, and the old device entry (with the wrong DevEUI) was deleted from ChirpStack.
However, even after ~10 hours, the device has not joined successfully. When checking the gateway logs and ChirpStack logs, we still see JoinRequest messages coming from the old DevEUI (the one that was deleted).
Some additional details:
-
The physical device is the same sensor, not a different one.
-
Only the DevEUI in ChirpStack was corrected.
-
The AppKey remained the same.
-
The old device entry was removed after creating the new one.
Our question is:
Why would ChirpStack/gateways still receive JoinRequest messages with the old DevEUI, even though the device entry was deleted and a new device with the correct DevEUI was created?
Could this indicate:
-
the device firmware still transmitting the old DevEUI,
-
some caching behavior,
-
or another possible cause?
Any insights on how to debug or resolve this would be greatly appreciated.
Thank you.
