May I ask a question? If multiple terminals are used for networking, NS will be assigned to two terminals with the same devaddr. At this point, the nodes are successfully networked and reported, and the reported information can be seen in the gateway ->LIVE LORAWAN Frames of the chirp stack. However, in Applications ->device, the reported information cannot be seen in the VIEW DATA and LORAWAN Frames. How can I eliminate this phenomenon?
Why does NS give two devices the same device address?
It will give a unique device address for each device.
Technically this is possible however. The DevEUI address-space is a lot bigger than the DevAddr space (and this also varies by NetID).
ChirpStack keeps a DevAddr to DevEUI mapping such that when it receives an uplink, it could validate it against the session-keys of multiple DevEUIs. Based on the MIC validation, it will find out which is the correct DevEUI.
However, in Applications ->device, the reported information cannot be seen in the VIEW DATA and LORAWAN Frames. How can I eliminate this phenomenon?
Are the devices using OTAA or ABP (I suspect ABP). In case of ABP this can be an issue with the session-keys.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.