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

KM Mesh Base

!a0cb01c4 · firmware 2.7.26.54e0d8d · reports 1 node(s) online locally · updates every minute

History

Silent for 39d 20h Sep 21 to Oct 6 · 6 active days · 13 RF frames · 1 gateway

Sep 21 Nov 15

Most recent

!18512fd2 510m !e4a0f4f0 no pin 785m YNWA_Shankly 948m KM Portable Mesh no pin 41509m

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 (3 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
KM Portable Mesh heard by this node 8 RF — 7.5 dB … 6.0 — 28d 19h ago
!18512fd2 heard by this node 1 RF — relayed — not attributable — 8h 30m ago
!e4a0f4f0 heard by this node 1 RF — relayed — not attributable — 13h 5m ago
YNWA_Shankly heard by this node 1 RF — relayed — not attributable — 15h 48m 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.