- Newest
- Most votes
- Most comments
Can you access the Basic Station logs (I haven't used a Multitech before)? If so, please share, because that will likely give clear insight into what the problem is.
Are you working in the same account and AWS region? If not, do you have other working gateways in this account and region? If not, have you created the IoTWirelessGatewayCertManagerRole?
new AU915 certs were made and placed on the gateway
Looking in the Multitech manual, you would have updated the Gateway Cert and Gateway Key of the Basic Station Configuration with the new CUPS certificate and key. If this is a different account or AWS region, you would also need to update the URI setting. Normally you would use the CUPS URI and let Basic Station get the LNS settings. If so, I would think Credentials should be set to CUPS.
https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-onboard-gateway-add.html
we know devices connect to the gateway
What are you observing to make this statement? I'm curious because devices don't connect to gateways.
Hello! AWS IoT Core for LoRaWAN customers can use US902-928, EU863-870, AS923-1 or AU915 frequency bands to connect LoRaWAN gateways and devices that are physically present in countries that support the frequency ranges and characteristics of these respective bands. US902-928 and EU863-870 bands are commonly used in the North America and European regions respectively. AS923-1 is commonly used in Australia, New Zealand, Japan, Singapore, and Taiwan among other countries. AU915 is commonly used in Argentina, Chile, and other South American countries. Please go through the below mentioned linked for more information: [+] https://aws.amazon.com/iot-core/lorawan/
Relevant content
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
Thank you for the insight, I will work on gathering the Basic Station Logs but due to the nature of MultiTech it will take some time.
I have created it. I will change the region to Asia Pacific (Sydney) and see if that resolves the issue.
As for the the devices connecting to the gateway I should have been more clear. The devices are not AWS devices, they are PCBs connecting to the MultiTech gateway, their EUI's are appearing in the gateway logs, so I know from MultiTech to the PCBs is functional, and that cellular and GPS are also functioning.