Config, best source first: a named MQTT channel (e.g. SFNarrow) › the node's own
map report › the MQTT channel it was heard on (an unnamed primary channel carries the preset name)
› its name (“MF”, “LongFast”, Gaulix codes like 35RENNLM8ClP).
Frequency is never published as a value. It is read from node names (“MF 869.3”) in the cell, then
from same-config nodes within 40 km, then from documented communities; otherwise the firmware default
is shown. Map reports do say whether a node is off the default channel/frequency — used to flag doubtful defaults.
Cells with no data borrow the majority of known nodes within 30 km (pale, dashed).
Colours: 8 colour-blind-checked slots in a fixed order; rarer configs are grouped as “Other”.
QR codes
Standard meshtastic.org/e/#… channel links, built in your browser. Scan, choose
Replace: it sets region, preset, frequency and the options below, and replaces your channels.
Re-add private channels with Add. Replace rewrites the whole LoRa section: TX power and OK-to-MQTT
are kept, rarely used options not in the link (frequency offset, duty-cycle override…) return to their defaults.
A channel is a name plus an encryption key. Keys are never in public data, so a renamed channel (e.g. SFNarrow) is encoded with the public default key. If the community uses its own key, you will be on the right frequency but unable to read messages: use the QR the community publishes.
Configs outside the EU 869.4–869.65 MHz band are flagged and their QR is hidden behind a click.
Presets that need firmware 2.8 get no QR.
Limits
Only nodes relayed by a public MQTT gateway appear; RF-only meshes are missing.
Without a name hint or a community document, the frequency shown is the firmware default and may be wrong.
Positions are self-reported and often fuzzed by several km. One or two nodes prove nothing.
Map reports have no “custom settings” flag: a custom setup can show up as LongFast.