Flash and configure a room server¶
Confirm that the official flasher supports your exact board as a room server, then back it up, flash it, secure access, and test it with a companion.
Before you erase¶
Erase Flash deletes stored room-server data
Erasing can remove the device identity/private key, room data, guest and admin access, name, radio settings, and other saved configuration. Back up anything you need before continuing.
For an existing device, record the board, firmware version, name, role, radio settings, and access configuration. Export or securely record the private key with a supported tool. Store passwords in a password manager and never place them in screenshots, issues, or chat.
If room history or identity cannot be backed up and must be retained, stop before erasing.
Before you start¶
- [ ] The exact board and Room Server role are confirmed.
- [ ] Existing identity, room data, and settings are backed up where supported.
- [ ] A known-good data USB cable and stable power are available.
- [ ] I am using a current browser with Web Serial support, such as Chrome or Edge.
- [ ] I checked the local community page for radio-setting overrides.
What flashing changes¶
Flashing replaces firmware and Erase Flash can delete identity, room data, access settings, and radio configuration. Setup writes guest/admin access, name, and local radio settings.
Recovery plan¶
Keep the exact board's USB recovery method, backed-up identity/settings, a known-good cable, and the verified Room Server artifact available before erasing. If flashing fails, return the same board to DFU mode and retry the same verified target; do not switch board files.
Flash the firmware¶
- Open the official MeshCore Web Flasher.
- Select the exact device model.
- Select Room Server and the intended version for that board.
- Click Enter DFU Mode and wait for the expected device to appear.
- Recheck the hardware and role selections.
- Click Erase Flash and wait for a successful erase message.
- Click Flash and wait for completion before disconnecting.
If flashing fails after erase, leave the device connected, refresh the flasher, re-enter DFU mode, confirm the board and role, and retry Flash. Use the board's documented USB recovery process if it is no longer detected.
Check the flash¶
The flasher reports completion, the device restarts as a Room Server, and Configure via USB can reconnect. Otherwise use the recovery plan before setting access details.
Configure the Room Server¶
- After flashing, click Configure via USB.
- Select the room server's serial device and connect.
- Set a descriptive name that does not expose a private location.
- Set separate, unique guest and admin passwords and store them securely.
- The guest password is shared with people who should enter the room.
- The admin password controls management access and should not be shared as the guest password.
- Check the local community page for different settings. If none are listed, use the Canada defaults: USA/Canada (Recommended) (
910.525 MHz / 62.5 kHz / SF7 / CR5). - Save settings and reboot.
Make sure it works¶
- Reconnect to the console after reboot and confirm the name, role, and radio settings.
- Send an advert.
- Confirm a companion discovers the Room Server.
- Log in from the companion with the guest password.
- Confirm the intended room behavior, then reboot once more and verify the settings persist.
Do not deploy the server remotely until USB recovery, admin access, discovery, and guest access all work on the bench.
Recovery and undo¶
If discovery, guest access, admin access, or persistence fails, keep the server local and reachable by USB. Restore the backed-up identity/settings where supported or reflash the exact Room Server target by USB, then repeat verification. Do not deploy a server whose access path or recovery is uncertain.
What's next¶
After the server survives reboot and access checks, find the local community and document who maintains the room and its recovery record.