Recommended Node Settings: Stop Your Node From Being That Node
So you've got a node on the mesh. Nice. Now let's talk about how to keep it from being that node -- the one screaming into the void every thirty seconds and clogging up the airwaves for everyone else.
I pulled these recommendations together after staring at the NEPAMesh dashboard for longer than I'd like to admit. The short version: your node talks way more than you think it does, and most of what it's saying isn't your text messages.
Your Node Won't Shut Up (And That's Normal)
Text messages are tiny -- 30 to 50 bytes each, barely a blip. But here's the thing nobody tells you when you first flash your node: it's not just sending texts. It's also broadcasting its GPS position, device telemetry (battery voltage, uptime, all that), and a little "hey I exist" packet called NodeInfo. All of that adds up fast.
According to our dashboard, position and telemetry packets account for the vast majority of network traffic. Your actual text conversations? A rounding error. Out of nearly 20,000 packets processed in a recent 24-hour window, only 22 were text messages. The rest was your node telling everyone where it is and how it's feeling. Repeatedly.
Why Hops Matter More Than You Think
Every packet your node sends takes about 100 to 200 milliseconds of radio time. Doesn't sound like much until you realize that packet might get relayed through three, four, five other nodes to reach its destination. Each hop burns additional airtime. Now multiply that across 337 nodes all broadcasting position updates, telemetry, and NodeInfo packets, and you've got a recipe for congestion.
Keeping hops in the 3 to 5 range means your messages can still travel across the mesh without turning the whole network into a packet blender. More hops isn't better -- it's just louder.
The Settings That Actually Matter
Here's what we recommend for nodes on the NEPAMesh network. These aren't arbitrary -- they're based on what we've seen actually reduce congestion while keeping the mesh functional and the map populated. If you're running stock settings, you're probably fine for a first node, but tweaking these will make you a better mesh citizen.
LoRa Settings
| Setting | Value | Why |
|---|---|---|
| Ignore MQTT | True | Keeps MQTT traffic from saturating your node. Only disable this if you're running a private broker and know what you're doing. |
| OK to MQTT | True | This is how you show up on map.nepamesh.com. Turn it off if you want to be invisible, but then what's the point? |
| Number of Hops | 5 | Don't go higher than 6 unless you enjoy watching the mesh struggle. |
Channel Settings
| Setting | Value | Why |
|---|---|---|
| Uplink enabled | Off | Leave it off unless you have a specific reason to enable it. |
| Downlink enabled | Off | Same deal. Off by default. |
| Position enabled | On | This lets you show up on the map. The whole point of being on the mesh. |
| Precise location | Off | Adds about 1.8 miles of fuzz to your reported position. Your neighbors don't need your exact address. |
Device Settings
Node Info broadcast interval: 4 hours (14400 seconds). Your node doesn't need to introduce itself every few minutes like it's at a networking event. Once every four hours is plenty. The mesh will remember you.
Position Settings
| Setting | Value | Notes |
|---|---|---|
| Broadcast Interval | 4 hours (14400) | Handheld nodes can get away with 1 hour if you're actually moving around. Fixed nodes have no excuse to broadcast more often. |
| Smart position | Off | Disable for fixed nodes. If your node isn't going anywhere, it doesn't need to tell everyone it hasn't moved. |
| GPS Polling Interval | 30 min (1800) | Only relevant if you have a GPS module. Otherwise, ignore this entirely. |
| Position flags | Disable unused | If you have GPS, turn off the flags you don't need. Fixed nodes should disable most of them. |
Telemetry Settings
If you have the Telemetry Module enabled, set all three update intervals -- Device metrics, Environment metrics, and Power metrics -- to 2 hours (7200 seconds).
Quick note on Power metrics: those are for external I2C power monitors, not your onboard battery data. If you don't have one of those plugged in, the data is meaningless anyway. Your battery percentage already comes through Device metrics.
Neighbor Info
Leave it off. It generates extra packets and the mesh doesn't need it to function. If you're actively debugging mesh topology, sure, flip it on temporarily. Otherwise, it's just noise. The irony of the mesh working better when you keep the Neighbor Info module off is not lost on me.
TL;DR
Broadcast less often. Keep hops reasonable. Show up on the map but don't share your exact location. Turn off stuff you're not using. The mesh works best when everyone's a good neighbor -- which, as mentioned, means keeping the Neighbor Info module off.
These settings aren't gospel. If you have a specific use case that needs different config, go for it. But if you're running a standard node and want to be a good citizen of the NEPAMesh network, this is the playbook.
Questions? Hop into the NEPAMesh Discord. We'll sort you out.
Useful Links
- NEPAMesh Map: map.nepamesh.com
- NEPAMesh Discord: (link at the top of the page)
- Meshtastic Settings Docs: meshtastic.org/docs/configuration
- Getting Started Guide: nepamesh.com
Meshtastic is a registered trademark of Meshtastic LLC. Meshtastic software components are released under various licenses, see GitHub for details. No warranty is provided - use at your own risk. The Meshtastic logo trademark is the trademark of Meshtastic LLC. This post is not endorsed by or affiliated with Meshtastic LLC.
