Meshtastic bf34

!3c65e4e7 · 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

Silent for 6d 15h Oct 23 to Nov 8 · 3 active days · 4 RF frames · 2 gateways

Oct 23 Nov 15

Most recent

Beanfield 🐊 flme.sh 9586m

Who heard it

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

Peer	Frames	Hops	SNR (direct only)	Hop budget left	Last heard
Beanfield 🐊 flme.sh	1 RF	—	-10.2 dB	—	6d 15h 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.