On-boarding and Deploying Your First Devices on the Helium Network - Part 1
LoRaWAN Sensor and Device Unique IDs and Security Credentials
Helium Network LoRaWAN Device Purchasing Checklist:
- Device is LoRaWAN version 1.0.x compatible*
- Device operates in LoRaWAN Class A mode**
- Device supports the Helium channel plan for its region of deployment (US915, EU868, other)
- The device’s EUIs and AppKey are available via printed labels, CSV files, APIs, or manufacturer-provided utilities
*note = Currently deployed LoRaWAN networks, including Helium, support LoRaWAN version V1.0.x. The LoRa Alliance has defined a v1.1.x roadmap specification. Sensors and devices supporting the 1.1.x release will maintain backward compatibility with 1.0.x networks. However 1.1.x devices support two security keys, the AppKey and NwkKey. A 1.1.x end-device will use its NwkKey (in lieu of its AppKey) to Join a 1.0.x LoRaWAN network. Please refer to section 6.1.1.3 Device root keys (AppKey & NwkKey) of the LoRaWAN 1.1 Specification for full details.
**note = Many other LoRaWAN private and public network options exist for IoT deployments that require LoRaWAN Class B or C modes.
Also see An In-depth look at LoRaWAN® Class A Devices
An In-depth Look at LoRaWAN® Class B Devices
An In-depth Look at LoRaWAN® Class C Devices
Recommendation: If possible, register your devices’ EUIs and keys on the network first, before activating them or installing their batteries. When devices first power up, they immediately try to join a LoRaWAN network. If the device is not registered on the network yet, it will keep trying to join without success. This wastes battery power and may lead to future delays in the device’s network join time. In order to protect their batteries, some devices go into slow network join mode if they fail to join the network on initial power-up. When in this slow join mode it may take the device up to 24 hours to successfully join the network.