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

FAU Solar

!329adcdf · updates every minute

94% 4.09 V · 15 min ago

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; the firmware default. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

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 on 62 days Sep 15 to Nov 15 · 62 active days · 3723 RF frames · 37 gateways

Sep 15 Nov 15

Most recent

CWP3Node 15m ERM Gateway 15m KQ4OOB - Base 68m FoxTastic-Home 240m ERM Base M2 Temp 240m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CWP3Node 2 RF — relayed — not attributable — 15 min ago
ERM Gateway 16 RF — hop distance not reported — 15 min ago
KQ4OOB - Base 14 RF — hop distance not reported — 1h 8m ago
FoxTastic-Home 1 RF — hop distance not reported — 4h 0m ago
ERM Base M2 Temp 4 RF — hop distance not reported — 4h 0m ago
Meshtastic eeff 1 RF — relayed — not attributable — 16h 9m ago
IRE Base MQTT 1 RF — relayed — not attributable — 16h 9m 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.