BOMBERO_🚒_BASE

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

100% 4.20 V · 20 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

History

Silent for 20d 16h Sep 15 to Oct 25 · 35 active days · 777 RF frames · 7 gateways

Sep 15 Nov 15

Most recent

BOMBERO_🚒_MQTT 29810m BOMBERO_🚒_ZHILLS 39494m SAMIAM_FETT no pin 39499m

Who heard it

YGV stations first (2), then direct links. Last 24 hours, plus 3 direct link(s) heard earlier.

Peer	Frames	Hops	SNR (direct only)	Hop budget left	Last heard
BOMBERO_🚒_MQTT	202 RF	—	8.0 dB … 3.0	—	20d 16h ago
BOMBERO_🚒_ZHILLS	1 RF	—	5.8 dB	—	27d 10h ago
SAMIAM_FETT heard by this node	1 RF	—	5.8 dB	—	27d 10h 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.