In a Meshtastic network, managing airtime is critical. Because LoRa bandwidth is limited, configuring how often a node broadcasts its metadata—such as position, telemetry, and node information—determines the balance between network visibility and congestion. I’ll try to outlines the technical configuration for two distinct roles: a Fixed Node and a Mobile Node. Both configurations imply that nodes are configured as “client”.
Fixed Node Configuration
A fixed node typically acts as a relay within the mesh. Since its physical location does not change, the broadcast intervals are generally higher than ones used for mobile nodes. Generally fixed nodes are plugged so power consumption isn’t a big deal. These are
| Parameter | Interval (Seconds) | …or in hours |
|---|---|---|
| Node Info Broadcast Interval | 10,800 | 3.0 Hours |
| Position | 43,200 | 12.0 Hours |
| Telemetry | 3,600 | 1.0 Hour |
| Env. Telemetry | 1,800 | 0.5 Hours |
| Neighbor Info | 3,600 | 1.0 Hour |
The Position interval is set to 12 hours. This is an efficient use of resources because a stationary node’s coordinates are static; frequent updates would provide no new data to the mesh. Neighbor Info is enabled at 1 hour to help map the mesh topology and identify which nodes are within direct RF range.
Mobile Node Configuration
Mobile nodes require higher update frequencies to remain relevant on the map. However, to prevent “spamming” the network, specific logic like Smart Position is employed.
| Parameter | Interval (Seconds) | Interval (Hours) |
|---|---|---|
| Node Info Broadcast Interval | 3,600 | 1.0 Hour |
| Position | 3,600 | 1.0 Hour |
| Telemetry | 3,600 | 1.0 Hour |
| Env. Telemetry | 1,800 | 0.5 Hours |
| Neighbor Info | Disabled | N/A |
Smart Position: Unlike the fixed node, this client uses “Smart Position” logic. Instead of a purely timer-based broadcast, the node calculates its rate of movement. If the node is stationary, it remains quiet; if it moves significantly, it triggers a broadcast regardless of the 3600s timer. Neighbor Info (Disabled): Disabling neighbor info on mobile nodes is a common optimization. As the node moves, its neighbor list changes constantly. Transmitting this fluctuating list adds overhead without providing a stable map of the network architecture.
Key Comparisons and Impact
The discrepancy between the two configurations highlights a “Role-Based” approach to mesh networking:
- Airtime Conservation: The fixed node uses significantly less airtime ($1/12th$ the position updates of the mobile node), acting as a “quiet” backbone.
- Environment Monitoring: Both nodes maintain a high frequency for Environment Telemetry (1800s). This suggests that sensor data (like temperature or humidity) is prioritized over identity data in this specific deployment.
- Mesh Hygiene: By disabling Neighbor Info on the mobile node, the network avoids “churn”—the rapid updating of routing tables that occurs when a moving node constantly reports new peers.
Note on Power: Mobile nodes often rely on battery power. While the intervals above are optimized for data, users should monitor the battery impact of the 30-minute Environment Telemetry interval if using high-draw sensors.