!bd503074

!bd503074 · updates every minute

powered 4.22 V · 9 days ago — this node reports itself externally powered rather than running on a battery.

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 Nov 5 first heard Nov 5 · 1 active day · 2 RF frames · 1 gateway

Nov 5 Nov 15

Most recent

Compatible🦊 13897m

Who heard it

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

Peer	Frames	Hops	SNR (direct only)	Hop budget left	Last heard
Compatible🦊	2 RF	—	-18.5 dB … -19.8	—	9d 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.