Recommended Configuration Settings
In order to maintain a healthy mesh network, we recommend the following configuration settings for your Meshtastic devices.
These settings are intended to facilitate a stable and reliable mesh network. They are based on the collective experience of the Mountain Mesh community and are subject to change as the mesh grows and evolves.
Radio configuration
Option | Recommended Config | Notes |
---|---|---|
Role | CLIENT or CLIENT_MUTE |
See Meshtastic Deployment Scenarios |
NodeInfo broadcast interval | 10800 (3 hours) |
Option | Recommended Config | Notes |
---|---|---|
Smart position enabled | True |
|
Position broadcast interval | 3600 (1 hour) |
|
GPS update interval | 1800 (30 minutes) |
|
Position flags | Disable unused flags | Fixed nodes should disable almost all of these. |
Option | Recommended Config | Notes |
---|---|---|
Hop limit | 5 |
Please do not set this higher than 6 . The mesh thanks you. |
Ignore MQTT | True |
This is enabled on most ROUTER nodes in our mesh. |
OK to MQTT | True |
Added in 2.5.0 . Enable to show up on online tools like info.MtnMe.sh. |
Module configuration
Option | Recommended Config | Notes |
---|---|---|
Device metrics update interval | 3600 (1 hour) |
Change to 1800 when testing new nodes. |
Environment metrics update interval | 3600 (1 hour) |
|
Power metrics module enabled | False |
This is for I²C power monitors, not onboard battery stats. |
Consider disabling the Environment metrics
/ Air Quality metrics
modules if you are not using the data.
Option | Recommended Config | Notes |
---|---|---|
Neighbor Info enabled | True |
Only enable this on "infrastructure" nodes. |
Update interval | 21600 (6 hours) |
This is a large packet! Do not set this lower than 6 hours. |
Neighbor Info is a large packet and should only be enabled on "infrastructure" nodes (Routers / Home base-stations). This is a great way to see who is around you on our mapping tools, but it is not recommended for mobile nodes or secondary indoor nodes.
Setting the interval too low will cause congestion on the mesh, leading to packet loss and dropped messages.