Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

2026-11-03T17:06:24Z

Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)

New page

{{DISPLAYTITLE:Observers}}

== MeshCore Observers ==

Observers are how ScotMesh nodes appear on the live map. An '''MQTT observer''' build is a repeater-style MeshCore firmware image that can push mesh traffic up to one or more '''MQTT''' brokers — feeding live maps and tools — without replacing the normal RF repeater role. You can also run a receive-only observer at a site that does not repeat on air.

For the full technical detail on the bridge (up to three broker slots, presets, <code>custom</code>, JWT <code>audience</code>, merged first flash, and more), see the upstream write-up: [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md (agessaman fork)].


=== Firmware ===

Prebuilt '''repeater observer MQTT''' binaries are published here:

https://static.loraproject.ie/mqtt/

Pick the file that matches your '''exact board''' (Heltec, LilyGo, RAK, Station G2, and others appear in the directory listing).

'''<code>*_merged.bin</code> vs the non-merged <code>.bin</code>'''

* '''Files ending in <code>_merged.bin</code>''' are a '''full''' image (bootloader, partition table, and application). Flashing one '''normally wipes''' stored repeater settings). Use merged when you '''need''' that full layout refresh—for example the '''first''' move to observer firmware on a board, or when the observer build’s '''partition table''' is new for that hardware (see “Partition Table Changes” in [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md]).
* '''Files without <code>_merged</code> in the name''' update the '''app''' only when the '''partition layout is unchanged'''. That path is what you want when you '''already run observer firmware or a repeater''' on that board and you want to '''keep''' your current configuration through an upgrade.

After a merged flash, '''re-enter''' RF settings, node name, Wi‑Fi, MQTT, <code>mqtt.iata</code>, and other stored values. After a non-merged upgrade on the same layout, settings are '''usually''' kept—still read release notes. Later updates can use '''OTA''' ([[#updates-without-usb-start-ota|<code>start ota</code>]]) or a non-merged binary when appropriate.


=== Updates without USB: <code>start ota</code> ===

On the repeater '''serial console''' (same place you run <code>set</code> / <code>get</code> commands), you can start the '''over-the-air''' path that brings up Wi‑Fi for firmware upload, so you do not have to plug in USB for every update. The exact command is:

<syntaxhighlight lang="text">start ota</syntaxhighlight>
Use your build’s normal OTA workflow (browser or tool) once the device is advertising the update Wi‑Fi. Keep power stable during the flash.


=== Observer setup ===

# '''Flash''' the <code>*repeater_observer_mqtt*</code> file for your board ([[#firmware|Firmware]] explains '''<code>_merged.bin</code>''' vs non-merged).
# '''If NVS was wiped''' (typical after '''<code>_merged.bin</code>'''; '''NVS''' is ''Non-Volatile Storage''—flash-backed settings such as Wi‑Fi, MQTT, and radio prefs), set '''RF and node identity''' first: frequency, bandwidth, SF, CR, TX power, and '''name''' must match your mesh before the node is useful on air. Use the '''device web UI''' or admin screens, or serial, using your coordinator’s values; repeater planning is in [[MeshCore/Regions|Regions]]. '''Then''' work through '''Wi‑Fi''' → '''<code>mqtt.iata</code>''' → (optional '''receive-only''') → '''MQTT''' in order below. '''If you used a non-merged''' update and kept settings, use <code>get</code> and only redo what is wrong—but '''still check MQTT''': stock images often leave '''LetsMesh Analyzer US''' on '''slot 1''' and '''LetsMesh Analyzer EU''' on '''slot 2''' until you repoint them (for example MayoMesh on slot 1).


==== Wi‑Fi ====

The observer needs LAN or internet path to the broker.

<syntaxhighlight lang="text">set wifi.ssid YourWiFiNetwork
set wifi.pwd YourWiFiPassword</syntaxhighlight>

==== Site code (<code>mqtt.iata</code>) ====

A short tag for '''where the repeater sits'''. It appears in MQTT topics and on maps—pick something stable (IATA-style codes are common).

{| class="wikitable"
|-
! Code
! Area
|-
| <code>EDI</code>
| Edinburgh
|-
| <code>DND</code>
| Dundee
|-
| <code>GLA</code>
| Glasgow
|}

<syntaxhighlight lang="text">set mqtt.iata EDI</syntaxhighlight>

==== Optional: receive-only on RF ====

If this unit should '''not''' relay mesh traffic on air:

<syntaxhighlight lang="text">set repeat off</syntaxhighlight>

==== MQTT (MayoMesh on slot 1) ====

ScotMesh uses '''MayoMesh''' for the shared observer map and broker (who runs it and links: [[#mayomesh-live-map|MayoMesh live map]]). Observer builds usually ship with '''LetsMesh Analyzer US''' on '''slot 1''' and '''LetsMesh Analyzer EU''' on '''slot 2'''. Point '''slot 1''' at MayoMesh for our map. '''Apply this whenever <code>get mqtt1.preset</code> is not already your MayoMesh custom setup'''—including after a merged flash '''and''' after a non-merged upgrade from stock observer images.

<syntaxhighlight lang="text">set mqtt1.preset custom
set mqtt1.server mqtt.mayomesh.net
set mqtt1.port 443
set mqtt1.audience mqtt.mayomesh.net</syntaxhighlight>
If you '''only''' use MayoMesh and want to free a second TLS slot on low-RAM boards (see upstream notes on PSRAM / two WSS connections):

<syntaxhighlight lang="text">set mqtt2.preset none</syntaxhighlight>
Then:

<syntaxhighlight lang="text">reboot</syntaxhighlight>
With '''<code>audience</code>''' set, the device uses '''JWT (Ed25519)''' sign-in to the broker, same idea as the built-in WSS presets in [https://github.com/agessaman/MeshCore/blob/mqtt-bridge-implementation-flex/MQTT_IMPLEMENTATION.md MQTT_IMPLEMENTATION.md].


==== Check ====

<syntaxhighlight lang="text">get mqtt.status
get mqtt1.preset
get mqtt.tx
get mqtt.rx</syntaxhighlight>
Confirm the node shows on [https://meshcore.mayomesh.net/ meshcore.mayomesh.net] after a short wait.


=== MayoMesh live map ===

* '''Who runs it:''' MayoMesh (the map and <code>mqtt.mayomesh.net</code> broker) is operated by '''County Mayo''', '''Ireland'''. ScotMesh uses that community’s infrastructure for the shared observer map.
* '''LetsMesh Analyzer:''' [https://analyzer.letsmesh.net/packets?region=EDI,DND,DUB,BHD,GLA packet view filtered to <code>EDI</code>, <code>DND</code>, <code>DUB</code>, <code>BHD</code>, <code>GLA</code>].
* '''MayoMesh live map:''' [https://meshcore.mayomesh.net/ meshcore.mayomesh.net] — MQTT over WebSocket (for example <code>wss://mqtt.mayomesh.net</code>, as shown on the site).
* '''Broker commands''' for your repeater are in [[#observer-setup|Observer setup]] under '''MQTT (MayoMesh on slot 1)'''.
* '''Self-hosting the map UI:''' based on [https://github.com/yellowcooln/meshcore-mqtt-live-map yellowcooln/meshcore-mqtt-live-map]; point your instance at MayoMesh’s broker instead of default LetsMesh-style endpoints.


=== MQTT uplink: <code>mqtt.tx</code> advert vs <code>on</code> ===

These control '''which of this node’s transmitted packets''' are sent upstream over MQTT. '''<code>mqtt.rx</code>''' is separate (received packets).

{| class="wikitable"
|-
! Setting
! Effect
|-
| <code>set mqtt.tx advert</code>
| Uplink '''only this node’s own advert''' TX packets. Lighter load; usually enough for map presence.
|-
| <code>set mqtt.tx on</code>
| Uplink '''all TX''' from this node. Richer feed, more bandwidth and airtime.
|-
| <code>set mqtt.tx off</code>
| No TX uplink over MQTT.
|}

For most map feeds, '''<code>advert</code>''' is enough:

<syntaxhighlight lang="text">set mqtt.tx advert</syntaxhighlight>
If you need every TX packet this node sends mirrored upstream:

<syntaxhighlight lang="text">set mqtt.tx on</syntaxhighlight>
Use '''<code>on</code>''' only when you intend that heavier feed (more bandwidth and airtime).
## 🔗 See also

* [[MeshCore/Regions|Regions]] — repeater region codes on the Scottish mesh.
* [[MeshCore|MeshCore]] — hub page for channels, scopes, and related guides.

MeshCore/Observers - Revision history

Admin: Import MeshCore content from scotmesh-wiki (faithful; freshness pass next)