Meshtastic EU868 Region and Duty-Cycle Basics

[Pavel]

Short answer: Set the Meshtastic region to EU_868 only when operating under the applicable European 863–870 MHz rules, and keep firmware defaults that enforce permitted channels, power and airtime. Duty cycle limits channel occupancy over time; they are not only a maximum transmit-power rule.

Before you start​

• Set the correct regional radio profile before testing; frequency plan, permitted power and duty-cycle constraints depend on location.
• Use the same modem preset, channel settings and channel key on nodes that are expected to communicate.

Step-by-step method​

1. Step 1: Confirm the legal region of operation and set every node to the same correct regional profile. Do not use US_915 or another plan because it appears less busy.
2. Step 2: Choose one shared modem preset and channel configuration. Slower long-range presets consume more airtime per message and reduce practical network capacity.
3. Step 3: Limit automatic telemetry, position updates and repeated messages. Estimate total airtime across forwarded mesh traffic, not only messages typed on one node.
4. Step 4: Review device logs for duty-cycle or channel-utilization warnings and test delivery under the expected network load.

Concrete example​

A node sending frequent GPS and sensor updates can consume far more airtime than occasional text messages, especially on a slow modem preset. Increasing interval from one minute to fifteen minutes can materially reduce channel use.

How to judge the result​

A compliant setup uses the correct region, keeps airtime within enforced limits and delivers messages without persistent duty-cycle blocking under normal traffic.

What to record​

• Record RSSI, SNR, hop count, delivery success and antenna height for a fixed route instead of quoting one maximum-distance message.
• Line of sight, Fresnel clearance and antenna placement usually improve range more effectively than additional transmit power.
• For solar nodes, calculate daily energy use and worst-month solar input, then include battery reserve for poor weather.

Common mistakes​

• Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
• Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
• Changing to another region profile to bypass restrictions can use unauthorized frequencies or power and can interfere with other services.

Final check​

Power-cycle both nodes and repeat the same bidirectional route test. Save region, preset, antenna, RSSI, SNR and delivery rate while keeping channel keys and precise locations private.