Use this matrix to choose the right Meshtastic role for each node in a real-world mesh. The goal is to maximize coverage and reliability while minimizing airtime, collisions, and maintenance.
Definitions in Practical Terms
- Router node: Participates more fully in mesh behavior, typically handling routing/relaying plus periodic housekeeping traffic (depending on your config and firmware behavior). Best when you want a stable, “always-on” backbone with good network awareness.
- Repeater node: A more minimalist relay profile intended to extend range with less node “chatter.” Best when you need a quiet, coverage-extending relay at a high site or you are airtime-constrained.
(Exact behavior varies by firmware version and configuration; treat the guidance below as operationally-oriented rather than strictly implementation-specific.)
Quick Decision Matrix
Choose Repeater when…
| Condition | Why |
|---|---|
| You’re installing on a high, line-of-sight site (tower/roof/hill) | High sites can “hear” a lot; repeater mode reduces extra management traffic and lowers airtime load. |
| The local mesh is dense (many nodes within earshot) | Minimizes collisions and redundant transmissions. |
| Power is tight (small solar/battery) | Lower overhead tends to mean better endurance. |
| You need a simple range extender and do not need rich telemetry | Repeater nodes can be “set and forget.” |
| Your primary constraint is RF airtime | Repeater prioritizes being quiet while still relaying. |
Choose Router when…
| Condition | Why |
|---|---|
| You want a backbone anchor in a sparse mesh | Router nodes help stabilize and improve route availability when there are fewer nodes. |
| You need better network robustness around an area (e.g., neighborhood hub) | More participation in routing behavior can improve delivery success. |
| You want to support telemetry / sensors (weather, gateway health, etc.) | Router role is typically used for “infrastructure” nodes with more features enabled. |
| Power is stable (mains/DC-fed or ample solar) | Router role is more comfortable with constant duty operation. |
| You expect changing topology (mobile operators moving through) | Routers tend to handle dynamic routing needs better. |
Scoring Worksheet (Most Useful for Planning)
Score each statement 0–2 (0 = no, 1 = somewhat, 2 = yes). Add totals.
Repeater Score
- Site is elevated and can hear many nodes: __/2
- Mesh is dense (10+ nodes in range): __/2
- Airtime is already busy (collisions/latency observed): __/2
- Power budget is limited (small solar, winter risk): __/2
- You want minimal telemetry / “quiet infra”: __/2
Repeater total: __/10
Router Score
- Mesh is sparse (few nodes in range): __/2
- You need high reliability for neighborhood coverage: __/2
- You plan to run sensors/health telemetry: __/2
- Power is stable and maintenance is easy: __/2
- Topology changes often (mobile users, events): __/2
Router total: __/10
Decision rule:
- If Repeater total exceeds Router by 2+, choose Repeater.
- If Router total exceeds Repeater by 2+, choose Router.
- If within 0–1, default to Repeater for high sites/dense meshes, otherwise Router.
Deployment Patterns That Work
Pattern A — “High Quiet Spine”
- Rooftop/hilltop nodes: Repeater
- Neighborhood anchors: Router
Why: High sites extend reach without flooding the channel; routers improve local delivery.
Pattern B — “Sparse Rural Coverage”
- Most fixed infrastructure nodes: Router
- One very high relay: Repeater (only if it hears a lot of nodes)
Why: Sparse networks benefit from routers; one quiet high relay can bridge valleys.
Pattern C — “Event / EMCOMM”
- Command post node: Router (telemetry + stability)
- Field relays: Repeater (quiet, range)
- Mobile teams: Client
Why: Keeps the channel usable while still extending coverage.
Operational “Tell-Tales” (When to Switch Roles)
Switch from Router → Repeater if you observe:
- Noticeable increases in collisions/latency after adding an elevated node
- Many nodes can already communicate without it
- Power draw is stressing solar/battery margins
Switch from Repeater → Router if you observe:
- Messages frequently fail unless a specific node is online
- Sparse topology; you need better delivery success
- You’re trying to support additional services (telemetry, mapping, health reporting)
Ham-Oriented Best Practices (Independent of Role)
- Height and feedline matter more than role. At ~900 MHz, coax loss is real; keep runs short and use low-loss cable.
- Prefer one good high site to many mediocre ones.
- Keep infrastructure nodes conservative: modest TX power, longer telemetry intervals, disciplined channel plan.
- Clearly label nodes as ISM/Meshtastic and keep them operationally separate from Part 97 traffic.