Check your observer

A broker connection proves only internet access. Your observer is working when a real radio packet reaches CoreScope.

Follow a packet through four stages

1. Radio: confirm the device is on the local mesh settings and can hear nearby activity.
   A packet counter, log, or connected application should change when a nearby node transmits.
2. Observer: check the method's service, integration, or device status.
   It should report an encrypted connection to at least the primary endpoint without repeating authentication errors.
3. Observer view: open CoreScope Observers.
   The observer name and three-letter location code should appear with a recent timestamp.
4. Packet view: create nearby MeshCore activity, then open CoreScope Packets.
   A recent packet attributed to the observer should appear within a few minutes.

Do not generate unnecessary traffic on a busy mesh. A normal advert or existing nearby activity is enough.

Check the details

Check	What you should see
Name	A clear service name such as YOW-Repeater-01, without a home address
Location	The nearest real three-letter airport code, not CAN, XXX, or HOME
Primary path	Connected to mqtt1.meshcore.ca with TLS certificate verification
Backup path	Connected to mqtt2.meshcore.ca where the method supports two entries
Packet mode	Packet publishing is enabled, not status-only
Packet time	A recent packet appears after the radio hears nearby traffic
Radio	Local settings are used; the Canada defaults apply only when no local override exists

Keep a maintenance note

Keep a short private maintenance note:

Observer:
Method and version:
Location code:
Checked at (include time zone):
Radio heard a packet: yes / no
Primary connected: yes / no
Backup connected: yes / no / not supported
Observer visible: yes / no
Packet visible: yes / no

Do not include credentials, private keys, Wi-Fi names, or Wi-Fi passwords.

Start with the first thing that failed

Use the matching guide for the first thing that failed:

What failed first	Where to start
Radio does not hear activity	Observer appears but no packets
Observer cannot connect	Observer never appears
Observer is visible but packet view stays empty	Observer appears but no packets
Backup alone fails	Only the backup connection fails
Place or name is wrong	Observer appears in the wrong place

For safe commands and a redacted support note, use Troubleshooting.