It'sa me, MeshWio

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

History

Silent for 32d 12h Sep 16 to Oct 13 · 6 active days · 15 RF frames · 3 gateways

Sep 16 Nov 15

Most recent

BURGER no pin 1088m Southport ☀ Node 1096m NF6P Shack 31236m

Who heard it

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

This node is a gateway. It has received 2 node(s) itself (2 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
NF6P Shack heard by this node	6 RF	—	-15.8 dB … -18.8	—	21d 16h ago
BURGER heard by this node	1 RF	—	relayed — not attributable	—	18h 8m ago
Southport ☀ Node heard by this node	1 RF	—	relayed — not attributable	—	18h 16m 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.