Experimental LoRa Mesh

MeshCore

A newer LoRa mesh protocol built around a different architecture than Meshtastic. It's decentralized by design — anyone can put up a node or repeater on their own, no club or coordinated rollout required. It runs on the same hardware Meshtastic does, and it's still actively developing here.

Frequency
910.525 MHz
License
None Required
Local Status
Developing
How this actually grows. MeshCore doesn't need a club or a coordinated rollout to get going — anyone can flash a device and put up a node or repeater independently. That means growth here happens organically, node by node, rather than waiting on an official local network to launch. Meshtastic still has the larger, more active presence locally through IowaMesh, but MeshCore is genuinely open for anyone to start building on right now.

What MeshCore actually is

Like Meshtastic, MeshCore runs on LoRa radio hardware and creates a mesh network for off-grid text messaging with no cell service or internet required. Where it diverges is architecture: instead of every device flooding messages to every other device in range, MeshCore separates nodes into distinct roles — companion radios that connect to a phone and only send/receive, repeaters whose specific job is forwarding traffic, and room servers that store messages for later pickup, similar to an old-school BBS.

That structure lets a MeshCore network find a route once and then send future messages along that known path, rather than rebroadcasting to everyone every time. The tradeoff is that it needs some deliberate planning — repeaters placed with intent — rather than Meshtastic's "everyone turns on a node and it just works" approach.

How it compares to Meshtastic

  • Not compatible. MeshCore and Meshtastic use different packet formats and can't talk to each other — a MeshCore node won't decode Meshtastic traffic even on the same frequency, and vice versa.
  • Same hardware, different firmware. Most popular LoRa boards support both — flashing between them takes a few minutes and no new hardware.
  • Built for different scales. Meshtastic is tuned for spontaneous, ad-hoc groups that just turn on and go. MeshCore is built for larger, more deliberately planned deployments where controlling routing and airtime matters more.
  • Delivery confirmation. MeshCore gives a definite yes/no on whether a message actually arrived; Meshtastic's delivery indicator is more ambiguous.

Deployment tips

Iowa's terrain shares a lot with what NodakMesh has documented for North Dakota — flat, open farmland is genuinely good for LoRa. A repeater with even modest elevation (20-30 feet) can often see clear line of sight for miles across open fields, and rural mounting points like grain elevators, silos, or an existing antenna tower tend to punch well above their weight for coverage.

Winters here aren't quite as extreme as North Dakota's, but cold still matters for battery-powered repeaters — lithium batteries lose real capacity in freezing temperatures, so an insulated, weatherproof enclosure and an oversized battery (or LiFePO4 chemistry, which handles cold better than standard LiPo) are worth planning for on anything meant to run unattended through winter. If wall power is available at the site, it's the simpler and more reliable choice over battery alone.

Getting started

Getting a first node running takes about 15 minutes and no license. Here's the short version:

  • Get a device. Any MeshCore-compatible LoRa radio works — make sure it's the 915 MHz version for North America, not the 868 MHz European variant.
  • Flash Companion firmware. The MeshCore web flasher installs it right from a Chrome or Edge browser — plug in with a real data cable (not a charge-only one, the most common snag), select your device, choose Companion, and flash.
  • Pair the app. Download the MeshCore companion app (iOS/Android) and connect over Bluetooth. Node discovery isn't instant — it can take a few minutes for nearby devices to exchange adverts and show up.
  • Start with Companion, not Repeater. A repeater can't send or receive your own messages, only relay others' — get a working companion node first before considering infrastructure.

Repeaters — extending coverage

A repeater is a dedicated device whose only job is relaying traffic — no phone pairing, no personal messaging, just power, an antenna, and a good spot. This is one of the bigger structural differences from Meshtastic: instead of every device on the network rebroadcasting everything, MeshCore only relays through devices specifically flashed as repeaters, which is a big part of why it stays quieter at scale.

The single biggest factor in how well a repeater performs is height, not raw power — a repeater mounted up on a roof or elevated structure will outperform one sitting at ground level by a wide margin, since LoRa depends heavily on a clear line of sight to the horizon. It's worth putting up a repeater once there's an area that can't reach an existing node, or a good elevated spot goes unused — not really worth it if you're the only person on the mesh nearby yet.

Room servers — store-and-forward messaging

A repeater only relays what's happening right now — if you're out of range when a message goes out, it's gone. A room server solves that by actually storing messages and handing them over when a member comes back into range, working like a community bulletin board rather than a live radio call: anyone can post, and everyone reads whenever they happen to check.

That makes room servers genuinely useful for groups that aren't all online at once — a volunteer fire department on different schedules, a farm with workers checking in at different times of day, or a hunting group spread across a large property. General guidance from the MeshCore community suggests they start earning their keep once a group has more than a couple of regular users; below that, direct messages between companion devices are usually enough on their own.