The ROUTER Role

What the ROUTER role does, when it makes sense — and why you almost certainly should not use it.

Table of contents

What is the ROUTER role?

ROUTER is an infrastructure role. A router always rebroadcasts every packet it hears exactly once, and other nodes prefer to route their traffic over it. It is meant for permanently installed nodes on mountains, towers or high rooftops that cover a whole region.

A router is not a way to improve reception for your own nodes at home.

How ROUTER behaves

Property ROUTER CLIENT (default)
Rebroadcasts packets Always, once Only if no one else did
Preferred for routing by others Yes No
Visible in node list Yes Yes
Bluetooth / Wi-Fi / Serial Off by default On
Screen Off On
Power consumption High Regular

On ESP32 devices the ROUTER role switches power saving on permanently and it cannot be turned off. Because Bluetooth is disabled, you can no longer connect with the phone app in the normal way — for maintenance you need an admin channel or a USB connection.

When is a ROUTER justified?

All of the following must be true:

  1. The node is at an exposed, elevated site with wide coverage (mountain, mast, high roof).
  2. It runs 24/7 with reliable power (mains or properly sized solar).
  3. It closes a coverage gap that no existing router already covers.
  4. The local community agrees that the node is needed.

If even one point does not apply, ROUTER is the wrong choice.

Why too many routers hurt the mesh

LoRa is a shared, very slow radio channel. Every router repeats every packet, so each extra router multiplies the traffic on the air:

  • More collisions — packets are lost instead of delivered.
  • Longer delays, because the channel is busy.
  • Real messages get crowded out by duplicated traffic.
  • Battery-powered nodes drain faster from the extra radio activity.

A healthy mesh is a large number of CLIENT nodes with very few, well-placed routers.

Use these roles instead

Your situation Correct role
Normal node, phone, handheld, home node CLIENT
Many nodes close together, high traffic area CLIENT_MUTE
Your own well-placed attic/roof node supporting your other nodes CLIENT_BASE
Filling a local dead spot without affecting the wider mesh ROUTER_LATE

ROUTER_LATE repeats packets only after all other nodes have had their turn. It is the polite way to add coverage for a small cluster of nodes.

Setting the role

App (Android / iOS): Settings → Device → Role

CLI:

meshtastic --set device.role CLIENT

To check what your node is currently set to:

meshtastic --info

If your node is currently set to ROUTER and does not meet the criteria above, please set it back to CLIENT. Thank you for keeping our mesh healthy!

Further reading