Skip to content

Search guides, devices and posts

Back to MeshCore

MeshCore Room Server Guide

Room servers add store-and-forward messaging to your MeshCore network. Members can go offline and come back later to read messages they missed, like a community bulletin board that works without internet.

This guide covers what room servers do, when your network needs one, and how to set one up from scratch.

Checked October 2026 against MeshCore 1.18.0.

What is a Room Server?

A room server is a MeshCore device that stores messages and delivers them to users who weren't online when the message was sent. Without one, a channel message works like a walkie-talkie call: if your radio isn't in range when it goes out, you miss it.

A room server keeps the most recent posts (32 of them) and pushes the ones you haven't seen when you log in. You can log in from anywhere on the mesh that can reach it, not just next to it. The MeshCore FAQ compares it to an email server: you come back later and collect what you missed. Think of it like a community bulletin board: members post, and everyone reads at their own pace.

Room servers are especially valuable for groups that aren't all online at the same time: farming operations that check in at different times of day, volunteer fire departments where members are on different schedules, or hunting groups spread across a large area.

How It Differs From Other Node Types

Repeater : relays messages in real time but doesn't store them. If the recipient isn't online, the message is lost.
Room Server : stores posts and delivers them later. Offline members get caught up when they log in again. It doesn't relay other traffic.
Companion : your personal device. Logs in to room servers to read and post messages.

Real-World Analogy

A repeater is like a megaphone: it amplifies the message right now. A room server is like a whiteboard in a break room: messages stay posted for people to read when they walk by, even hours or days later.

When Do You Need a Room Server?

Community Mesh Networks

Any network with several regular users benefits from a room server. It becomes the central coordination point. Post updates, share information, and coordinate without needing everyone online simultaneously.

Event Coordination

County fairs, festivals, community events. A room server lets organizers post updates that volunteers and attendees can check at their own pace throughout the day.

Farm & Ranch Operations

Coordinate across large properties where workers check in at different times. Post irrigation updates, equipment locations, or daily task lists that everyone can read when they're near a node.

Emergency Communications

Volunteer fire departments, severe weather coordination, search and rescue. A room server ensures critical messages aren't missed when members are out of range temporarily.

Minimum network size: A room server is most useful when you have at least 3-5 regular users. With only 2 people, direct messaging between companions is usually sufficient. As your network grows, a room server becomes increasingly valuable.

Hardware Requirements

Room servers use the same hardware as companions and repeaters. The key difference is that room servers should be always-on with reliable power, since they need to be available to store and deliver messages.

Any Supported Device

Heltec V3, T-Beam, RAK WisBlock, and Station G2 all work as room servers. No special hardware needed.

Reliable Power

Wall power is strongly recommended. A room server that goes offline loses its value. Battery backup is a nice-to-have for power outages.

Good Location

Place where it can reach the most users. A room server at a central, elevated location serves the widest audience. A room server doesn't relay other nodes' traffic, so pair it with a repeater for reach.

Step-by-Step Setup

1

Flash Room Server Firmware

  1. a Visit the MeshCore Flasher in Chrome or Edge
  2. b Connect your device via USB
  3. c Select your device from the list
  4. d Choose the Room Server role
  5. e Pick the version, press Flash! and wait for it to finish. Our firmware guide covers each step.
2

Configure Passwords

Room servers have three levels of access. Set the passwords over USB while you do the radio settings in step 3 (the flasher's Console or Repeater Setup page, or config.meshcore.io), or later from the MeshCore app after logging in as admin. Passwords can be up to 15 characters.

Admin Password Change it

Full control: settings, the command line, the access list, reboots. The default is password, so change it with password <new-password>. Keep it to server operators only.

Guest Password Recommended

Read and post. Share it with the people who should be able to post. Most builds ship with hello (the MeshCore FAQ's default), so set your own with set guest.password <password>. If the guest password is blank, anyone can log in and post.

Read-Only Access Off by default

With set allow.read.only on (the Read Only switch in the app), anyone who logs in without the right password can read posts but not post. Good for public announcement boards. While it's off, a wrong password simply fails to log in.

Tip: For community room servers like NodakMesh, a guest password shared on Discord works well. This keeps the room accessible to community members while preventing spam from unknown devices.

3

Configure Radio Settings

The room server must use the same radio settings as the rest of your network. A freshly flashed room server starts on the European default (869.618 MHz, 62.5 kHz, SF8), so in the US you have to change it over USB before your companion can reach it. MeshCore's recommended US settings:

Frequency 910.525 MHz
Bandwidth 62.5 kHz
Spreading Factor / Coding Rate SF7 / CR5

In the flasher's Console, run set radio 910.525,62.5,7,5, then reboot (radio changes apply after a restart). While you're there, set name <name> gives it a name people will recognise, and set lat / set lon put it on maps.

Important: If the room server's frequency, bandwidth or spreading factor don't match your network's companions and repeaters, it won't be discoverable. Match the coding rate as well, so it can't be the cause of a problem. If your local mesh or country uses a different preset, copy the settings from your companion instead.

4

Connect and Verify

Use a companion device to test your room server:

  1. 1 Discover the room server: Open the MeshCore app on your companion device. The room server appears in your Contacts once your companion hears its advert. The 2-minute zero-hop adverts a new install sends stop once you've saved a setting, and the automatic flood advert only goes out every 47 hours, so run advert on the room server after setup to send a flood advert across the mesh.
  2. 2 Log in to the room: Tap the room server in Contacts, enter the guest password on the Room Login screen and log in. The app can remember the password.
  3. 3 Send a test message: Post a message to the room. The room server acknowledges it, and it's stored for everyone else who logs in. The app limits room posts to 150 characters.
  4. 4 Test store-and-forward: Turn off your companion and have someone else post to the room (or, over USB, run room.post <text> on the room server to add a test post). Turn your companion back on and open the room again, logging in if asked. The posts you missed should arrive.

Administration

Managing Users

Control access by sharing or changing the guest password. Admins can also set or remove one user's access with setperm <pubkey> <0-3> (Access Control in the app). Rotate the guest password if it gets shared too widely. People already logged in keep access until the room server restarts, because only admin logins are saved.

Monitoring Health

Check on your room server periodically. Log in as admin and open Status in the app for battery, uptime, airtime, the last signal heard and how many messages have been posted. A screen, if the board has one, only shows its name, radio settings and firmware version. Over USB, stats-core, stats-radio and stats-packets give the detail.

Remote Management

Log in as admin from the MeshCore app and you can change settings and run commands over the mesh. The phone apps add a short wait before each remote session unless you buy Remote Management; the desktop apps are fully unlocked. Ethernet builds (a RAK4631 with the RAK13800 module) also take commands over TCP port 23. The MeshCore CLI can log in through your companion too.

Room Server + Repeater Combo

A common question: "Can I make one device both a repeater and a room server?" The short answer is no. Each device runs one firmware type, and room server firmware doesn't relay: in 1.18, set repeat on only replies that repeat is deprecated. You get the same result by running two devices at the same location, which is also what the MeshCore FAQ recommends.

When to Combine

  • You have a good elevated location with power
  • You want both coverage extension and message storage
  • The location serves as a community hub (town center, farm shop, fire station)

Dual-Device Setup

Run a repeater and room server side-by-side at the same location:

Device 1: Repeater firmware with an external antenna mounted high for max coverage
Device 2: Room Server firmware, which can use a stock antenna indoors and focuses on message storage

Both share the same power source but run independently. Total cost: $40-60 for two Heltec V3 devices.

Troubleshooting & FAQ

Room server not discoverable

Verify radio settings match your companion device (frequency, bandwidth, spreading factor) with get radio. Make sure the room server firmware (not companion or repeater) is flashed. Check that the device is powered on and the antenna is connected. Once it's configured it sends no zero-hop adverts unless advert.interval is set, and floods one only every 47 hours, so send a flood advert with advert. If its clock is wrong, apps can ignore its adverts; check it with clock.

Can't post messages (permission denied)

If the app says you don't have permission to post, or hides the message box, you're logged in read-only: read-only mode is on and the password you used wasn't the guest password. Log in again with the guest password from the room server operator. If you're the operator, check it with get guest.password.

Old messages not loading

A room server only keeps the 32 most recent posts, and each new post replaces the oldest. When you log in, it pushes the posts you haven't received yet, up to those 32, so anything older is gone. The app keeps the room messages it has already received on your phone. Posts are stamped with the room server's clock, so if new posts stop arriving after it restarted, check its clock with clock and fix it from the app with Sync Clock.

How many messages can a room server store?

32 posts, on every board. That's the firmware's default (MAX_UNSYNCED_POSTS), and the MeshCore FAQ says a client receives up to 32 unseen messages when it logs in. Each post can be up to 151 characters, and the app limits them to 150. Posts are stored in RAM, so they're lost if the device loses power (another reason to use reliable power with battery backup).

Can I run multiple room servers?

Yes. Each room server is independent. They don't sync with each other. Multiple room servers let you create topic-specific rooms (e.g., one for general chat, one for emergency comms, one for a specific area). Users join whichever rooms are relevant to them.

What happens if the room server loses power?

Stored posts are lost (they're in RAM, not permanent storage). Its settings, passwords and identity are saved, so it restarts cleanly and begins accepting new posts. Only admin logins survive a restart, so everyone else has to log in again. This is why wall power with a UPS or battery backup is recommended for important room servers.