We don't have a local MQTT server for MeshCore here in Brisbane yet. But you can still contribute to monitoring and diagnostics of both local data and global mesh data with a MeshCore Observer pointed towards EastMesh (Australia) or LetsMesh (Global) brokers.
Observers monitor packets and forward them to monitoring and visualisation tools specifically built for MeshCore networks. There are several end points that forward on to different web-apps that can be accessed with just your browser.
The EastMesh broker presents to Corescope which provides detailed monitoring and tracing, as well as the EastMesh Maps for eastern Australia.
The LetsMesh broker is a global end point that forwards on to several other tools as well as it's own mapping and tracing.
MeshCore-EastMesh keeps the upstream MeshCore firmware intact and adds an EastMesh layer on top for:
repeater_mqtt builds with native WiFi, MQTT, and the optional local web panelcompanion_radio_wifi builds for Wi-Fi-connected companion devicesFollow the instructions here on their Wiki
The firmware will has options to send data to the following brokers.
eastmesh-auletsmesh-euletsmesh-usIf you'd like to connect your node to EastMesh MQTT broker, then here are the settings you'll need.
| Server | mqtt2.eastmesh.au |
| Port |
443 for https 9883 for http |
| TLS enabled |
Yes (for https) No (for http) |
| Verify TLS | Yes (recommended) |
| Transport | websockets |
| Token Audience | mqtt2.eastmesh.au |
| Payload Mode | Packet |
| Status Topic | meshcore/{IATA}/{PUBLIC_KEY}/status |
| Packets Topic | meshcore/{IATA}/{PUBLIC_KEY}/packets |
IATA:
The MeshCore-EastMesh project uses a curated list of IATA airport codes to define its regional "Scope." These codes act as administrative boundaries for the mesh, ensuring that traffic is routed efficiently and that nodes appear in the correct geographic clusters on the CoreScope map.
If a relevant region cannot be found here.
Then you can map to your local IATA code for the region on this map.
Public Key:
This is the public key of your Observer. Most clients will automatically fill out the details.
TLS Enabled:
Depending on your node hardware or MQTT client, this option may or may not work. The MQTT server does support both TLS and non-TLS connections.
It's ideal to have it on if your node supports it, but if you find it won't work, it's fine to leave it disabled.
Clarification on encryption/TLS: