I wonder if there is a plan to add more fields inside the Mesh Relay metadata.
I can see there is relay_id, which helps to identify the uplink source gateway, but I also need RSSI, SNR and Lat, long.
It is required for the field tester device > I have RAK10701
I am using a custom python script running as service on CS server side acting as a loop-back. I can adjust it to extract whatever info I need from the uplink payload before scheduling the down-link back to RAK10701 Lat, Long of the source Relay GW I can try to get myself via mqtt or API from the CS server, but I am still missing radio parameters…
Upvote on the Lat, long of the relay GW. Would be very useful for range calculation to the nodes when my relay gateways are moving. Right now I’m thinking I’ll need to add a tracker node to each to know where it is, which is not ideal considering the gateway has it’s own GPS.
Please not that adding the lat / long to each uplink would add additional overhead. You already have the RSSI and SNR as the Border Gateway will expose the RSSI and SNR as it was received by the Relay Gateway. That way, ADR can also still work.
The lat / long could be something to add to the heartbeat payloads in the future.
@brocaar if I understood correctly below statement
Border Gateway will expose the RSSI and SNR as it was received by the Relay Gateway.
RSSI and SNR I see in rx_info on the Border Gateway uplinks is actually from Relay Gateway? How to differentiate RSSI and SNR for Border gateway itself from Relay Gateway?
Regarding Lat, Long > in my case I can think about a workaround, either to have a reference data (something like a file with all GWs and coordinates which I will load into my script), or to take it from the CS server via API. So it is not a problem.
Correct, else ADR would never work. The Relay > Border signal RSSI / SNR is currently not available, but it would be possible to make some modifications to expose this in the meta-data (like the hop count).
Ok great. So the RSSI and SNR I see on border gateway (in my snapshot) is actually the values from the Node-to-RelayGateway and not for RelayGateway-to-Border.
In this case this topic can be closed. For Lat-Long of the RelayGateway I can manage myself inside my script.
