ADR (Adaptive Data Rate) is a LoRaWAN mechanism in which the Network Server analyses the link quality reported by the gateways (RSSI and SNR) and instructs each end device to switch to a lower spreading factor (faster, less battery-hungry, for example SF7 instead of SF12) whenever the signal margin allows it.
True
End devices typically start at a high spreading factor for safety on first uplink. The Network Server then averages the link margin over the last 20 frames or so, and if the margin is comfortable it sends a LinkADRReq MAC command telling the device to step down in SF, increase its data rate and possibly reduce its TX power. If conditions later deteriorate, the device autonomously climbs back to a higher SF after a configurable number of missed acknowledgements (the ADR back-off). The mechanism saves battery, reduces duty-cycle consumption and is central to LoRaWAN scalability.
Enable ADR only on stationary devices — for moving assets (asset trackers, vehicles) ADR oscillates and wastes energy, so the LoRa Alliance explicitly recommends disabling the ADR bit on mobile end devices.
LoRaWAN bank in preparation
The full LoRaWAN bank isn't available yet. Drop your email to get notified at launch and grab an early-bird discount.
Join the waitlist →See the 9 other LoRaWAN practice questions
Related questions
- An important distinction must be made: "LoRa" is the physical-layer radio modulation (CSS, Chirp Spread Spectrum, proprietary to Semtech), whereas "LoRaWAN" is the MAC-layer protocol and network architecture (an open standard from the LoRa Alliance) built on top of LoRa.1. Architecture · LoRa vs LoRaWAN
- LoRaWAN uses a "star-of-stars" topology: each end device transmits unidirectionally toward ALL in-range gateways, the gateways forward the packet to the Network Server, which deduplicates the copies; there is no mesh between end devices.1. Architecture · Star-of-Stars-Topologie
- As of 2026, the main public LoRaWAN operators in France are: Orange Live Objects (near-nationwide coverage), Bouygues Objenious (in sunset), Helium Network (community-driven) and Loriot (Swiss-based commercial Network Server vendor, not a public carrier). In addition, many deployments are run on private networks (dedicated infrastructure).6. Network providers · Öffentliche Betreiber
- For critical IoT deployments (smart city, industrial sites, fleet asset tracking), private LoRaWAN networks are often preferred over public operators: full infrastructure control, contractual SLA, stronger security and no commercial dependency on a third-party operator.6. Network providers · Öffentlich vs. Privat
- Typical LoRaWAN smart-city use cases include: smart water meters, parking-bay occupancy sensors, fill-level sensors for waste bins, public-lighting telemonitoring, air-quality stations, EV charger monitoring (status and energy readings — not the OCPP charge-control protocol) and flood alerts — a typical LoRaWAN sensor costs between EUR 30 and EUR 150.7. Use cases · Smart City