Meshtastic nodes offer several modes tailored to different communication needs. Here, we’ll cover the primary modes—Client, Client_Mute, and Router—to help you understand when and why to use each one.
Client Mode
Client Mode is designed for general-purpose use. In this mode, the node serves as both a user device and a network participant, actively communicating with other nodes and acting as a limited relay to expand network reach.
Best For:
- Home base stations or mobile nodes that should participate in mesh coverage expansion.
Client_Mute Mode
Client_Mute Mode is similar to Client Mode but with one key difference: the node doesn’t forward messages from other nodes. This reduces power consumption and minimizes network traffic, making it ideal for users who only need to send and receive messages without supporting mesh relaying.
Best For:
- Handheld units that aren’t in ideal positions to relay messages to the mesh. This mode conserves battery and leaves message relaying to nodes with greater reach.
Router Mode
Router Mode is optimized for nodes positioned to relay messages across the network. In this mode, the node doesn’t serve as a user endpoint but functions as an infrastructure piece to strengthen connectivity and range, making it ideal for fixed nodes that bridge communication gaps in large or challenging environments.
Best For:
- Strategic locations with excellent coverage to enhance network connectivity. Use Router Mode sparingly—avoid configuring home base stations as routers—and ensure the node has sufficient power capacity to handle large message volumes.
Note: When an ESP32 node is configured in Router Mode, Power Saving is automatically enabled and cannot be turned off. This means the node will show as “sleeping” when connected via Bluetooth, and Wi-Fi will be disabled to preserve power.
Leave a comment