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

Meshtastic 0690

!d4930690 · updates every minute

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; the firmware default. — 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 13 days Nov 2 to Nov 15 · 13 active days · 87 RF frames · 5 gateways

Nov 2 Nov 15

Most recent

JT HeltecV4 (MQTT) 55m Meshtastic 32804 1135m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic 32804 47 RF — 7.5 dB … 5.8 — 18h 55m ago
JT HeltecV4 (MQTT) 1 RF — relayed — not attributable — 55 min 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.