Skip to main content

MeshCore: understanding the pieces before flashing a device

What problem does it solve? MeshCore is a LoRa-based communications system that supports messaging through compatible radio devices, including devices acting as companions, repeaters and room servers.

MeshCore and Meshtastic may run on similar hardware, but their on-air protocols are not directly interchangeable. Having the right brand of radio board alone does not make two devices compatible.

What do the different firmware roles mean?​

MeshCore uses firmware tailored to different jobs. A beginner should understand that role choice changes what the device does.

RolePlain-English descriptionA typical reason to use it
Companion radioA radio linked to an app or computer that lets a person send and receive messagesYou want to type messages and talk to other compatible MeshCore devices
RepeaterA station that forwards certain MeshCore messages to extend communication pathsYou want to build a useful shared relay at a suitable location
Room serverA message-storage service that lets participating users retrieve stored postsYou want a place to leave and later retrieve community messages

Firmware options and hardware support can evolve, so check the project's current documentation before choosing an image to flash.

How a message might travel​

Suppose a companion at a cabin can't reach another companion directly. A correctly positioned and configured repeater may be able to hear and help forward messages between them. MeshCore's routing behavior is determined by its protocol; it should not be assumed to rebroadcast every packet.

A room server plays a different role: rather than only forwarding messages as they pass, it stores certain messages for later retrieval. Our new MeshCore Room Servers guide walks through joining a room, flashing room-server firmware, setting visitor and administrator access, testing stored-message retrieval, and safely operating a room node.

Why location matters more than simply adding devices​

Imagine a repeater hidden in a metal shed at the bottom of a valley. It might have excellent firmware but still be a poor relay because the surrounding terrain and building reduce radio coverage. Evaluate the antenna, feedline, mounting height, placement and available power before expecting a repeater to fix a range problem.

Settings you may be asked to configure​

  • Frequency: selects the radio channel's center frequency. Use an authorized frequency supported by your hardware and applicable regulations.
  • Bandwidth, spreading factor and coding rate: LoRa parameters that influence link reliability, speed and airtime. Devices need compatible settings for a usable LoRa link.
  • Name and role: describe how a device identifies and behaves in the network.
  • Keys and passwords: may control message access and device administration. Treat administrator credentials like passwords, not public information.
  • Position: useful for some maps, but not required for learning and may expose a private location.

We won't prescribe arbitrary settings for everyone. A configuration that fits one area's deployment may be wrong for your independent experiment.

Regions and scope filtering: what beginners should know​

MeshCore region scopes influence which flooded packets repeaters rebroadcast. This can conserve airtime, but restrictive policies can leave newcomers unable to get messages through the network. Do not confuse MeshCore radio scopes such as mi-central with IATA-style observer location codes such as GDW. An observer code groups reporting/MQTT data; it does not set RF forwarding permissions.

Read our balanced, beginner-first guide: Observer Location Codes, MeshCore Regions, and Scoping. It explains the benefits, common misconceptions, unscoped traffic, and why clear onboarding matters.

Room servers: bulletin-board messages over RF​

Unlike a normal channel message that may be missed while someone is out of range, a room server stores a limited set of posts for a visitor to collect on a later login. It's particularly interesting for small community bulletin boards, asynchronous field updates and experiments with off-grid communications.

A room server is not an MQTT observer and does not require our broker or Internet connectivity to do its core job. The official MeshCore guidance recommends separate devices for room-server and repeater roles. We cover the differences and practical access controls in Room Servers: Build & Use.

Connecting a MeshCore MQTT observer​

Our independent Northern Michigan Mesh MQTT broker has accepted MeshCore observer packet and status reports. We've documented the complete MQTT Server URL (mqtts://mqtt.northernmichmesh.org:8883), county-based observer reporting codes, firmware selection, setup steps and connection checks in MeshCore MQTT Observer Setup. Choose the reporting region for your observer's actual county using the Northern Michigan region map.

An observer is a monitoring/reporting device, not automatically a repeater or an Internet bridge between remote RF meshes. No observer should be required to publish to anyone else's broker in order to participate in the radio network.

Practical questions before building a repeater​

  1. Who needs to talk to whom, and can any of the devices hear one another now?
  2. Would a better antenna location likely help?
  3. Is the repeater hardware supported by the current firmware?
  4. Is the power supply suitable for unattended service?
  5. What monitoring, physical access, equipment weatherproofing and privacy decisions are necessary?
  6. If an Internet gateway is added, what data will it forward and who can see it?

Common misunderstanding​

“A repeater is always better than a companion.” They're designed for different uses. If you want to send messages from your phone, a companion may be the appropriate starting role. A repeater is infrastructure, not a mandatory first purchase.

Official resources​

Have a different approach or disagree with an example? Talk about it in our forum. Questions are welcome.