K4EX_MQTT2 eparsonline.org

!02ee456c · updates every minute

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

Heard once, on Sep 27 first heard Sep 27 · 1 active day · 1 RF frame · 1 gateway

Sep 27 Nov 15

Most recent

!9ea03ba8 1120m

Who heard it

Last 24 hours.

This node is a gateway. It has received 1 node(s) itself (1 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
!9ea03ba8 heard by this node	1 RF	—	relayed — not attributable	—	18h 40m 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.