Skip to content

MESH-API v0.7.3.7 Beta - All Extensions Route to MeshCore

Choose a tag to compare

View all tags
@mr-tbot mr-tbot released this 13 Jun 18:27
v0.7.3.7-beta
e0a2430

MESH-API v0.7.3.7 Beta — All Extensions Route to MeshCore

A bug-fix release on top of v0.7.3.6 Beta.

🟣 Every extension now reaches MeshCore (GitHub #59)

Messages and AI replies that an extension pushes to the mesh — Telegram, Discord, Home Assistant, the alert feeds (NWS, GDACS, Amber, NASA), MQTT, Matrix, Mattermost, n8n, and the rest — now reach every connected radio: Meshtastic and MeshCore, not just Meshtastic.

What was wrong: a user running Meshtastic + MeshCore + Telegram reported that a message sent from Telegram arrived on Meshtastic but never on MeshCore — "like the TG extension is not known for MeshCore." The shared BaseExtension.send_to_mesh() helper (and a couple of extensions that sent directly) only spoke to the Meshtastic interface and ignored MeshCore entirely.

The fix: extension outbound now flows through the core network-agnostic web_send path introduced in v0.7.0. Broadcasts fan out to every active radio and DMs route by the destination's network prefix, honoring default_send_network (auto = whichever radios are connected). Discord's webhook + polling inbound and Home Assistant's reply path were updated to use the same helper. A Meshtastic-only fallback is retained for older cores.

  • ✅ No config changes required — auto already targets whichever radios are connected.
  • ✅ Applies to all 30+ bundled extensions at once (single framework-level fix).
  • ✅ Slash commands and AI replies were already network-agnostic; this closes the gap for extension-originated traffic.

📚 Documentation

  • All in-app and README version references updated to v0.7.3.7.
  • CHANGELOG updated with summary + detailed notes.

Beta software. Verify on your own mesh before relying on it for emergencies.

Assets 2
Loading