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

FL Mesh HT V4R8 Kit(1)

!3934deef · updates every minute

0% 2.99 V · 15 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.

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

Silent for 15d 0h Oct 27 to Oct 31 · 4 active days · 323 RF frames · 7 gateways

Oct 27 Nov 15

Most recent

FLMesh HT T190 (1) no pin 21616m LWS ARC Shaun Gateway 📵 21658m LWS ARC Shaun BASE 📵 21758m LWS ARC HT T114 (3) no pin 22250m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FLMesh HT T190 (1) 299 RF 0 7.8 dB … -19.0 4 15d 0h ago
LWS ARC Shaun Gateway 📵 7 RF 0 6.8 dB … -4.2 5 15d 0h ago
LWS ARC Shaun BASE 📵 8 RF 0 6.2 dB … -6.5 5 15d 2h ago
LWS ARC HT T114 (3) 3 RF — 7.2 dB … 6.2 — 15d 10h 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.