6.4 KiB
title, nav_order, last_updated, description, aliases
| title | nav_order | last_updated | description | aliases | |||
|---|---|---|---|---|---|---|---|
| Nodes | 4 | 2026-05-13 | Browse, filter, and sort mesh nodes — view details, signal quality, roles, and quick actions. |
|
Nodes
The Nodes screen displays all devices visible on your mesh network.
Node List
The node list shows every node your radio has heard, including:
- Node name — user-configured long name
- Short name — 4-character identifier
- Signal quality — last heard signal strength
- Last heard — time since last communication
- Distance — estimated distance (if positions are shared)
- Battery — remote node battery level (if telemetry is enabled)
Node Status Indicators
| Badge | Meaning |
|---|---|
| 🟢 Online | Node heard within the last 15 minutes |
| 🟡 Away | Node heard within the last 2 hours |
| 🔴 Offline | Node not heard for over 2 hours |
| ⭐ Favorite | Node marked as favorite by the user |
Node Roles
Nodes can be configured with different roles that affect their mesh behavior:
| Role | Description |
|---|---|
| Client | Standard end-user device |
| Client Mute | Receives but doesn't retransmit |
| Client Hidden | Like Client Mute, plus hides from node list |
| Router | Prioritizes message forwarding; stays awake to relay |
| Router Client | Routes and operates as a client |
| Repeater | Retransmits only; no user interface |
| Tracker | Optimized for position reporting at regular intervals |
| Sensor | Optimized for telemetry reporting |
| TAK | Interoperates with TAK systems (sends/receives CoT) |
| TAK Tracker | TAK position reporting only |
| Lost & Found | Continuous position beacon for recovery |
Choosing a Role
Most users should keep the default Client role. Consider a different role when:
- Router — You have a node in a fixed, elevated location with reliable power (rooftop, hilltop). Routers stay awake continuously to relay messages for others and are essential for extending mesh coverage. Don't use Router on battery-powered handheld devices.
- Router Client — Like Router, but the device is also used as a personal client. Good for a home base station that you also send messages from.
- Client Mute — You want to receive mesh traffic but not contribute to relaying. Useful for monitoring-only devices or to reduce congestion in dense areas.
- Repeater — A dedicated relay node with no screen or user interaction. Optimized purely for forwarding; lowest power consumption of the relay roles.
- Tracker — An unattended device whose sole purpose is broadcasting its GPS position (e.g., a vehicle, pet, or asset). Sleeps between broadcasts to conserve battery.
- Sensor — An unattended device reporting environmental telemetry (temperature, humidity, air quality). Similar power profile to Tracker.
- TAK / TAK Tracker — Only needed if interoperating with ATAK/WinTAK systems. See TAK Integration for details.
💡 Tip: The mesh works best when most nodes are Client or Router. Too many Mute nodes reduces mesh resilience; too many Routers in a dense area can cause congestion. A good rule of thumb: one Router per 5–10 Clients in your area.
Encryption Indicators
Nodes display encryption status icons next to their name:
| Icon | Meaning |
|---|---|
| 🔒 Locked | Communication uses PKI (public key infrastructure) — end-to-end encrypted with verified identity |
| 🔓 Unlocked | Communication uses shared channel PSK — encrypted but identity not individually verified |
| ⚠️ Mismatch | Public key mismatch — the node's key has changed since last seen (investigate before trusting) |
💡 Tip: PKI encryption (firmware 2.5+) provides stronger security than channel PSK because each node has a unique key pair. If you see a key mismatch warning, the node may have been reset or compromised.
Quick Actions
From the node list, you can:
- Tap a node to view its detail page
- Long-press for quick actions:
- Send a direct message
- View on map
- Request position
- Mark as favorite
- Traceroute
Filtering & Sorting
Text Search
Type in the search field to filter nodes by name or short name. The filter updates in real time as you type.
Filter Toggles
| Filter | Description |
|---|---|
| Only online | Show only nodes heard within the last 15 minutes |
| Only direct | Show only nodes with direct (non-relayed) connections |
| Include unknown | Show nodes that haven't sent user info yet |
| Exclude infrastructure | Hide infrastructure-role nodes (Router, Repeater, Router Client) |
| Exclude MQTT | Hide nodes heard only via MQTT internet bridge |
| Show ignored | Show nodes you've previously dismissed or muted |
Sort Options
| Sort | Description |
|---|---|
| Last heard (default) | Most recently heard nodes first |
| Alphabetical | Sorted by node long name |
| Distance | Nearest nodes first (requires position sharing) |
| Hops away | Fewest relay hops first |
| Channel | Grouped by channel index |
| Via MQTT | Grouped by MQTT vs. radio-heard |
| Favorites | Favorited nodes first |
Node Detail
Tapping a node opens the detail view with comprehensive information. See Node Metrics for full details on metrics and telemetry.
The detail screen includes device info, position, and action buttons:
Inline status indicators show key metrics at a glance:
| Indicator | Screenshot |
|---|---|
| Signal quality |  |
| Battery level |  |
| Hop count |  |
| Last heard |  |
| Distance |  |
Related Topics
- Node Metrics — detailed telemetry dashboards for each node
- Messages & Channels — send a direct message to a node
- Map & Waypoints — view node positions geographically
- Discovery — traceroute and neighbor info for topology exploration
- Signal Meter — understand what the signal bars mean