MeshCore room servers: a bulletin board over radio
Beginner to intermediate · A practical guide for users and operators
You may hear people call these room nodes, room servers, or simply rooms. In MeshCore, a room server is a dedicated device running room-server firmware. It acts like a small bulletin board system (BBS): people with compatible MeshCore radios can connect, post messages and come back later to retrieve posts that the room stored while they were away.
Unlike an Internet forum, a room can work over MeshCore LoRa radio without cellular service, Wi-Fi, or an MQTT broker. That does not guarantee long-distance delivery: the users still need usable radio paths to the room, directly or through compatible repeaters.
A channel is primarily live radio messaging: if your radio isn't in range when a message travels, you might miss it.
A room server holds a limited history so compatible clients can reconnect later and retrieve messages. It's closer to a small mailbox or bulletin board than a real-time chat room.
First, understand the three roles
| Role | Main job | Does it store a shared room history? |
|---|---|---|
| Companion | Connects your phone, computer or compatible handheld to the MeshCore radio network so you can send messages | No—it is your user-facing radio |
| Repeater | Forwards selected compatible MeshCore packets over RF to help messages travel farther | No—forwarding isn't the same as a room archive |
| Room server | Accepts room logins, stores posts and returns available history to users | Yes, subject to firmware and storage limits |
A room server is not an MQTT observer, an Internet message bridge, or a replacement for strategically placed repeaters. Meet the MeshCore roles and learn about MQTT observers.
Example: leaving a note for tomorrow
Imagine a small community room with two visitors.
- Alex connects from a compatible MeshCore companion radio and posts, “Trail check-in: the bridge on the west route is clear.”
- The room node receives and stores that post. Alex can now go out of range.
- Sam arrives later, establishes a radio path to the same room and logs in.
- Sam's client requests available unseen room messages. The room can supply stored posts from its limited history.
A direct channel message sent while Sam was offline would not automatically be waiting on a server. The room-server behavior is what makes the delayed retrieval possible.
The MeshCore FAQ describes returning up to 32 previously unseen messages when a client logs in. Treat that as the documented behavior of the referenced implementation, not a promise of indefinite retention or an unlimited archive. Software updates and hardware storage constraints can change what a specific room holds.
How do users find and join a room?
You need a compatible MeshCore companion—such as a Bluetooth companion paired with the MeshCore smartphone app, or a supported T-Deck—whose radio settings match the network. The client must discover or already know a reachable room server.
A typical first visit looks like this:
- Turn on your companion radio and open its supported MeshCore app/interface.
- Confirm frequency, bandwidth, spreading factor and coding rate match the local MeshCore network. Some routes may use repeaters; a room doesn't create a radio path by itself.
- Look for nearby or discovered room servers in the client's contact/discovery list. A name or advertisement alone doesn't guarantee reliable communication.
- Select the desired room and use the client's Connect / Login / Join action. The exact wording varies by platform and version.
- Enter the room's guest/access password if the operator requires one. This is not your phone's Bluetooth pairing code, the room's administrator password, or Northern Michigan Mesh's public MQTT login.
- Wait for the login/synchronization response. Read available past posts; if your access allows it, try a short test message.
- Leave range, then come back and log in again to test whether later messages are retrieved.
Can't find the room? Check whether its radio is powered and advertising, whether your device is actually on compatible RF settings, and whether a working path exists. Don't conclude the room is broken just because an online map shows an observer nearby.
Read the official MeshCore FAQ for currently supported client types. App menus evolve, so follow the labels actually shown by your installed client.
Build your own room server
What you'll need
- A supported LoRa board that has an available MeshCore room-server firmware image. Do not assume that a companion or repeater image includes room-server functionality.
- A suitable antenna, feedline and safe mounting location. Height and radio path are important even though the room stores posts.
- A reliable power source and weather protection appropriate to the installation.
- A USB cable and a computer with a compatible browser for flashing and initial configuration.
- At least one companion radio on the same compatible LoRa parameters for testing.
Verify your specific hardware against the options in the official MeshCore flasher. Make sure the firmware image says Room Server for your device model.
Step 1 — Flash room-server firmware
- Connect the board to your computer and open MeshCore's official firmware flasher.
- Select the exact hardware model and a Room Server build. Flash it using the method provided for your board.
- Reconnect to the device's USB serial/console after flashing. The official configuration interface can manage compatible repeater and room-server nodes.
- Record the installed firmware version and role. The documented CLI commands
verandget rolemay help confirm you're configuring the intended device.
Don't flash the wrong board variant, and don't disconnect power while an update is in progress.
Step 2 — Configure the radio and identity
In config.meshcore.io or a supported serial console:
- Give the room a clear name so other operators can recognize it.
- Set the radio frequency, bandwidth, spreading factor and coding rate to the legal, compatible plan you intend to use locally. A room using the wrong LoRa settings cannot talk to a companion just because both say “MeshCore.”
- Review transmit power, antenna, duty-cycle and location-advertisement settings for your device and applicable U.S. rules.
- Decide whether to advertise a precise position. Public location metadata can disclose an unattended node's site.
- Verify a nearby companion can discover or contact the room before installing it remotely.
Do not copy a fixed Northern Michigan frequency into a new device without checking your area's actual network and applicable radio rules. A geographic observer code such as GDW is not a radio frequency and is not a MeshCore forwarding scope.
Step 3 — Set separate administrator and visitor access
A room server has two separate credential concepts:
| Credential | What it's for | Who should know it? |
|---|---|---|
| Admin password | Changes device configuration and manages the room | Only trusted operators/administrators |
| Guest/room password | Lets visitors join with the access allowed by the room's configuration | The people you want to permit to visit/post |
A public room can choose to share a guest password; never publish its admin password. They should not be the same password.
The current MeshCore CLI reference documents the commands below. Enter your own strong values, not these placeholders:
# Inspect identity and current access configuration.
ver
get role
get guest.password
get allow.read.only
# Choose a private admin password and a separate room guest password.
password YOUR_NEW_PRIVATE_ADMIN_PASSWORD
set guest.password YOUR_ROOM_GUEST_PASSWORD
# Confirm the resulting settings; avoid sharing screenshots with passwords.
get allow.read.only
Defaults require care: the official FAQ mentions a historical default guest password, while the current CLI reference documents a blank default guest password. Defaults may vary with firmware/build. Inspect and set your own guest and admin passwords instead of trusting either historical default. Some installations may also ship with a known default administrator password—change it before public use.
Step 4 — Choose who may read and who may post
You may want a room where visitors can read announcements but only approved people can write posts.
MeshCore supports an allow-read-only setting and companion-specific access permissions. The official CLI reference documents:
# See whether the room is configured to allow read-only access.
get allow.read.only
# Example: enable the firmware's read-only login option.
set allow.read.only on
# Inspect the current access list (serial console).
get acl
For more detailed per-client access, the documented setperm command accepts a companion's public key and a permission level:
| Permission | Numeric value |
|---|---|
| Guest | 0 |
| Read-only | 1 |
| Read-write | 2 |
| Admin | 3 |
For example, an operator may choose a read-only permission for a known companion's public key:
# EXAMPLE ONLY — replace with a real authorized companion public key.
setperm YOUR_COMPANION_PUBLIC_KEY 1
Security warning about blank guest passwords: a publicly reported MeshCore issue describes a combination of read-only enabled plus blank guest password that granted unexpectedly broad posting access in the affected build. Do not assume set allow.read.only on alone makes a public room safe. Use a deliberate nonblank guest password for write access where appropriate and test both an unauthenticated visitor and an authorized poster with your exact firmware version before advertising a room as read-only. See the upstream issue. Access-control behavior may change as firmware is fixed.
Step 5 — Test the complete experience
Start on a desk before putting the room on a tower or remote site:
- Use a companion radio to discover and log into the room.
- Post a harmless test message with an account that should be allowed to write.
- Disconnect that companion.
- Have another authorized user connect, retrieve history and verify that the message appears.
- Test a visitor who is read-only and ensure their post attempt actually fails.
- Go out of RF range, return, and see which messages are synchronized.
- Reboot the room and verify whether available history and settings persist as your firmware promises.
- Test with the Internet unavailable to confirm the path relies on RF alone, if that's the intended deployment.
A success in one step doesn't guarantee the others: discovering a room, authenticating, posting and retrieving history are separate operations.
Should a room server also act as a repeater?
Usually not. The MeshCore FAQ specifically recommends separate room-server and repeater devices. A room-server build may offer a repeat option, but does not necessarily have the full feature set of dedicated repeater firmware.
For new deployments, keep the room's primary job storing and serving posts. Use a suitable, separately configured repeater if you need to expand RF reach. Putting both roles on one radio may introduce complications and competing airtime demands.
Some firmware exposes get repeat and set repeat on|off. Check your build's current setting; if you intentionally want a dedicated, non-repeating room server, you can use set repeat off where supported. Don't change a shared installation's repeat behavior without understanding whether anyone currently relies on it for RF coverage.
Room servers versus the Northern Michigan Mesh forum and MQTT
| Feature | MeshCore room server | Web forum / Discourse | MQTT observer feed |
|---|---|---|---|
| How to reach it | Compatible MeshCore RF path | Browser with an Internet/IP path | Authorized MQTT/IP connection |
| Main purpose | Small shared store-and-retrieve radio message board | Full-featured asynchronous online discussions | Reporting heard packets and node status |
| Can work with no Internet? | Yes, when compatible RF paths and power exist | Not through the public Internet service | Not through our public Internet-reached broker |
| Same credentials? | No: room access is configured by its owner | Forum account | Dedicated MQTT account |
| Guaranteed archive? | No: bounded device storage / firmware behavior | Depends on forum service and backups | No: an observer report is not a room mailbox |
Our public CoreScope observations dashboard and MQTT observer guide are useful monitoring resources. They are not a public room-server directory, and seeing a node on a map doesn't guarantee that you can connect to its room.
Common problems and where to look
| Problem | Check first |
|---|---|
| Room doesn't appear in the app | Wrong firmware role, incompatible radio parameters, no adverts heard, poor RF path, stale discovery/contact list |
| Room appears, but login fails | Guest password, outdated contact, insufficient RF link, clock mismatch, or client/firmware compatibility |
| Can read, but can't post | Read-only permissions, guest password and per-companion ACL; this can be intentional |
| Visitor can post when they shouldn't | Test the read-only/blank-guest-password behavior; inspect firmware and ACL immediately |
| Messages aren't retrieved on return | History/sync timing, storage limits, firmware changes, room reboot, or missing RF return path |
| Users have different history | Different visit times, sync state and history limits; do not assume a globally synchronized archive |
| Room works nearby but not elsewhere | RF coverage, antenna placement, repeaters and routing; MQTT alone doesn't fix the radio path |
A small, worthwhile first project
Try a local bulletin-board experiment before deciding to host a region-wide service: configure a room on a supported board, let two trusted companion users post and return later, and verify the actual history and access behavior. Document the radio parameters, room firmware, antenna placement, number of messages retrieved and who could read/write.
That gives you reproducible observations to share on the Northern Michigan Mesh forum without suggesting that every operator must use the same room, frequency, scope or governance rules.
Official sources and further learning
- MeshCore FAQ: role comparison, room servers and message history
- Official MeshCore flasher
- Room-server and repeater configuration interface
- Official CLI reference: password,
guest.password,allow.read.only,setperm - MeshCore configuration web UI source and access overview
- Read-only blank-guest-password edge case reported upstream
- Our location codes and RF scope explanations
Next: MeshCore overview · MeshCore MQTT observers · Northern Michigan Mesh forum.