MeshCore EastMesh Observer
EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.
This release adds secure WebSocket transport support for custom MQTT brokers from the Observer web panel and CLI.
What's Changed
- Added TCP/WSS transport selection for custom MQTT brokers.
- Added web-panel Custom MQTT transport control for switching between TCP and WSS.
- Added CLI support for viewing and setting the custom MQTT transport.
- Kept custom MQTT authentication to username and password only; no JWT/web auth is used for custom brokers.
- Verified custom MQTT WSS connections with the ESP-IDF x509 root CA bundle.
- Fixed custom MQTT WSS to use the
/mqttWebSocket path. - Configured custom MQTT WSS using a full
wss://host:port/mqttURI so ESP-MQTT handles the WebSocket connection consistently. - Updated
get mqtt.statusto show the custom MQTT transport and state, for examplecustom:wss:up.
Breaking Changes
None.
Notes
eastmesh-auremains the recommended MQTT endpoint oncemqtt.iatais configured.- Custom MQTT is available for private broker deployments.
- For TCP custom MQTT, use the broker host and port as before.
- For WSS custom MQTT, set the host and port, select WSS transport, and the firmware will connect using
wss://host:port/mqtt. - WSS uses TLS encryption and validates against the ESP-IDF x509 root CA bundle.
- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with
set web off. - Browsers may still require accepting the self-signed certificate warning on first HTTPS access.
flood.max.unscopeddefaults to64; lower it only if you want to limit how far unscoped flood traffic repeats.flood.max.advertcontrols the hop limit for flooded advert packets.
Documentation
xjarid.github.io/MeshCore-EastMesh
Flashing
Assets
.bin- standard update image-merged.bin- full ESP32 image for flashing after erase