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

Unauthorized Device

!6e3c72a1 · firmware 2.8.2.4c89b69 · reports 2 node(s) online locally · updates every minute

powered 4.29 V · 29 h ago — this node reports itself externally powered rather than running on a battery.

History

Silent for 1d 5h Sep 15 to Nov 14 · 27 active days · 78 RF frames · 5 gateways

Sep 15 Nov 15

Most recent

MUC4R0-ORL 🦉 1146m SolarBasedBcoN 1153m MobileBcoN 1189m SLT-2798 7986m

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 (20 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
MUC4R0-ORL 🦉 heard by this node 461 RF — -5.0 dB … -21.0 — 19h 6m ago
SolarBasedBcoN heard by this node 1321 RF 0 8.0 dB … 3.8 4 19h 13m ago
MobileBcoN heard by this node 814 RF 0–1 8.0 dB … -2.5 3 19h 49m ago
SLT-2798 heard by this node 1 RF — -7.0 dB — 5d 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.