Skip to content

Build a standalone MQTT observer

Dedicated observer firmware lets a supported Wi-Fi LoRa board send nearby packet telemetry without a separate host computer.

Is this method right for you?

Good fitYou can dedicate a supported Wi-Fi LoRa board to observing.
Choose another methodRemoteTerm, Home Assistant, PyMC, or a nearby USB host already manages the radio.
What stays onlineThe board, stable power, 2.4 GHz Wi-Fi, and internet access.

This uses third-party firmware. Confirm the board and build shown by the flasher before continuing.

Confirm the firmware source

Item Reference
Flasher observer.gessaman.com
Recorded source branch mqtt-bridge-implementation-flex
Recorded source commit c0c845f5
Broker presets meshcore-ca-1 and meshcore-ca-2

The commit records the source used when this guide was reviewed; it does not prove the live flasher still uses that build. Stop if the flasher shows a board, source, or build you have not checked.

Before you start

Back up before enabling Erase device

Erasing can remove the private identity key, name, radio settings, region data, and other saved configuration. Back up the private key and record the board, role, firmware version, and settings. If an identity cannot be backed up, stop and use a new board or ask for help.

  • [ ] Confirm the exact board is listed by the observer flasher.
  • [ ] Decide whether this node should repeat traffic or observe only.
  • [ ] Back up the existing identity and settings.
  • [ ] Keep a known-good data USB cable and the board's recovery method nearby.
  • [ ] Choose a real location code.

What this changes

Flashing replaces the board firmware. Setup then changes its name, radio values, path-hash mode, location code, Wi-Fi credentials, broker presets, packet mode, and repeat behaviour.

The command builder runs locally in this browser. It does not store Wi-Fi fields, place them in the URL, or include them in the default preview.

Set up

1. Flash the board

  1. Open observer.gessaman.com.
  2. Under MQTT Observer Firmware, choose the exact supported board.
  3. Choose Repeater or Room Server.
  4. For a new or intentionally repurposed board, enable Erase device only after the backup gate above.
  5. Flash the merged image.
  6. When flashing finishes, prefer Configure via USB. Use Console only for settings the setup screen does not expose.

The flasher should report completion and the board should reconnect over USB.

2. Enter the shared settings

Use the local mesh settings. When no community override exists, the Canadian onboarding baseline is:

Setting Value
Radio preset USA/Canada (Recommended)
Raw radio values 910.525 MHz / 62.5 kHz / SF7 / CR5
Path hashes 3 bytes (set path.hash.mode 2)
Primary preset meshcore-ca-1
Backup preset meshcore-ca-2
Wi-Fi A 2.4 GHz network

3. Build the commands

The CLI has no documented general quoting contract. The builder rejects spaces, quotes, backslashes, control characters, and other ambiguous Wi-Fi values. Use Configure via USB for a network it cannot represent safely.

Loading Canadian location suggestions…

SSID and password stay in this page only. They are cleared when you leave and hidden from the preview until you reveal them.

Complete the required fields to build commands.

Check the non-sensitive summary and redacted preview. Reveal and copy commands only on a trusted computer. The clipboard will contain Wi-Fi credentials, so clear it after use.

Enter commands by hand

If you prefer manual entry, set the non-sensitive values first:

set name YOW-Repeater-01
set radio 910.525,62.5,7,5
set path.hash.mode 2
set mqtt.iata YOW
set wifi.powersave none
set mqtt1.preset meshcore-ca-1
set mqtt2.preset meshcore-ca-2
set mqtt3.preset none
set mqtt4.preset none
set mqtt5.preset none
set mqtt6.preset none
set mqtt.status on
set mqtt.packets on
set mqtt.raw off
set mqtt.rx on
set mqtt.tx advert
set bridge.enabled on
set repeat on
advert

Replace the name and location code. Use set repeat off for an observe-only node.

Enter credentials directly in the device console:

set wifi.ssid <network-name>
set wifi.pwd <network-password>
reboot

Do not paste completed credential lines into chat, issues, screenshots, logs, or saved notes. Do not add generic shell quotes to a device CLI value.

What you should see

After reboot, run:

get name
get wifi.status
get mqtt.iata
get mqtt1.preset
get mqtt2.preset
get mqtt.status
get mqtt.packets
get bridge.enabled
get path.hash.mode

The board is configured correctly when:

  • Wi-Fi and MQTT report connected;
  • the location code is correct;
  • presets are meshcore-ca-1 and meshcore-ca-2;
  • packet publishing and bridge mode are on; and
  • path hash mode is 2.

Verify in CoreScope

  1. Find the observer in CoreScope Observers.
  2. Wait for normal nearby radio activity.
  3. Confirm a recent packet in CoreScope Packets.

Finish with Check your observer. Connected Wi-Fi and MQTT are not proof that packets reached CoreScope.

Recovery

If the board does not reboot or reconnect:

  1. disconnect and reconnect with a known-good data cable;
  2. use the board-specific recovery/boot sequence published by the flasher;
  3. reflash the exact correct target without erasing again unless recovery requires it;
  4. restore the backed-up identity and settings only to the intended board; and
  5. repeat the local CLI checks before returning the board to service.

If the firmware runs but observing fails, restore the recorded prior settings or reflash the last known-good reviewed build. Keep the private identity backup private.

If verification fails

Use Troubleshooting. Share only read-command output after removing private details. Never share Wi-Fi commands or a private key.