Skip to content

MESH-API v0.7.2.2 Beta — Traffic Monitor, Emergency Alerts & Hermes Extension

Pre-release
Pre-release

Choose a tag to compare

@mr-tbot mr-tbot released this 10 Jun 03:48

MESH-API v0.7.2.2 Beta — Traffic Monitor, Emergency Alerts & Hermes Extension

A feature release on top of v0.7.2.1 Beta.

📊 Real-time Traffic Monitor

A new movable 📊 Traffic Monitor box at the top of the dashboard visualizes live mesh radio activity:

  • Green → yellow → red bars scale with traffic intensity (RX received + TX sent), over a sliding 60-second window.
  • A thin amber marker on each bar shows the TX portion so you can tell sent vs received at a glance.
  • Like every dashboard panel it can be dragged, reordered, or hidden (it's registered in the UI Settings → section visibility list).
  • Backed by a new lightweight GET /api/traffic endpoint (per-second rx/tx buckets + rolling totals). Traffic is counted at the radio chokepoints for both Meshtastic and MeshCore.

🚨 Emergency Alert Box

When a node triggers /emergency (or /911):

  • A large flashing red box appears in the masthead — between the logo and the toolbar, below the connection status — pulsing for visibility.
  • Click it to open a modal listing each alert with the message text and node information (name, short name, ID, hop count) plus Reply and Show on Map actions.
  • Alerts must be cleared by the user (per-alert "Clear" or "Clear All"); cleared state persists in the browser so they don't re-appear.

🧩 Hermes is now an Extension (not core)

The Nous Research Hermes AI provider has moved out of the core into a bundled extension (extensions/hermes), keeping the core lean:

  • It registers itself as the hermes AI provider automatically, so setting ai_provider: "hermes" or a Channel-Agent provider: hermes continues to work exactly as before.
  • Configure it from the 🧩 Extensions manager (API key, model, URL, timeout) instead of the core config.
  • Backward compatible: legacy hermes_* keys in the main config.json are imported into the extension automatically on first load.
  • The core AI-provider dispatch now routes any extension that registers an ai_provider_name, so third-party AI-provider extensions work generically too.

🐳 Docker

Multi-arch images (linux/amd64 + linux/arm64) are published to Docker Hub: mrtbot/mesh-api (latest, 0.7.2.2-beta, 0.7.2.2).


Built and maintained by one developer with the help of AI tools. If MESH-API is useful to you, please consider a donation (links in the README) and file issues with your real-world experience. 🙏