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

FLMesh Seeed X1(1)

!80d086e8 · firmware 2.8.2.34c9457 · reports 3 node(s) online locally · updates every minute

88% 4.10 V · 16 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.

History

Silent for 16d 13h Sep 23 to Oct 29 · 22 active days · 1555 RF frames · 26 gateways

Sep 23 Nov 15

Most recent

LWS ARC Shaun Gateway 📵 23860m LWS ARC Shaun BASE 📵 23860m LWS MBL 4 HT TKR V2(2) 23948m FLMesh HT T190 (1) no pin 25207m 👽 LWS ARC Area 51 Gateway 35989m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
LWS ARC Shaun Gateway 📵 10 RF — 6.2 dB … -16.2 — 16d 13h ago
LWS ARC Shaun BASE 📵 68 RF 0 7.2 dB … 0.5 5 16d 13h ago
LWS MBL 4 HT TKR V2(2) 542 RF 0 7.8 dB … -17.5 3 16d 15h ago
FLMesh HT T190 (1) 4 RF — 7.2 dB … 5.8 — 17d 12h ago
👽 LWS ARC Area 51 Gateway 1 RF — -6.5 dB — 24d 23h ago
FLMesh MBL 2 RAK 1W(1) both ways 14 RF 0 10.8 dB … 4.5 5 26d 13h 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.