Observe with Home Assistant¶
Use the MeshCore integration you already run in Home Assistant to publish packet telemetry to MeshCore Canada.
Is this method right for you?¶
Check your screen¶
Current MeshCore integrations use these fields:
| Packet control | Location control |
|---|---|
Payload Mode = packet |
Free-text Broker IATA Code |
If your screen looks different, see Home Assistant screen does not match the guide. Update the integration if it cannot accept the correct location code; do not substitute a nearby code.
Before you start¶
- [ ] Home Assistant and the MeshCore integration are healthy.
- [ ] The radio is connected over a supported USB, BLE, or TCP path.
- [ ] The radio uses the local mesh settings.
- [ ] You chose a real location code.
- [ ] You read Observer data, access, and privacy.
What this changes¶
You will add two MQTT broker entries and enable packet payloads. Do not enter a Wi-Fi password or static MQTT password.
Set up¶
Open:
Settings → Devices & Services → MeshCore → Configure → Manage MQTT Brokers
Add the primary entry:
| Field | Value |
|---|---|
| Server | mqtt1.meshcore.ca |
| Port | 443 |
| Transport | websockets |
| Use TLS | Enabled |
| TLS Verify | Enabled |
| Username / Password | Leave blank |
| Use MeshCore Auth Token | Enabled |
| Token Audience | mqtt1.meshcore.ca |
| Payload Mode | packet |
| Status Topic | meshcore/{IATA}/{PUBLIC_KEY}/status |
| Packets Topic | meshcore/{IATA}/{PUBLIC_KEY}/packets |
Set the integration's location field to the real three-letter code nearest the observer.
Add the backup entry with the same settings, changing only:
| Field | Value |
|---|---|
| Server | mqtt2.meshcore.ca |
| Token Audience | mqtt2.meshcore.ca |
Leave optional owner fields blank unless they are needed. Save both entries.
What you should see¶
Both entries show connected and nearby radio activity changes the packet count. If the brokers connect but no packets appear, packet mode may be off or the radio may hear nothing.
Verify in CoreScope¶
- Find the observer in CoreScope Observers.
- Wait for normal nearby MeshCore activity.
- Confirm a recent packet in CoreScope Packets.
Finish with Check your observer. Home Assistant's connected badge is not proof that packets reached CoreScope.
Recovery¶
Disable or remove only the two MeshCore Canada broker entries you added. Keep unrelated Home Assistant integrations and the radio connection unchanged. Confirm the original MeshCore integration still operates.
If verification fails¶
Use Troubleshooting. Include the Home Assistant version, MeshCore integration version, first failed stage, and a redacted error. Review any diagnostics archive before sharing it.