LoRaWAN uses different frequencies in different parts of the world. Hermetry’s network server runs the EU868 region (Europe, 863–870 MHz). This is the only region switched on. Region data for other bands exists in the network server, but those regions are not switched on and cannot be chosen for gateways, profiles or devices. Use devices and gateways built for EU868.
Channels
| Channels | Frequencies | Data rates | How the device learns them |
|---|---|---|---|
| 3 default channels | 868.1, 868.3, 868.5 MHz | DR0–DR5 | Built into every EU868 device |
| 5 extra channels | 867.1, 867.3, 867.5, 867.7, 867.9 MHz | DR0–DR5 | Sent in the join accept (OTAA devices) |
| RX2 downlink channel | 869.525 MHz | DR0 | Region default |
Join requests use the three default channels. An ABP device starts with the three default channels only.
The network server also sends the gateway its radio configuration when it connects: the eight multi-data-rate channels above, plus one 250 kHz LoRa channel at 868.3 MHz (SF7) and one FSK channel at 868.8 MHz (50 kbit/s). You do not set channels on a Basics Station gateway yourself.
Data rates
| DR | Modulation | Spreading factor | Bandwidth | Max application payload |
|---|---|---|---|---|
| DR0 | LoRa | SF12 | 125 kHz | 51 bytes |
| DR1 | LoRa | SF11 | 125 kHz | 51 bytes |
| DR2 | LoRa | SF10 | 125 kHz | 51 bytes |
| DR3 | LoRa | SF9 | 125 kHz | 115 bytes |
| DR4 | LoRa | SF8 | 125 kHz | 222 bytes |
| DR5 | LoRa | SF7 | 125 kHz | 222 bytes |
| DR6 | LoRa | SF7 | 250 kHz | 222 bytes |
| DR7 | FSK | — | 50 kbit/s | 222 bytes |
The maximum application payload is the space left for your data when no MAC commands ride along. Lower data rates reach further but take longer on air and carry less. Uplink channels use DR0–DR5; ADR moves devices within the range set on the profile (DR0–DR5).
Receive windows
| Window | Default on Hermetry |
|---|---|
| RX1 delay | 5 seconds (profile setting, 1–15 s) |
| RX1 data-rate offset | 0 |
| RX2 | 869.525 MHz, DR0 |
| Join accept | 5 s after the join request (RX1), or 6 s (RX2) |
Duty cycle
European rules limit how much of each hour a transmitter may be on air in each sub-band. Gateways must respect this for downlinks too. Hermetry keeps a ledger of each gateway’s downlink airtime per sub-band over the last hour and plans downlinks within 90 % of the allowed budget, leaving a margin. The gateway enforces the law itself as well.
| Sub-band | Frequencies | Duty cycle | Max EIRP |
|---|---|---|---|
| K | 863.0–865.0 MHz | 0.1 % | 16 dBm |
| L | 865.0–868.0 MHz | 1 % | 16 dBm |
| M | 868.0–868.6 MHz | 1 % | 16 dBm |
| N | 868.7–869.2 MHz | 0.1 % | 16 dBm |
| P | 869.4–869.65 MHz | 10 % | 27 dBm |
| Q | 869.7–870.0 MHz | 1 % | 16 dBm |
RX1 answers go out on the uplink’s channel (sub-bands L and M, 1 %). RX2 and Class C downlinks go out on 869.525 MHz (sub-band P, 10 %). When RX1 has no budget left on a gateway, the same gateway may still answer in RX2.
1 % of an hour is 36 seconds of airtime. At DR0 even a short downlink takes about a second on air, so a gateway can send only a few dozen RX1 downlinks per hour per sub-band at the slowest data rates.
The gateway’s health telemetry shows its use per sub-band as lora.gw.dc_used_pct.<band>, and the default alarm warns above 80 %. See Gateway status, health and the map.
What uses duty cycle
- Acknowledgements of confirmed uplinks. Prefer unconfirmed uplinks on sensors.
- MAC commands, such as ADR changes.
- Join accepts.
- Your application downlinks.
Many devices sending confirmed uplinks through one gateway can use up its budget; downlinks then wait or go through another gateway.
Other regions
Other regions are not available. A request that names another region is refused (This region is not supported yet.), and the region field on forms is locked to EU868.