- Newest
- Most votes
- Most comments
Hi JT. Please take a look at our AWS IoT Core for LoRaWAN workshop, particularly the new downlink and multicast downlink sections as they may help you: https://catalog.us-east-1.prod.workshops.aws/workshops/b95a6659-bd4f-4567-8307-bddb43a608c4/en-US/470-downlink
For debugging the unicast downlink, in addition to the CloudWatch logs, have you used the Network Analyzer? https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-network-analyzer-overview.html
Furthermore, if you have access to the Basics Station logs on your gateway, you can see the uplink and downlink messages there: https://doc.sm.tc/station/tcproto.html#
Finally, in regards to multicast downlink, AWS IoT Core for LoRaWAN implements the LoRaWAN Remote Multicast Setup Specification: https://lora-alliance.org/resource_hub/lorawan-remote-multicast-setup-specification-v1-0-0/ . Your device must implement this too for it to be able to participate in multicast sessions with AWS IoT Core for LoRaWAN. From https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-multicast-status.html :
Package attempting
After your devices have been associated with the multicast group, the device status is Package attempting. This status indicates that AWS IoT Core for LoRaWAN has not yet confirmed whether the device supports multicast setup and operation.
Relevant content
- asked 3 years ago
- asked 2 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
Thanks
I have reached out to our vendor to see if that multicast method is supported. I suspect its not. That will answer why it doesn't work.
I have enabled extra loging now via the CLI for cloud watch - Thank you for the link.
Is there anyway to retry a failed delivery ? Some times some network issue might mean the command needs to be sent again.
JT