Skip to content

Set up a network observer

An observer forwards nearby MeshCore packet data to CoreScope. It does not decrypt private messages or need to repeat traffic.

How the pieces fit

  1. Radiohears nearby MeshCore packets
  2. Observerforwards the packet data
  3. MeshCore Canadareceives it through two shared endpoints
  4. Live toolsCoreScope shows observers and packets

The shared endpoints use MQTT, but you do not need to learn MQTT before choosing a setup.

Observers share what they hear

Observer details and heard packet data can appear in CoreScope. Do not transmit sensitive information. Read Observer data and privacy before turning one on.

Choose your setup

Start with what already manages your radio.

The same choices are listed here:

Your current setup Recommended method Host that must stay on
RemoteTerm already manages the radio RemoteTerm The RemoteTerm host
Home Assistant already has MeshCore Home Assistant Home Assistant
PyMC already manages a repeater PyMC The PyMC host
A Linux or macOS host is connected by USB MCtoMQTT The USB host
A supported Wi-Fi LoRa board can be dedicated Standalone MQTT firmware No separate host

If none fit, ask in the MeshCore Canada forum before installing anything new.

What every setup needs

Whichever setup you choose, you need:

  • a radio already set for the local mesh;
  • a real three-letter location code;
  • the MeshCore Canada primary and backup endpoints;
  • encrypted connections with certificate checks;
  • packet publishing, not status-only publishing; and
  • an always-on host or board.

The Canadian onboarding baseline is USA/Canada (Recommended), 910.525 MHz / 62.5 kHz / SF7 / CR5, with 3-byte path hashes. A published local setting takes priority.

For exact broker fields, use the observer endpoint reference.

Finish the check

Setup is not finished when a screen says “connected.” You are done when:

  1. your observer appears in CoreScope Observers; and
  2. a packet heard by your radio appears in CoreScope Packets.

Finish with Check your observer. If something fails, go to Troubleshooting.