Different structure for rx_metadata for gateways from the packet broker

Archer
Fri, 04 Oct 2024 14:30:10 +0000
MQTT

Hello,

I would like to set up a monitoring view for the gateways. The data from rx_metadata is part of my considerations.
It is clear and understandable that there are differences between the data of gateways from the TTN network and from the Packet_Broker.
But why are there different data structures for data from gateways that come via the Packet_Broker?
These are two GWs from a TTI-ZTennant, to which I have access. Both gateways should be configured identically. Nevertheless, rx_metadata provides the following structure for Gateway1:
rx_metadata: {
0:
{
gateway_ids: object
gateway_id: ‘packetbroker’
packet_broker: {};
};
};

the deveui can be found in the packet_broker node, also the netid. (packet_broker.forwarder_net_id, packet_broker.forwarder_gateway_id, packet_broker.forwarder_gateway_eui)

Gateway 2 provides :

rx_metadata: array {
0:
{
gateway_ids:
{
gateway_id: ‘eui-xxxxxxxxxxxxxxxxxxxx’,
eui: ‘xxxxxxxxxxxxxxxxxx’
};
};
};

In this case, the packet_broker_node is missing - and therefore unfortunately also the netID. However, since the EUI’s are only unique within a NetID - is there a way to find the NetID in this structure as well?

Steffen

12 posts - 4 participants