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

Meshtastic d60c

!1e24d60c · updates every minute

94% 4.11 V · 6 h ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

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 5 days Oct 23 to Nov 15 · 5 active days · 17 RF frames · 4 gateways

Oct 23 Nov 15

Most recent

CommGuy Base - MeshAdv 367m IRE Base MQTT 679m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CommGuy Base - MeshAdv 2 RF — relayed — not attributable — 6h 7m ago
IRE Base MQTT 1 RF — relayed — not attributable — 11h 19m 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.