What Is MeshCore?

There’s a small LoRa board on your bench. Maybe a Heltec V3, maybe a RAK WisBlock. You’ve seen MeshCore mentioned in a Discord thread, or on GitHub, and the claim is something like: “flash this, and you have an off-grid radio mesh.” You want to know what that actually means before you flash anything.

This is the short version.

The mesh in two sentences

LoRa (Long Range) is a spread-spectrum radio modulation that sends small packets far and slowly, using very little power. MeshCore runs on top of LoRa hardware and handles the networking: when you send a message, nearby nodes relay it outward until it reaches the destination. Each relay is a hop, and packets can travel through a chain of them across a city or a hillside.

The network is fully decentralized. There’s no central server, no account to create, no internet path. Every node you deploy makes the coverage better for everyone nearby.

Three firmware roles

Not every node does the same job. For everyday mesh use, MeshCore defines three main firmware roles:

Companion is the firmware you run on the radio you carry. It connects to the MeshCore companion app on your phone via Bluetooth Low Energy, letting you send and receive messages. Companion nodes do not relay packets — their job is to be your radio interface, not the network’s backbone.

Repeater is a fixed node placed somewhere with line-of-sight — a rooftop, a ridgeline, a water tower. It hears everything in range and relays it onward. The higher you mount it, the more range it contributes. Repeaters are the backbone of any real MeshCore deployment; two or three well-placed repeaters can cover a neighborhood or a small town.

Room Server stores group messages. If a member is out of range when a group message is sent, the Room Server holds it. When they come back in range and sync, they get the message. This is useful for any scenario where people move in and out of coverage — field teams, neighborhoods, club nets.

Encryption, out of the box

Messages on MeshCore are end-to-end encrypted using AES-128. Direct messages between two contacts use a shared key derived from their cryptographic handshake. Public channels use a channel key. The radio traffic that travels over the air is ciphertext — repeaters relay it without decrypting.

That encryption is not a feature you configure. It’s the default state from the first packet you send.

Getting on the mesh

The practical minimum is one Companion node. Two lets you confirm you’re actually reaching another node. A Repeater in a good location converts a bench experiment into a usable network.

Flash firmware using the MeshCore web flasher — it runs in Chrome and supports most popular boards without requiring a local toolchain. Select your board, select Companion or Repeater, flash. The whole process takes about five minutes.

From there, SNR readings in the companion app and in Waev’s Live Packets view tell you whether your links are solid or marginal. That’s covered in Reading the Signal, and when your mesh outgrows the bench and needs permanent nodes, repeater placement is where the real engineering starts.

What Waev adds

Waev is a separate analytics layer, not a replacement for MeshCore firmware or the companion app. Where MeshCore handles the radio and the messages, Waev subscribes to the MQTT stream from enrolled observers and surfaces the data — live packet feeds, per-link SNR, network topology, node history. If you’re building a community mesh or running infrastructure other people depend on, the analytics layer is where you verify that the network is doing what you think it’s doing.