MeshCore Guide: Repeater-Based LoRa Mesh on Your Meshtastic Hardware

MeshCore, popularized in large part by Andy Kirby’s channel and now maintained by the meshcore-dev community, is the most serious architectural alternative to Meshtastic on identical hardware. If Meshtastic is a crowd where everyone repeats everything they hear, MeshCore is a courier network with dispatchers: quieter, more deliberate, and better suited to networks you design rather than networks that just happen. Version 1.16 (June 2026) runs on the boards Canadians already own — Heltec V3, RAK4631, T-Beam, T-Deck, T-Echo, XIAO nRF52/ESP32-S3, Station G2/G3, T1000-E — in the licence-exempt 902–928 MHz band under ISED RSS-247.

How the routing actually works

Four steps, verified against the project’s own documentation. First, a message to a new destination (and every public-channel message) is flooded — Repeaters rebroadcast it outward. Second, on delivery the destination returns an acknowledgement that records the exact chain of Repeaters the packet crossed. Third, that path is embedded in the header of every subsequent direct message, so Repeaters forward it only along the known route — no redundant rebroadcasts. Fourth, if a cached path goes stale, the sender retries it and, after three failures, resets and re-floods to learn a fresh route. The result is a mesh whose airtime cost stays nearly flat as membership grows — the scaling weakness of managed flooding is designed out, at the price of needing infrastructure: a bag of Companion-only nodes will not self-heal into a multi-hop network. Someone has to place Repeaters.

The three roles you’ll actually deploy

Companion is your pocket node: it pairs with the free Android/iOS app (or the web client and CLI) over Bluetooth, USB or Wi-Fi, sends and receives, and never relays — which is why handheld battery life is architecturally better than Meshtastic’s (field reports agree, though no rigorous benchmark exists). Repeater is fixed infrastructure — rooftop, mast, solar box — configured over USB at config.meshcore.io, or over the air if you buy the RF remote-management unlock. Placement is the whole game: a valley chain of three well-sited Repeaters outperforms thirty random handhelds. Room Server is a store-and-forward bulletin board that buffers roughly 32 unseen messages per member — the mesh equivalent of a village noticeboard, ideal for groups that aren’t online simultaneously. Change its default passwords immediately: guest is “hello” and admin is “password” out of the box, and leaving them is an open door.

Security: honest marks, not marketing

Identity is solid: every node advertises a signed Ed25519 public key, and direct messages derive per-contact keys via X25519 key exchange — cleaner than a shared channel PSK. The payload layer is the weak spot: messages are encrypted with AES-128 in ECB mode and authenticated by an HMAC-SHA256 truncated to two bytes, and community cryptographers have rightly flagged both choices — ECB leaks patterns across repeated blocks, and a 2-byte MAC is a thin integrity check. Treat MeshCore’s encryption as serious obfuscation with authentication, not high-assurance cryptography; Meshtastic’s AES-256-CTR is the stronger construction today. For coordinating a ride share or a farm crew, it is entirely adequate. For anything where an interception matters, encrypt above the transport — the same advice we give for any radio link.

Flashing a Meshtastic radio to MeshCore (and back)

Use the official web flasher in Chrome or Edge (it needs Web Serial), pick board, role and region — Canada is the 915 MHz plan, with a North American default around 910.5 MHz, SF7, 62.5 kHz bandwidth. When converting from Meshtastic, do a full erase first so stale config can’t corrupt anything; when merely updating MeshCore, never full-erase — it destroys your node identity and keys. ESP32 boards flash directly over USB; nRF52 boards (RAK4631, T-Echo, XIAO nRF52840) double-tap reset into a UF2 drive and take a drag-and-drop file. After flashing, “Forget” the device in your phone’s Bluetooth settings before re-pairing. Going back to Meshtastic is the mirror image at flash.meshtastic.org. No dual-boot exists — pick a firmware per board, and since boards are cheap, the practical answer for the curious is one of each.

Where it fits in a sovereign comms stack

MeshCore’s sweet spot is the engineered network: a property, a valley, a town where you control a few high spots and want maximum reach per milliwatt of airtime. Its 64-hop ceiling (Meshtastic stops at 7) makes long daisy-chains viable — coastline nets, road corridors, repeater-to-repeater backhauls. Its weaknesses are the mirror of its strengths: thin Canadian community density (Europe is its stronghold), a younger telemetry/integration ecosystem, the freemium unlocks, and the crypto caveats above. Our verdict lives in the full Meshtastic vs MeshCore head-to-head; the wider landscape — Reticulum, LoRaWAN, Helium, APRS — is scored in the mesh protocols comparison. Hardware that runs both firmwares is catalogued in the 915 MHz LoRa device database, link budgets are a range-calculator question, and if you’re building out a Canadian mesh — solar repeaters, node kits, antennas — start at the Meshtastic Canada hub or talk to us about a build.