Adding Devices to Helium is very easy and if you follow the steps provided you should have no problem adding any of our sensors to the Helium Public Network. Links for quickstart:
To register for an account, visit Helium Console and click Register.
During Registration, you’ll be asked to provide an Organization name and a Team name.
Define an Organization name for the top level owner of the account (ie: company name). Think of Teams as a way to organize groups of devices.
A confirmation email will be sent to the email address used to create an account. You must confirm the account in order to continue using Console. If you did not receive an email, please check your spam folders.
Helium Console allows developers to add devices and grab the device identifiers to load onto their device firmware that authenticates and identifies the device for the Helium Network.
To add a device, go to Devices and click the + Add Device icon on the top right of the window.
Enter a name for your device. Device names do not have to be unique (as every device will be given a unique identifier generated by Console).
AppKey are auto generated by the Helium Console when you create a new device. However, you can input your own
AppKey if your device is already provisioned with these credentials.
- Device EUI – 64 bit end-device identifier, sometimes called Manufacturer EUI
- App EUI – 64 bit application identifier
- App Key – 128 bit AES key, used to secure communication between device and network
Once added, you’ll see a consolidated view of all your device details, as well as the Activation Method (only
OTAA is currently supported) and the LoRaWAN US Channels used by the Helium Network (which will always be
LoRaWAN devices may behave differently from one manufacturer to another. After adding a new device, it may take some time to join the network and begin receiving data. This can range from less than a minute to as long as several minutes(20). If your device does not try all 8 sub-bands, then you will need to ensure it is trying to communicate on the correct sub-band, which is sub-band 2.
When copying EUIs and Keys into your device software, or into Console, make sure you are using the correct byte ordering, known as “endianness”. This is often labeled as
MSB (Most Significant Bit) and
LSB (Least Significant Bit). Reversing byte order is a very common mistake when adding a new device to the network. On the device details page in Console, you can easily switch the byte order of the EUIs and Key by cliking the
msb label next to them.