EastMesh

Capabilities

Node role

Features

• MQTT repeater builds
• WiFi companion builds
• Optional local HTTPS config panel (ESP32)
• JWT auth using device identity
• Battery reporting on supported targets
• Observer role support

1. v2026.6.5 # Latest 2 variants 2 days ago · 2026-06-26 02:52 UTC

   observer eastmesh observer-eastmesh-v2026.6.5 View ↗

   observer eastmesh bridge espnow observer-eastmesh-bridge-espnow-v2026.6.5 View ↗

   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 the Waev curated broker as a selectable MQTT uplink — with automatic short-lived auth tokens to satisfy Waev's requirements — and widens the Custom MQTT settings panel in the web panel.

   What's Changed

   • Added the waev curated broker (wss://mqtt.waev.app:443/mqtt) using WSS, verified TLS, and MeshCore JWT authentication with the broker host as the token audience.
   • Added get mqtt.waev and set mqtt.waev on|off to toggle the Waev broker, and added Waev to the Primary MQTT and Secondary MQTT dropdowns in the web panel.
   • Added per-broker JWT auth token lifetimes; Waev receives a 1-hour token to match its shorter maximum token lifetime, while the other brokers keep the existing lifetime.
   • Fixed the web panel so the Custom MQTT settings panel spans the full width of the MQTT Servers card when Custom is selected.
   • Updated the README and custom CLI guides for the Waev broker.

   Breaking Changes

   • None in this release.

   If you are upgrading from before 2026.6.4, that release's changes still apply: get mqtt.status switched from per-broker fields to p:/s: broker slots, and saved LetsMesh EU/US selections are cleared once on upgrade.

   Notes

   • eastmesh-au remains the recommended MQTT endpoint once mqtt.iata is configured; meshmapper and waev are available as global second brokers.
   • Select brokers from the Primary and Secondary dropdowns in the web panel, or toggle them from the CLI (set mqtt.eastmesh-au on, set mqtt.meshmapper on, set mqtt.waev on, etc.). A maximum of two brokers can be enabled at once.
   • waev (mqtt.waev.app) uses a 1-hour auth token that the firmware refreshes automatically, so no extra configuration is needed. Set your Waev account email with set mqtt.email <email> so Waev can link the observer to your account.
   • LetsMesh EU/US are retired but still selectable for legacy use.
   • Custom MQTT is available for private broker deployments and uses username/password auth only. 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 connects 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.unscoped defaults to 64; lower it only if you want to limit how far unscoped flood traffic repeats.
   • flood.max.advert controls the hop limit for flooded advert packets.

   Documentation

   xjarid.github.io/MeshCore-EastMesh

   Flashing

   • flasher.eastmesh.au
   • flasher.meshcore.io

   Assets

   • .bin - standard update image
   • -merged.bin - full ESP32 image for flashing after erase
2. v2026.6.4 # 2 variants 5 days ago · 2026-06-23 00:27 UTC

   observer eastmesh observer-eastmesh-v2026.6.4 View ↗

   observer eastmesh bridge espnow observer-eastmesh-bridge-espnow-v2026.6.4 View ↗

   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 replaces the retired LetsMesh brokers with the new MeshMapper broker and reworks broker selection into Primary and Secondary slots.

   What's Changed

   • Added the meshmapper curated broker (wss://mqtt.meshmapper.net:443/mqtt) using WSS, verified TLS, and MeshCore JWT authentication with the broker host as the token audience.
   • Added get mqtt.meshmapper and set mqtt.meshmapper on|off to toggle the MeshMapper broker.
   • Reworked the web-panel broker section into Primary MQTT and Secondary MQTT dropdowns that enforce the two-broker maximum and reveal the custom host, username, and password fields when Custom is selected.
   • Retired the unmaintained LetsMesh EU/US brokers; they remain selectable but are marked retired, and saved selections are cleared once on upgrade so dead brokers stop retrying.
   • Shortened get mqtt.status to report the two active broker slots as p:<broker>:<state> and s:<broker>:<state> (for example p:meshmapper:up), keeping the reply within the LoRa text limit.
   • Custom MQTT remains username/password only; no JWT/web auth is used for custom brokers.
   • Updated the README, web panel, and custom CLI guides for MeshMapper and the Primary/Secondary broker layout.

   Breaking Changes

   • get mqtt.status output changed from per-broker fields to p:/s: broker slots; update anything that parses the previous format.
   • Saved LetsMesh EU/US broker selections are cleared once on upgrade; re-enable a broker such as MeshMapper if you need a second uplink.

   Notes

   • eastmesh-au remains the recommended MQTT endpoint once mqtt.iata is configured; meshmapper is available as a global second broker.
   • Select brokers from the Primary and Secondary dropdowns in the web panel, or toggle them from the CLI (set mqtt.eastmesh-au on, set mqtt.meshmapper on, etc.). A maximum of two brokers can be enabled at once.
   • LetsMesh EU/US are retired but still selectable for legacy use.
   • 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 connects 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.unscoped defaults to 64; lower it only if you want to limit how far unscoped flood traffic repeats.
   • flood.max.advert controls the hop limit for flooded advert packets.

   Documentation

   xjarid.github.io/MeshCore-EastMesh

   Flashing

   • flasher.eastmesh.au
   • flasher.meshcore.io

   Assets

   • .bin - standard update image
   • -merged.bin - full ESP32 image for flashing after erase
3. v2026.6.3 # 2 variants 18 days ago · 2026-06-09 10:19 UTC

   observer eastmesh observer-eastmesh-v2026.6.3 View ↗

   observer eastmesh bridge espnow observer-eastmesh-bridge-espnow-v2026.6.3 View ↗

   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 /mqtt WebSocket path.
   • Configured custom MQTT WSS using a full wss://host:port/mqtt URI so ESP-MQTT handles the WebSocket connection consistently.
   • Updated get mqtt.status to show the custom MQTT transport and state, for example custom:wss:up.

   Breaking Changes

   None.

   Notes

   • eastmesh-au remains the recommended MQTT endpoint once mqtt.iata is 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.unscoped defaults to 64; lower it only if you want to limit how far unscoped flood traffic repeats.
   • flood.max.advert controls the hop limit for flooded advert packets.

   Documentation

   xjarid.github.io/MeshCore-EastMesh

   Flashing

   • flasher.eastmesh.au
   • flasher.meshcore.io

   Assets

   • .bin - standard update image
   • -merged.bin - full ESP32 image for flashing after erase