Setting up your Meshtastic network requires careful consideration of each device's Role, as this is crucial for optimizing performance and ensuring reliable communication. Choosing the correct Role can enhance network efficiency, while selecting the wrong one may lead to congestion and poor performance. A device's Role defines its primary function within the network and is designed for specific usage, aiding in the effective management of network behavior. Here are some common device roles to consider.
Client
The de facto role for devices in Meshtastic is the CLIENT role, which is a flexible and general-purpose option that meets the needs of most use cases. When uncertain about which role to choose, sticking with the Client role is a safe bet.
Although the term "Client" may carry some negative connotations in certain technological contexts, it's important to note that Clients in Meshtastic do repeat and route messages. Unfortunately, this has previously led to confusion, causing some individuals to mistakenly select the ROUTER role.
Client Mute
The CLIENT_MUTE role is similar to the CLIENT role but differs in one important aspect: it does not repeat or route messages. This role is perfect for devices meant to be used in areas with high network traffic, where additional message routing could lead to congestion. By utilizing the CLIENT_MUTE role, you can ensure that the device only sends and receives its own messages without adding to network traffic.
This role is also highly recommended for mesh enthusiasts with multiple devices. Designate one device as a CLIENT and set the others to CLIENT_MUTE to manage your airtime usage more responsibly.
Router and Repeater
What are Router and Repeater?
The ROUTER role is designed for devices that primarily route messages to other devices within the mesh. This role is suitable ONLY for stationary devices positioned in extremely strategic locations, acting as unofficial hubs for routing packets. Routers enhance the mesh's range and reliability by relaying messages from other devices, effectively cutting in line before other nodes have the chance to rebroadcast a message. Unlike most other roles, Routers always rebroadcast, while others may skip this step if they detect a nearby node rebroadcasting first.
Another key behavior of Routers is their focus on power conservation; they attempt to sleep as much as possible and send telemetry packets less frequently than other devices. This is because their primary function is to route others' traffic rather than generating their own messages.
The REPEATER role functions similarly to the ROUTER role regarding packet routing, but it takes an additional step by completely turning off any broadcasted traffic, such as telemetry. Repeaters only respond to packets from other nodes and do not originate messages.
What constitutes a strategic location?
When evaluating sites for these roles, consider a tower on a mountain peak rather than a tall building. By designating a device as a Router or Repeater, you are implicitly opting for the entire mesh to prioritize that node for rebroadcasts from any direct neighbors. This strategic placement is crucial for maximizing packet delivery to the broadest possible audience. It's advisable to use line-of-sight viewshed survey tools to determine optimal locations, but the best selection can often be made by collecting real-world data on the mesh first.
Consequences of Incorrectly Assigning Router and Repeater Roles
Increased Rate of Packet Collisions
Because Routers and Repeaters always rebroadcast, deploying too many of these roles in close proximity can result in multiple devices rebroadcasting packets simultaneously. This creates higher noise levels and increases the rate of packet errors, which often culminates in sporadic delivery failures.
Decreased Overall Range
An improperly located Router can prematurely consume hops from packets passing through it. This leads to inefficient routing, as packets might use up a hop before they reach more strategically placed nodes. For instance, deploying many Routers in a valley can consume all available hops before a packet can reach a destination located at a peak above the valley, drastically limiting the overall range.
Asymmetrical Links
Similar to the problem of decreased range, poorly placed Routers can result in asymmetrical communication. In this scenario, one subset of the mesh might be able to send messages to another group, but that group would struggle to respond due to the premature consumption of hops by the improperly placed Routers. Users may attempt to mitigate this issue by increasing the hop limit, which ironically further exacerbates congestion by consuming more airtime.
Sensor
The SENSOR role is designed for devices that primarily gather and transmit sensor data. While these devices still participate in routing messages for others, they prioritize sending their own telemetry data to the network, even during periods of high channel utilization. This role is particularly suited for applications such as environmental monitoring, weather stations, or any scenario where the primary function of the device is to collect and report telemetry.
When using the SENSOR role in conjunction with power.is_power_saving, the device will attempt to sleep between intervals of transmitting environmental telemetry. This combination significantly extends the runtime of devices leveraging these settings.
Tracker
The TRACKER role is intended for devices primarily focused on tracking the location of assets, vehicles, or individuals. Devices assigned this role periodically send their GPS coordinates to the network using Position packets, which have a higher priority to ensure more reliable location tracking. While Trackers also participate in routing messages, their main objective is to deliver timely location data, even during times of high channel utilization.
By utilizing the TRACKER role along with power.is_power_saving, the device will attempt to sleep between intervals of sending position data. This combination helps significantly extend the runtime of devices employing these settings.
Conclusion
Selecting the appropriate device role is essential for the performance and reliability of your Meshtastic network. By comprehending the distinctions between the various roles, you can optimize your network configuration to suit your specific needs, ensuring efficient communication among all devices. For more detailed technical information about each role, please visit the device configuration documentation.
