MeshContinuum (MECON) Invitation Only

A web reader for your MeshCore mesh

MeshContinuum connects to a MeshCore mesh through a supported Companion or Repeater and gives you a web reader for its message history, plus remote management of the devices connected to it.

The mesh itself keeps working exactly as MeshCore is designed to — offline, peer to peer, with no cloud in the loop. This service is an optional companion to that, not a replacement for it: your mesh does not depend on it, and does not stop working if it is unreachable.

View the project on GitHub

How it fits together

MeshContinuum is an application layer around MeshCore — it does not replace MeshCore's packet formats, radio routing, node identities, or normal Companion apps. Everything in the shaded area is optional; the radios keep talking to each other without it.

MeshContinuum architecture MeshCore radios (Companions, Repeaters, the RF network) connect to Observers and MQTT brokers, which connect to the MeshContinuum backend, which serves the Reader web app. A dashed boundary marks everything from Observers onward as optional: the MeshCore radios keep working peer to peer without any of it. MeshContinuum (optional) MeshCore Companions, Repeaters RF network Observers & MQTT brokers own · shared · public MeshContinuum backend stores · dedupes decrypts · routes one durable record Reader web app RF packets MQTT API keeps working, offline, on its own

A standard USB Companion can also reach MeshContinuum directly, through a small Pi gateway agent and an authenticated connection — no MQTT broker required for that path.

What MeshContinuum adds on top of MeshCore

Live views from this instance's own Reader — an actual fleet of Companions and Repeaters, not a mockup.

Devices overview listing an actual fleet of MeshCore Companions and Repeaters, with connection, decryption, firmware version, battery, uptime and packet counts per device.

One inventory for every enrolled device

Every Companion and Repeater this instance knows — connection state, decryption status, firmware version, battery, uptime and packet counts — in one list, kept current whether or not a phone is anywhere nearby.

Remote device configuration page showing radio settings, name and location, and access fields for a Repeater, editable over MQTT or USB.

Remote configuration, over MQTT or USB

Radio parameters, name, location and access settings, read from and written back to the real device — automatically over whichever transport is actually available right now.

Device status page showing identity, firmware, connection health, over-the-air update history and reported crash diagnostics for one device.

Diagnostic transparency

Identity, firmware, link health, update history and — when something goes wrong — the device's own reported crash diagnostics. Nothing about a device's real state is hidden from its own operator.

Over-the-air firmware update confirmation dialog, describing signature verification and automatic revert on a failed update.

Signed, backend-scheduled firmware updates

A device pulls a new build over its existing connection and verifies the release's signed manifest itself before writing a byte — and reverts on its own if the new build never reconnects.

A MeshCore channel conversation showing decrypted messages with per-message observation counts, alongside a compose bar for sending through an enrolled gateway.

Read and send, from a browser

Channel history stays readable long after any one radio has moved on, each message carries how many observers actually heard it, and a reply goes out through whichever enrolled gateway is available.