Skip to content

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

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Jun 00:27
observer-eastmesh-v2026.6.4
263f04e
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 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

Assets

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