New: the AI firewall watches every module and explains each incident in plain words. See how it works

LoRaWAN limits

Every LoRaWAN limit and default in one place – gateways, devices, keys, profile settings, pairing, downlinks, frames and codecs.

This page collects the limits and defaults of Hermetry’s LoRaWAN network server. The pages linked in each section explain them.

Gateways and devices

ItemLimit
Device limitGateways and end devices count toward your plan’s device limit like any device. A licensed router serving as a gateway counts once, as itself.
Gateways per organisationNo separate limit beyond the device limit
Gateway EUI16 hexadecimal digits; not all zeros or all F; unique on the whole platform
DevEUI16 hexadecimal digits; not all zeros or all F; unique on the whole platform
JoinEUI16 hexadecimal digits (all zeros allowed)
AppKey, NwkSKey, AppSKey32 hexadecimal digits each
DevAddr (ABP)8 hexadecimal digits, inside the network’s NetID prefix, unique among your live devices
Name of a gateway or device1–128 characters
Gateway locationLatitude −90 to 90, longitude −180 to 180, altitude −1,000 to 100,000 m
LoRaWAN versions1.0.2, 1.0.3, 1.0.4
ClassesA, C
RegionEU868 only

See Add a gateway, Add an OTAA device, Add an ABP device.

Profile settings

SettingDefaultRange
RX1 delay5 s1–15 s
RX1 data-rate offset00–5
RX2869.525 MHz, DR0DR0–DR7
ADROn
ADR data-rate range (UI)DR0–DR5DR0–DR5
Installation margin (ADR)10 dB0–30 dB
De-duplication window200 ms50–1,000 ms
Device status request interval24 h0 (never) – 720 h
Confirmed downlink sends30–10
Class C reachable after the last uplink900 s60–86,400 s
Class C acknowledgement wait60 s5–3,600 s
Aggregated duty-cycle request0 (none)0–15

See LoRaWAN device profiles.

Joins and frames

ItemLimit
Join acceptSent 5 s (RX1) or 6 s (RX2) after the join request
DevNonce memory (1.0.2, 1.0.3)The last 256 values per device
Frame counter stepAt most 16,384 forward; a repeat only as the retransmission of the last confirmed uplink
Device message per uplinkOne, however many gateways heard it
Decoded keys per message64, nested at most 4 levels
raw payloadUp to 4,096 bytes (as hex)
Frames logThe last day, at most 1,000 frames per organisation; the drawer shows 200

Pairing mode

ItemLimit
Window length1–120 minutes (the UI offers 5, 15, 30, 60, 120)
Devices listed per window200, newest first
RequirementA shared AppKey on the profile

See Pairing mode.

ItemLimit
Methodlora.downlink
fPort1–223
dataHex or base64, at most 1,024 characters
Max payload, DR0–DR251 bytes
Max payload, DR3115 bytes
Max payload, DR4–DR7222 bytes
Class C downlinksAt the RX2 data rate (DR0 by default: 51 bytes)
Application downlinks per Class A uplink1
Duty-cycle planning90 % of each sub-band’s hourly budget per gateway
Command limitsThe general command limits apply: 10 per device per minute, 600 per organisation per minute by default

See Sending downlinks and Regions and frequency plans.

Gateways at run time

ItemValue
Health recordOne per gateway per minute
Connection re-checkEvery open gateway connection is re-checked every 60 s
Malformed messages3 within 60 s close the connection
Gateway mapUp to 1,000 gateways, refreshed every 15 s

Codecs

ItemLimit
Library106 codecs
Your codec idt. + 2–62 lower-case letters, digits or dashes
Your codec size40,960 bytes
Test vectors per codecAt least 1, at most 200
Models, FPorts per codec64 each
Maker codes (OUI) per codec32
Nesting depth32 levels
Test bench frameFPort 1–255, at most 255 bytes
API rate, no credential60 a minute per address (bundle: 6 an hour)
API rate, users and API keys240 a minute (bundle: 30 an hour)
API rate, licensed routers120 a minute per certificate

See Write your own codec and Codecs API.