An OTAA LoRaWAN end device is identified by: a DevEUI (a 64-bit device-unique identifier, similar in spirit to a MAC address), an AppEUI/JoinEUI (a 64-bit application owner identifier) and an AppKey (a 128-bit pre-shared secret used for the OTAA Join procedure).
True
The DevEUI is 8 bytes long and is unique per device — it is either IEEE-assigned (a real EUI-64 from a registered OUI) or vendor-assigned. The JoinEUI (called AppEUI in LoRaWAN 1.0) is also 8 bytes and identifies the application or its owner so that the Join Server knows where to route the Join Request. The AppKey is a 16-byte secret shared between the device and the Join Server, used to authenticate the Join procedure. During the Join, the device and the Network Server derive the session keys (NwkSKey and AppSKey in 1.0, four keys in 1.1) and the Network Server assigns a DevAddr dynamically.
Never reuse the same DevEUI across two devices, even in lab environments — duplicate DevEUIs cause silent Join Accept collisions that are notoriously hard to debug from the device side.
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