I have the problem that unconfirmed uplink messages can be seen in the Gateway Live Frames, where the device address cannot be found by entering it in the network server’s search field. Why can’t I assign the devices? Are these messages from devices that are not registered on the server? Shouldn’t I only see join requests that are not accepted? Or could it be that the device address is not up to date? Please help.
This means they are not registered on your NS. Since gateways are simply “dumb packet forwarders” if you are in a busy area you will get plenty of packets from foreign devices that your gateway will pass to the NS, where the NS then determines whether they are meant for you server. You can see these packets in the Gateway Live Frames as you are seeing.
Not sure what you mean here, but if they are not your devices you will not know the application key to be able to assign them. If they are your devices you need to create an application and then add the devices to them.
No because if the device joined with another NS, it will not be sending join requests but uplink packets which your gateway will receive and forward blindly.
1 Like
Why do the incoming uplinks already have a device address assigned, even though they are not registered anywhere and therefore cannot join? The device address is only assigned during the join process, isn’t it?
Ah I thought you were referring to the devEUI before but it’s the same idea. Once a device has done the join-process, it begins broadcasting the devAddr instead of the devEUI.
If there are devices nearby that are onboarded to someone else’s LNS, your gateway will still forward the messages to your LNS, and the packet will display the devAddr assigned to it by the other LNS. The server will then reject the packet as it’s not a registered device on your server but the packet is still visible in the gateway logs.
1 Like
This topic was automatically closed after 90 days. New replies are no longer allowed.