Not amateur radio
Device roles
Which nodes relay, which stay quiet, and why that choice shapes the whole mesh.
Not amateur radio
Which nodes relay, which stay quiet, and why that choice shapes the whole mesh.
Every Meshtastic node has a role, and the role mostly answers one question: does this node repeat other people's packets, and how eagerly? A role also sets what the node prioritizes and whether it sleeps. A plain client repeats a packet only when no other node has already done so, which is the listening behavior in Managed flooding. Infrastructure roles repeat regardless.
| Role | What it does | Relays? | Good for |
|---|---|---|---|
| Client | App-connected or stand-alone messaging device | Yes, when no other node has already | Everyday personal use |
| Client mute | Takes part but does not forward others' packets | No | Adding no routing load |
| Client base | Personal base station: always rebroadcasts packets to or from its favorited nodes, other packets like a client | Always for favorites | A well-placed attic or roof node that helps your own weaker nodes |
| Router | Infrastructure that always rebroadcasts once, and is shown in topology | Always, once | Strategic spots that extend coverage for everyone |
| Router late | Infrastructure that always rebroadcasts once, but only after the others | Always, once, last | Dead spots, or a cluster where placement does not help the wider mesh |
| Tracker | Sends position packets as priority | Only while awake | Following people or assets |
| Sensor | Sends telemetry packets as priority | Only while awake | Remote environmental readings |
Other roles exist for specific jobs, and some older ones are retired; the device configuration page keeps the current list.
Each rebroadcast uses shared airtime, so more relaying is not automatically better. The documentation points infrastructure roles at well-positioned nodes, and offers a mute role for devices that should join the mesh without adding to the load. A tracker or sensor can sleep between reports when power saving is on, and the comparison table lists it as relaying only while awake.
Router roles also use more power than a client, and the documentation notes that the router role enables power saving by default on one hardware family. That fits the documentation's advice to put them in strategic locations.
A separate rebroadcast mode setting chooses which packets a node repeats, for example ignoring traffic from other meshes it does not belong to. It works alongside the role, not instead of it.