PacketTrends Mesh a public map of nodes that asked to be on one map stations

Chief e883

!f277a8c1 · updates every minute

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; some frames went out with a smaller budget, as low as 2 — Meshtastic spends fewer hops on a reply than on a broadcast, so this is the reply economy rather than a second setting; above the default of 3. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Heard on 4 days Nov 12 to Nov 15 · 4 active days · 70 RF frames · 1 gateway

Nov 12 Nov 15

Most recent

Chief_YARD 391m

Who heard it

Last 24 hours.

This node is a gateway. It has received 1 node(s) itself (4 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Chief_YARD both ways 75 RF 0 7.2 dB … -1.8 2 6h 31m ago
Reading the hop budget. Every Meshtastic frame carries a hop limit that each relay decrements. A reception showing 0 left is one that arrived with nothing to spare — one more relay in the path and it would not have arrived at all. That is the closest this data comes to explaining a loss, and it is still not a loss: a frame that was dropped is exactly the one that never reached a gateway to be counted here.