MeshCore Components: Companion, Repeater, & Room Server.

A stand-alone T-Deck vs, the android phone companion app.

Companion, Repeater, and Room Server

MeshCore is built around a small set of components that work together to enable messaging over a mesh network. Each component plays a distinct role, but they are designed to complement one another. Understanding these roles makes it much easier to see how MeshCore supports communication even when devices move in and out of range.

The Companion is the most user-facing part of MeshCore. It is typically a smartphone running the MeshCore app that connects to another device such as a Heltec V4 —using Bluetooth Low Energy (BLE). It can also be a stand-alone device like the T-Decl Plus pictured above.

The Companion’s primary purpose is to provide a familiar and easy-to-use interface. Instead of interacting directly with a small screen or physical buttons, users can read and write messages, browse conversations, and manage settings from their phone. The Companion does not usually participate directly in the mesh network itself; instead, it acts as a bridge between the user and the MeshCore-enabled device that is handling mesh communication.

In simple terms, the Companion is how most people use MeshCore. It focuses on usability and accessibility rather than network coverage.

A Repeater extends the reach of the mesh network. Its job is straightforward: receive messages from one device and forward them to others.

Repeaters are typically placed in fixed or strategic locations to help messages travel farther than they could otherwise. For example, if two users are too far apart for their devices to communicate directly, a Repeater positioned between them can relay messages so communication still works.

I personally run 3 repeaters. 1 at home and 2 solar powered repeaters outdoors.

Repeaters do not usually store messages long-term or provide user interfaces. They are designed to be reliable, low-maintenance, and always on. By adding more Repeaters, the mesh network becomes stronger and more resilient, allowing messages to find alternate paths if one route is unavailable.

A helpful analogy is a relay runner: the Repeater doesn’t create the message or read it—it simply helps pass it along.

A Room Server adds persistence to the mesh network. While normal mesh messaging works best when users are connected at the same time, a Room Server allows conversations to continue even when users go offline.

Room Servers store messages and deliver them later when users reconnect. This means:

  • Users can leave the network and come back later.
  • Messages sent while they were away are not lost.
  • Conversations feel more like email or forum posts than live chat.

Room Servers are especially useful for roaming users, low-connectivity environments, or groups that do not expect everyone to be online at the same time. When a client connects to a Room Server, it automatically receives a set number of recent, unseen messages so the user can quickly catch up.

In addition to storing messages, Room Servers can be managed remotely using authorized devices or a Companion-connected smartphone.

These components are most effective when used together:

  • Companions provide an easy and familiar way for people to interact with the system.
  • Repeaters expand coverage and improve reliability across distance and terrain.
  • Room Servers ensure messages are not lost and can be retrieved later.

A small setup might only use Companions and direct device-to-device messaging. As the network grows or users become more mobile, adding Repeaters improves reach. When message history and delayed delivery become important, a Room Server completes the system

Tags: , , ,

Was this helpful?