Observer connection reference¶
Use this after you choose an observer setup. Follow that guide rather than copying these values without context.
Broker settings¶
These values come from the shared observer configuration.
| Use | Host | Port | Transport | TLS | Token audience |
|---|
Loading official connection settings…
If the table does not load, open observer-config.json.
Topic templates¶
meshcore/{IATA}/{PUBLIC_KEY}/packets
meshcore/{IATA}/{PUBLIC_KEY}/status
{IATA} is the observer's real three-letter location code. {PUBLIC_KEY} is supplied by the radio or integration. Never substitute a private key.
Authentication and transport¶
- Use WebSockets on port
443. - Require TLS and verify certificates.
- Use the MeshCore JWT token option where available.
- Match each token audience to its server address.
- Do not put a token or password into a URL, screenshot, issue, or diagnostic bundle.
Packet mode by method¶
| Method | Required packet setting |
|---|---|
| MQTT firmware | mqtt.packets on, bridge.enabled on, and mqtt.rx on |
| MCtoMQTT / companion capture | Configure the /packets topic |
| PyMC | format: letsmesh |
| Home Assistant | Payload Mode = packet |
| RemoteTerm | Enable the Community MQTT packet topic |
What each check tells you¶
| State | What it proves |
|---|---|
| DNS or port reachable | The host can reach the server |
| Broker connected | Transport and authentication succeeded |
| Observer visible | Status reached the live service |
| Recent packet visible | The radio-to-viewer path works end to end |
Only a recent packet completes the observer check.