Meshtastic bd34

!ad1dbd34 · firmware 2.7.26.54e0d8d · reports 6 node(s) online locally · updates every minute

History

Silent for 6d 12h Nov 1 to Nov 8 · 3 active days · 5 RF frames · 4 gateways

Nov 1 Nov 15

Most recent

ArgusNavis 11333m K4FSG TallBoi discord.gg/floridamesh 14683m KQ4SNEPiHat 15150m SutMesh Base KQ4SNE 15260m S5 TREKKER DELTA 21339m

Who heard it

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

Peer	Frames	Hops	SNR (direct only)	Hop budget left	Last heard
ArgusNavis heard by this node	9 RF	—	-18.8 dB … -20.8	—	7d 20h ago
K4FSG TallBoi discord.gg/floridamesh heard by this node	5 RF	—	2.0 dB … -14.2	—	10d 4h ago
KQ4SNEPiHat heard by this node	8 RF	—	-11.2 dB … -18.0	—	10d 12h ago
SutMesh Base KQ4SNE heard by this node	5 RF	—	-15.2 dB … -19.5	—	10d 14h ago
S5 TREKKER DELTA heard by this node	2 RF	—	-15.8 dB … -17.5	—	14d 19h 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.