Device Roles for Meshtastic Network

Here’s a breakdown of the frequently-used Meshtastic node roles:

1. Client (Most frequently used)

• If you are sure, choose Client mode.
• App connected or stand alone messaging device. Rebroadcasts packets when no other node has done so.
• General use for individuals needing to communicate over the Meshtastic network with support for client applications.

Variation:

• Client_mute: Device that does not forward packets from other devices.
• Client_hidden: Device that only broadcasts as needed for stealth or power savings.

2. 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.

Variation:

• Lost_and_found: Broadcasts location as message to default channel regularly for to assist with device recovery.
• Tak: Optimized for ATAK system communication, reduces routine broadcasts.
• Tak_tracker: Enables automatic TAK PLI broadcasts and reduces routine broadcasts.

3. 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.

4. Router

• Infrastructure node for extending network coverage by always rebroadcasting packets once. Visible in Nodes list.
• Best positioned in strategic locations to maximize the network’s overall coverage. Device is shown in topology.

Variation:

• Router_late: Infrastructure node that always rebroadcasts packets once but only after all other modes, ensuring additional coverage for local clusters. Visible in Nodes list.

5. Repeater

• Infrastructure node for extending network coverage by always rebroadcasting packets once 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.