- Newest
- Most votes
- Most comments
Based on the information provided, there are a few potential issues that could be causing the problems you're experiencing with your Wio-E5 mini LoRaWAN device:
-
LoRaWAN version mismatch: The fact that you're able to create the device with OTAA v1.0.x but not with v1.1 suggests there might be a version compatibility issue. Ensure that your Wio-E5 mini firmware supports LoRaWAN v1.1 if you're trying to use that version.
-
Credential mismatch: Double-check that the device credentials (DevEUI, AppEUI/JoinEUI, and AppKey) configured in AWS IoT Core exactly match what is programmed on your Wio-E5 mini. Even a small discrepancy can prevent successful activation.
-
Activation process: For OTAA devices, remember that they need to go through an activation or join procedure before they can send uplink data. Make sure your device is properly attempting to join the network.
-
NwkKey issue: In LoRaWAN v1.1, there are two root keys - AppKey and NwkKey. If you're using v1.1, ensure both keys are correctly configured. The NwkKey is not used in v1.0.x, which could explain why you're able to create the device with that version.
-
Profile configuration: Verify that your device profile and service profile are correctly set up and associated with your device. Incorrect profile settings can prevent proper communication.
-
Gateway configuration: Ensure your LoRaWAN gateway is properly connected to AWS IoT Core and is able to forward the join requests and uplink messages from your device.
To troubleshoot further:
- Enable IoT wireless logging and check CloudWatch logs for more detailed error messages.
- Use the Network Analyzer feature in AWS IoT Core for LoRaWAN to confirm if uplinks are reaching AWS.
- If possible, enable debug logging on your gateway to see detailed join and uplink message information.
If the issue persists, you may need to review your device's configuration, ensure it's in the correct mode (OTAA), and potentially try a factory reset of the device before reconfiguring it.
Sources
"Last Uplink Received At" field is empty | AWS re:Post
Add your wireless device to AWS IoT Core for LoRaWAN - AWS IoT Wireless
What is the best approach for bulk-provisioning LoRaWAN devices in IoT Core. | AWS re:Post
Hi,
Thank you for the suggestions! Do you have more specific advice on the error message I'm receiving? How would profile and gateway configuration cause the error message?
answered a year ago

Hi,
Thank you for the suggestions! Do you have more specific advice on the error message I'm receiving? How would profile and gateway configuration cause the error message?