If you’re new to Meshtastic or just want your radio to work: leave it set to CLIENT (the default). It will send, receive, and help relay messages for others automatically. That’s the right choice for 95% of operators.
Why Device Roles Matter
When setting up your Meshtastic node, you’ll notice several device role options. For most users joining WPAMesh, CLIENT or CLIENT_MUTE is the right choice.
Router roles fundamentally change how your node behaves on the mesh. Routers are expected to be always-on, strategically placed at high elevations with excellent coverage, and they take priority in relaying messages across the network.
When too many nodes claim router status—especially portable or inconsistently powered ones—it actually degrades mesh performance rather than helping it.
Imagine a room full of people all trying to be the one who relays messages. Instead of efficient communication, you get chaos and collisions. That’s what happens when too many nodes are set to ROUTER—everyone’s shouting over each other trying to “help,” and the actual messages get lost in the noise.
The role you choose affects three things:
- Routing behavior — Whether your node relays messages from others, and with what priority
- Visibility — Whether other nodes can see you in their node list
- Power usage — How aggressively the radio sleeps to save battery
Quick Reference Table
Here’s the at-a-glance summary. The highlighted row is what most people should use:
| Role | Relays Messages? | Visible? | Coordination? |
|---|---|---|---|
| CLIENT ⭐ | ✓ Smart relay | ✓ Yes | No |
| CLIENT_MUTE | ✗ Never | ✓ Yes | No |
| CLIENT_BASE | ✓ Priority for favorites | ✓ Yes | No |
| CLIENT_HIDDEN | ~ Local only | ✗ No | No |
| TRACKER | ~ When awake | ✓ Yes | No |
| SENSOR | ~ When awake | ✓ Yes | No |
| ROUTER | ✓ Always (priority) | ✓ Yes | YES — Contact us |
| ROUTER_LATE | ✓ Always (delayed) | ✓ Yes | YES — Contact us |
| REPEATER | ✓ Always (priority) | ✗ No | YES — Contact us |
What Role Should You Pick?
Quick Recommendations
TRACKER for GPS tracking, SENSOR for weather stations or environmental monitors.Client Roles (Use These)
These are the roles for everyday use. No coordination needed—just pick the one that fits your situation.
Default
Recommended
The standard role for almost everyone. Your node sends and receives messages, and intelligently relays traffic for others when needed. It uses “smart” timing to avoid collisions—if it hears another node relay a message first, it won’t duplicate the effort.
- 📱 Handheld devices
- 🏠 Home base stations
- 🚗 Vehicle-mounted nodes
- 🥾 Hiking, biking, outdoor use
Low Impact
Same as CLIENT, but your node never relays messages for others. Use this when you’re in an area with good coverage and don’t need to contribute to the mesh relay—or when you have multiple nodes and want to reduce “self-competition.”
- 🏙️ Congested areas with many nodes
- 📡 Near a strong base station
- 🔋 Your “extra” devices
Multi-Device
Like CLIENT, but gives priority to relaying messages from nodes you’ve “favorited.” Perfect if you have an attic/roof node and want it to prioritize your handheld or mobile.
- 🏠 Your best home antenna position
- 📻 Hub for your personal devices
Want to Run a Router?
If you have a node in a great fixed location—solid power, excellent elevation, wide coverage—reach out to us! We’d love to talk about whether a router role makes sense for your setup and how it fits into the broader WPAMesh infrastructure.
Coordinated router placement is what makes a mesh network actually work well.
Punch your coordinates into site.meshtastic.org. Your proposed location should easily see 75 kilometers or more if it’s a good fit for a router role. If you’re seeing less than that, a CLIENT role will serve you (and the mesh) better.
Running a router is a commitment. Here’s what we look for in infrastructure maintainers:
- Excellent location — High elevation with wide coverage (75+ km viewshed)
- Reliable power — Always-on, with backup power or solar if possible
- Meshtastic knowledge — Well-versed in the software, ecosystem, and have a moderate understanding of RF theory
- Commitment to updates — Prepared to update firmware regularly to ensure mesh health
- Coordination — Willing to communicate with other infrastructure maintainers
We know! But don’t worry—you can still support the mesh with a non-router role device if you can’t meet all the requirements. A well-placed CLIENT node at your house still helps the network. Not everyone needs to be a router, and the mesh works better when most nodes aren’t routers.
📡 Contact the WPA Mesh Coordinators
Questions about which role to use? Think you have a good location for a router? We’re happy to help!