- Newest
- Most votes
- Most comments
Good morning Greg_B, hope you are well.
First thanks for your attention.
In the examples that I uploaded I did triggers from different devices really. However, a device that is communicating now will not communicate at any time. The connection is unstable.
I've been trying to figure out why for a few months now. Initially I thought it was a frequency problem, but now I see in the log that all triggers are captured by the gateway and relayed to AWS.
Missing messages are not displayed in the NetWork analyzer.
Is there any way where I can see the websocket server log?
Hi. Are the gateway logs showing two different devices or two different sessions of the same device? I'm asking because the success and failure examples have different DevAddr.
You mentioned Network Analyzer: have you confirmed that the missing messages fail to appear in Network Analyzer? I'm wondering if they reach IoT Core (and would therefore appear in Network Analyzer if your NA configuration was correct), but maybe there's a problem with the configuration of the Destination for the misbehaving device (and hence no message seen in the MQTT test client).
Relevant content
- asked 8 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
The available logging is Network Analyzer and CloudWatch: https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-logging-monitoring.html. There is no way to see logs of WS discarded uplinks. Based on the screenshots you shared, there's no reason why they would be discarded, and hence they should be seen in Network Analyzer. Can you create a support case? Then you can supply your device and gateway IDs in the case, and it can be investigated more deeply.