1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi. 1.0.4 is not yet fully supported, but in some cases a 1.0.4 device should still work. For example, I have used a 1.0.4/RP2-1.0.1 AU915 Class A device without issue, but it couldn't operate in Class B because 1.0.4 has breaking changes in the beacon format.
Has your device successfully joined, but then the uplinks fail to get through? If so, what do the gateway logs show about the uplinks? Is your device class A? What RF region?
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 10 Monaten
The device is Class A, US915.
My gateway shows it is connected, but my network analyzer shows no messages passing.
I have a second gateway set up with a local LNS to monitor the LoRaWAN frames. I see the initial join request and then periodic uplink packets. This tells me the device has joined because if not it would continue to send join requests.
The device details page says no uplink has been received from the device.
Can you access the Basic Station logs on the gateway? If so, you should see something like this (if the logging level is set to verbose):
This is the uplink (and indicated by updf) being received by the gateway:
And then immediately following you should see the updf being sent over websockets (WS) to AWS.