Choose a MeshCore role¶
Choose a role based on the job the device will do.
| Role | Use it for | Relays mesh traffic? | Usually | Setup |
|---|---|---|---|---|
| Companion | Send and receive messages | Normally no | Mobile; often pairs with a phone | Set up a companion |
| Repeater | Improve local coverage | Yes | Fixed with continuous power | Set up a repeater |
| Room server | Keep a shared room available | Can, but not recommended | Fixed with continuous power | Set up a room server |
| Observer | Send heard network data to CoreScope | No | Fixed; requirements vary | Set up an observer |
Role details¶
Companion nodes are the small personal devices (handheld or portable) that let a user connect to the mesh.
- Run on battery or USB power.
- Usually pair with a smartphone over Bluetooth for messaging.
- Standalone options like the T-Deck include a screen and keyboard, but we don't recommend them for beginners since the firmware is still rough.
- Normally do not route packets. Client repeat is a limited off-grid feature; leave it off on an established public mesh unless local guidance says otherwise.
Repeaters are fixed installations, typically mounted at elevation (rooftop, tower, mast), that extend range and link mesh segments.
- Run continuously on mains or solar power. Most Ottawa repeaters operate on solar.
- Form the recommended routing backbone for an established mesh.
Room servers run specialized firmware that functions like a persistent chat room or mini-BBS.
- When a companion connects, it can retrieve up to 32 unseen messages, similar to checking an inbox.
- Can repeat, but this is not recommended. Ottawa keeps repeat disabled on room servers and uses separate repeaters.
- Lack several repeater and remote-administration features. Use them as shared message rooms, not as network repeaters.
New to MeshCore? Start with a companion. Before buying or flashing, confirm that the setup guide supports your device.
If none of these roles fits, ask the community before buying hardware.