PacketTrends Mesh a public map of nodes that asked to be on one map stations

Rene WRKS539

!1f2e5669 · firmware 2.8.0.ad0628d · reports 16 node(s) online locally · updates every minute

95% 4.12 V · 8 h 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

Heard once, on Nov 5 first heard Nov 5 · 1 active day · 1 RF frame · 1 gateway

Nov 5 Nov 15

Most recent

KE4JQ MOB1W 511m KE4JQ MT EDC v4 514m TAV G2 516m SSS Test2 522m HMSTD G2 534m

Who heard it

Last 24 hours.

This node is a gateway. It has received 5 node(s) itself (5 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
HMSTD G2 heard by this node 5 RF — -5.8 dB … -11.8 — 8h 54m ago
KE4JQ MOB1W heard by this node 1 RF — hop distance not reported — 8h 31m ago
KE4JQ MT EDC v4 heard by this node 1 RF — hop distance not reported — 8h 34m ago
TAV G2 heard by this node 1 RF — hop distance not reported — 8h 36m ago
SSS Test2 heard by this node 1 RF — hop distance not reported — 8h 42m 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.