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

FloridaMesh HT TKR V2(1)

!9a05751e · updates every minute

66% 3.86 V · 9 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.

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; 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 15 days Sep 17 to Nov 14 · 15 active days · 170 RF frames · 7 gateways

Sep 17 Nov 15

Most recent

FLMesh HT T190 (1) no pin 679m LWS ARC Shaun BASE 📵 15291m LWS ARC Shaun Gateway 📵 15292m

Who heard it

Last 24 hours, plus 2 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FLMesh HT T190 (1) 3 RF — 6.5 dB … 5.5 — 11h 19m ago
LWS ARC Shaun BASE 📵 1 RF — 5.5 dB — 10d 14h ago
LWS ARC Shaun Gateway 📵 1 RF — 6.2 dB — 10d 14h 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.