You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only point where the Application server reports the DevAddr is in the JoinEvent, and afterwards its completely unreported. This is a shame, because its very valueable information. The Gateway API basically only communicates the DevAddr and no DevEUI.
I would like to see either the DevAddr on the Gateway part, or the DevEUI on the appserver Integration API.
The added benefit of having the DevAddr on the gateway, is that if a join request is accepted, the address is already known. Now I have to wait for the first data to arrive at the station in order to pick it up from the Join event of the appserver.
The text was updated successfully, but these errors were encountered:
The only point where the Application server reports the DevAddr is in the JoinEvent, and afterwards its completely unreported. This is a shame, because its very valueable information. The Gateway API basically only communicates the DevAddr and no DevEUI.
chirpstack-api/protobuf/as/integration/integration.proto
Lines 103 to 104 in 4b2fccc
https://github.com/brocaar/chirpstack-api/blob/master/protobuf/nc/nc.proto
I would like to see either the DevAddr on the Gateway part, or the DevEUI on the appserver Integration API.
The added benefit of having the DevAddr on the gateway, is that if a join request is accepted, the address is already known. Now I have to wait for the first data to arrive at the station in order to pick it up from the Join event of the appserver.
The text was updated successfully, but these errors were encountered: