MeshCore performance tuning for the Netherlands
Optimize reliability, airtime usage, and battery life without breaking compatibility with the Dutch MeshCore network
Why performance tuning works differently in the Netherlands
On the Dutch MeshCore network, performance tuning starts with one important rule: stay compatible with the network preset that everyone else uses. If you change core radio parameters like spreading factor, bandwidth, or coding rate on your own, you may simply stop hearing the rest of the network.
The official MeshCore documentation says you should use the preset for your region, and notes that many regions have moved to the "narrow" style using BW62.5 with lower SF values such as SF7, SF8, or SF9. It also describes CR5 as the default for good stable links. For LocalMesh in the Netherlands, that means choosing the preset Netherlands in the app, with the Dutch network profile behind it of SF7, BW62.5, CR5.
So this page is not about inventing your own RF profile. It is about tuning the things around that shared profile: transmit power, adverts, congestion, battery use, and repeater behaviour.
Performance dimensions
Range
How far can messages reach between nodes
Speed
How fast are messages sent and received
Battery life
How long can node run on battery
Reliability
Percentage of messages that arrive without errors
Throughput
How much data can the network handle
Scalability
How many nodes can communicate simultaneously
Performance optimization tips
1. Do not change spreading factor on your own
For LocalMesh in the Netherlands, the working network profile is built around <strong>SF7</strong>. If you switch your node to SF8, SF10, or SF12 while the rest of the network stays on SF7, you are no longer tuning performance - you are moving off the shared radio profile.
Impact: Changing SF by yourself can make your node effectively disappear from the Dutch network. If the community ever changes preset, it should happen as a coordinated network-wide move, not as a per-node experiment.
2. Improve antenna height and placement first
If you want better range or a more stable link, first look at where your node is placed. A higher antenna or a cleaner position often makes more real-world difference than touching RF parameters. If you are very close to a 4G or 5G cell site and still see strange reception problems, a suitable cavity filter can sometimes help suppress strong unwanted signals outside the 868 MHz band. Only after that should you cautiously look at transmit power.
Impact: Better height, fewer obstacles, and smarter placement can improve reception and range without breaking compatibility with the rest of the Dutch network. And in harsh RF environments, such as near a cell tower, a cavity filter can sometimes help against front-end overload or desensitization. In practice that is usually more effective than changing SF, BW, or CR on your own.
3. Do not change bandwidth casually
The Dutch MeshCore network expects the narrow preset profile. In practice that means <strong>BW62.5</strong>. If you switch to a different bandwidth on your own, you will no longer be aligned with the network you are trying to join.
Impact: Bandwidth changes are not an isolated speed tweak. On a shared mesh they are a compatibility change. Leave BW alone unless the Dutch community changes the preset together.
4. Keep coding rate on the shared profile
The official MeshCore FAQ describes <strong>CR5</strong> as the default for good stable links. For LocalMesh in the Netherlands, that is the value you should stay on if you want to remain compatible with the rest of the network.
Impact: Just like SF and bandwidth, changing CR on a single node is not a smart way to "improve" things on a shared network. Keep CR5 unless the broader network changes together.
5. Tune intervals before touching RF settings
If you want better battery life or less congestion, first look at adverts, telemetry, and other periodic traffic. Those settings often give you real gains without moving away from the shared Dutch RF profile.
Impact: For most users this is a far better tuning lever than trying random SF or CR changes. Less unnecessary traffic usually helps the whole network.
6. Avoid channel congestion
Monitor airtime and avoid needless chatter. If the channel is busy, reduce non-essential traffic first instead of inventing your own radio profile.
Impact: The cleanest fix for congestion is usually fewer unnecessary broadcasts, better repeater placement, and sensible intervals - not breaking compatibility with the network preset.
Configuration examples
Recommended starting points for the Dutch MeshCore network
Default Netherlands / LocalMesh profile
Use this if you simply want to be compatible with the Dutch network:
spreading_factor: SF7
bandwidth: 62.5 kHz
coding_rate: CR5
goal: stay compatible with the Dutch MeshCore network
Battery-friendly client config
Keep the Dutch RF profile unchanged and only tune the safer variables:
spreading_factor: SF7
bandwidth: 62.5 kHz
coding_rate: CR5
tx_power: conservative value for your hardware
telemetry / adverts: slower intervals to save battery
Repeater config for the Netherlands
Again: keep the RF profile shared, tune repeater behaviour around it:
spreading_factor: SF7
bandwidth: 62.5 kHz
coding_rate: CR5
tx_power: appropriate for repeater hardware and local rules
flood / advert settings: tuned for network hygiene, not for custom RF compatibility
Best practices for optimization
-
✓
Start from the network preset: For LocalMesh in the Netherlands, that means the preset Netherlands with SF7, BW62.5 and CR5.
-
✓
Do not tune yourself off the network: If you change SF/BW/CR alone, you may no longer hear the rest of the mesh.
-
✓
Test in real conditions: Lab performance ≠ field performance with obstacles and interference
-
✓
Monitor after changes: Check if your optimization actually improves what you wanted
-
✓
Document your settings: Keep track of which config you use and why
-
✓
Tune the safe variables first: Height, antenna placement, power, intervals, congestion control, and where needed filtering usually matter more than inventing your own RF profile.
Frequently asked questions
What is more important: range or speed?
On the Dutch MeshCore network, compatibility comes first. If everyone else is on the shared network preset, changing your own SF to chase more range is usually the wrong move. Start by staying on the Dutch profile, then improve antenna height, placement, power, and congestion behaviour.
How do I measure if my optimization works?
Track these metrics: SNR (higher is better), packet loss % (lower is better), air utilization (under 10%), battery life (measure actual runtime), message latency (time from send to receive). Also look at the RF environment: if you are close to a 4G or 5G cell site, strong out-of-band signals can hurt reception. In that case, a suitable cavity filter may be more useful than changing SF or CR.
Can I use different configs on different nodes?
Some settings can differ per node, such as transmit power or how often a device sends non-essential traffic. But if you want to communicate with the LocalMesh network, your core RF profile must stay compatible. In practice that means staying on the Dutch preset rather than changing SF/BW/CR on your own.
What are the limits of LoRa physics?
Absolute max range is ~50km line-of-sight at sea level. In practice: ~10km open field, ~1-3km urban. Max data rate is ~5.5 kbps at SF7/250kHz. You can't bypass these limits - LoRa is designed for long range low bandwidth.
How do I optimize for maximum battery life?
Keep the Dutch network RF profile unchanged, then reduce power where appropriate, slow down non-essential broadcasts, disable Bluetooth when not needed, and use sleep modes sensibly. Battery tuning should happen around the shared network preset, not by moving to your own private SF/BW/CR combination.
Optimize your MeshCore network
For LocalMesh in the Netherlands, good performance tuning means staying compatible with the shared network profile and improving the variables around it.
Start with the Dutch preset, then look first at antenna height, placement, power, intervals, and congestion based on real results.