Skip to content

Observer EastMesh Firmware v1.16.0-eastmesh-v2026.6.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Jun 02:52
observer-eastmesh-v2026.6.5
cdf2cc6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Assets

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