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

Meshtastic 0400

!ea330400 · updates every minute

100% 4.19 V · 3 days 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 2 days Nov 12 to Nov 15 · 2 active days · 6 RF frames · 6 gateways

Nov 12 Nov 15

Most recent

Moka 417m Meshtastic a165 417m KO4HXD- 2 443m david79-uconsole 468m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Moka 1 RF — relayed — not attributable — 6h 57m ago
Meshtastic a165 1 RF — relayed — not attributable — 6h 57m ago
KO4HXD- 2 1 RF — relayed — not attributable — 7h 23m ago
david79-uconsole 1 RF — relayed — not attributable — 7h 48m 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.