Open jpmeijers opened 9 months ago
Q1: Where are the field names for the Helium hotspot's metadata defined? Is it in https://github.com/helium/helium-packet-router/blob/b06b2758f443c04079e74daf809a156f281162bd/src/protocols/gwmp/hpr_gwmp_worker.erl#L240-L244 ?
Those are the Meta fields that will always exist. https://github.com/helium/helium-packet-router/blob/b06b2758f443c04079e74daf809a156f281162bd/src/protocols/gwmp/hpr_gwmp_worker.erl#L251-L255 These fields will be added if the gateways has a location.
Q2: "gatewayId": "2eccbd518b5ad386",, from the sourcecode above this looks like it's the Base58 of the Helium Gateway ID (aka PubKey). But I can't reproduce this. Can anyone help/explain please?
There are 2 gateway ids.
meta.gateway_id
, which is the b58 pubkey if the gateway.gatewayId
, which is the MAC address of the gateway.
The MAC cannot be reversed into the b58, which is why it's also provided.
Request 1: Can we add a field in the metadata that explicitly states this gateway is part of Helium? Something like "network": "helium_iot",
Thanks for the PR 👍
Request 2: Can we populate the proper rxInfo->location object with the Hotspot's coordinates, so we can rely on standard ChirpStack endpoints to consume the location?
rxInfo->location
is populated by the stat
object in a PUSH_DATA frame.
The Packet Routers cannot fill out a stat
object, and the location information are the only optional fields in the object, so it was removed. https://github.com/helium/helium-packet-router/pull/271
This is both a question and a feature request.
In ChirpStack I see the following Up Event:
Under
rxInfo
, the second object is a Helium IoT Hotspot, while the first one is directly connected to Chirpstack.Under
metadata
for the Helium hotspot, there are a couple of fields, all pretty self explanatory.Questions:
"gatewayId": "2eccbd518b5ad386",
, from the sourcecode above this looks like it's the Base58 of the Helium Gateway ID (aka PubKey). But I can't reproduce this. Can anyone help/explain please?Requests:
"network": "helium_iot",
rxInfo->location
object with the Hotspot's coordinates, so we can rely on standard ChirpStack endpoints to consume the location?