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

FamiLAB Longwood

!087ba05c · firmware 2.7.15.567b8ea · reports 2 node(s) online locally · updates every minute

powered 5.11 V · 72 min ago — this node reports itself externally powered rather than running on a battery.

History

Silent for 47d 11h Sep 20 to Sep 28 · 4 active days · 9 RF frames · 1 gateway

Sep 20 Nov 15

Most recent

Meshtastic 9a93 48m Meshtastic 7a78 126m itsaMeshtag no pin 387m LWS ARC Altamonte Gateway 14087m

Who heard it

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

This node is a gateway. It has received 3 node(s) itself (41 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic 9a93 heard by this node 200 RF 0 8.0 dB … -20.2 3 48 min ago
Meshtastic 7a78 heard by this node 127 RF — 7.5 dB … -14.8 — 2h 6m ago
itsaMeshtag heard by this node 54 RF 0 7.2 dB … 5.5 7 6h 27m ago
LWS ARC Altamonte Gateway heard by this node 1 RF — -16.2 dB — 9d 18h 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.