| Device Role |
Description |
Best Uses |
| CLIENT |
App connected or stand alone messaging device. |
General use for individuals needing to communicate over the Meshtastic network with support for client applications. |
| CLIENT_MUTE |
Device that does not forward packets from other devices. |
Situations where a device needs to participate in the network without assisting in packet routing, reducing network load. |
| CLIENT_HIDDEN |
Device that only broadcasts as needed for stealth or power savings. |
Use in stealth/hidden deployments or to reduce airtime/power consumption while still participating in the network. |
| TRACKER |
Broadcasts GPS position packets as priority. |
Tracking the location of individuals or assets, especially in scenarios where timely and efficient location updates are critical. |
| LOST_AND_FOUND |
Broadcasts location as message to default channel regularly for to assist with device recovery. |
Used for recovery efforts of a lost device. |
| SENSOR |
Broadcasts telemetry packets as priority. |
Deploying in scenarios where gathering environmental or other sensor data is crucial, with efficient power usage and frequent updates. |
| TAK |
Optimized for ATAK system communication, reduces routine broadcasts. |
Integration with ATAK systems (via the Meshtastic ATAK Plugin) for communication in tactical or coordinated operations. |
| TAK_TRACKER |
Enables automatic TAK PLI broadcasts and reduces routine broadcasts. |
Standalone PLI integration with ATAK systems for communication in tactical or coordinated operations. |
| REPEATER |
Infrastructure node for extending network coverage by relaying messages with minimal overhead. Not visible in Nodes list. |
Best positioned in strategic locations to maximize the network's overall coverage. Device is not shown in topology. |
| ROUTER |
Infrastructure node for extending network coverage by relaying messages. Visible in Nodes list. |
Best positioned in strategic locations to maximize the network's overall coverage. Device is shown in topology. |
| ROUTER_CLIENT |
Combination of both ROUTER and CLIENT. Not for mobile devices. |
Devices in a strategic position for priority routing that need to also serve as a standard CLIENT. |
This table shows the?default?values after selecting a preset. As always, individual settings can be adjusted after choosing a preset.
| Device Role |
BLE/WiFi/Serial |
Screen Enabled |
Power Consumption |
Retransmit |
Prioritized Routing |
Visible in Nodes List |
| CLIENT |
Yes |
Yes |
Regular |
Yes |
No |
Yes |
| CLIENT_MUTE |
Yes |
Yes |
Lowest |
No |
No |
Yes |
| CLIENT_HIDDEN |
Yes |
Yes |
Lowest |
Local only |
No |
No |
| TRACKER |
Yes |
No |
Regular |
No |
No |
Yes |
| LOST_AND_FOUND |
Yes |
No |
Regular |
No |
No |
Yes |
| SENSOR |
Yes |
No |
High |
No |
No |
Yes |
| TAK |
Yes |
Optional |
Regular |
Yes |
No |
Yes |
| TAK_TRACKER |
Yes |
Optional |
Regular |
Yes |
No |
Yes |
| ROUTER |
No |
No |
High |
Yes |
Yes |
Yes |
| ROUTER_CLIENT |
Yes |
Yes |
Highest |
Yes |
Yes |
Yes |
| REPEATER |
Yes |
No |
High |
Yes |
Yes |
No |
This setting defines the device's behavior for how messages are rebroadcasted.
| Value |
Description |
ALL |
ALL (Default) - This setting will rebroadcast ALL messages from its primary mesh as well as other meshes with the same modem settings, including when encryption settings differ. |
ALL_SKIP_DECODING |
ALL_SKIP_DECODING - Same as behavior as ALL, but skips packet decoding and simply rebroadcasts them.?Only available with Repeater role. |
LOCAL_ONLY |
LOCAL_ONLY - Ignores observed messages from foreign meshes that are open or those which it cannot decrypt. Only rebroadcasts message on the nodes local primary / secondary channels. |
KNOWN_ONLY |
KNOWN_ONLY - Ignores observed messages from foreign meshes like LOCAL_ONLY, but takes it a step further by also ignoring messages from nodenums not in the node's known list (NodeDB). |
W0AYE Ben Wussow