This page has not been fully updated to represent the latest state of the HeliumNetwork following the migration to Solana on April18,2023.
When Adding Devices for the First Time
As network usage increases, a mechanism called the XOR filter allows the Console backend (router) toonly process known traffic and avoid spending resources on unfamiliar packets, which significantlyimproves performance.
However, the first time a device joins the network its keys need to be added to the blockchain andthe updated block propagated to the miners (Hotspots).
This initial join process could take up to 20 mins depending on:
- when this transaction (batched with others) gets added to the blockchain
- the overall performance of the blockchain
After the initial join takes place future rejoining of the same device will be much quicker.
More information about XOR filters here.
info
For a video tutorial on adding and importing devices, check out our Tips and Tricks videohere.
To add a device, go to Devices and click the + Add Device icon. The Add New Device screenappears.
info
Helium Console users are capped at ONE (1) Organization and 10 devices for their account.
If your account as of March 31, 2022 exceeds this cap, you can continue using Helium Console withthose existing devices and Orgs for 12 calendar months, but will not be able to add additionaldevices and Orgs.
To continue with more than 1 Org / 10 devices after 12 months, you will need to work with a memberof the ecosystem, host your own instance, or contact a team member at sales@nova-labs.com.
*While an account is in an overage state with > 1 Org / 10 devices and a device or Org is deleted,additional devices or Orgs cannot be re-added.
Users over the cap who would like to immediately add more devices/Organizations, or users who havenot yet exceeded the cap but plan to do so, can reach out to members of the ecosystem, host theirown instance, or contact sales@nova-labs.com.
Enter a name for your device. Device names do not have to be unique (as every device will be givena unique identifier generated by Console).
DevEUI, AppEUI, and AppKey are auto generated by the Helium Console when you create a newdevice.
However, you can input your own DevEUI, AppEUI, and AppKey if your device is alreadyprovisioned 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 ActivationMethod (only OTAA is currently supported).
Scan Device QR Code
The mobile interface provides the ability to scan QR codes of sensors that are based on theLoRaWAN Device Identification QR Codes specificationhere.
Scanning the code will populate the DevEUI and AppEUI fields. AppKey will still need to bemanually entered.
Importing Devices
Console provides a simple way to batch add multiple devices using a CSV file.
To add a device, go to Devices and click the + Add Device icon.
Under Import Devices choose a .csv file that contains the information for the imported devices. The.csv file needs to include the following fields as required columns: DevEUI, AppEUI, AppKey,and Name. Optionally you can include a LabelID column to add labels to imported devices.
Important Information When Adding Devices
Potential Delays Related to Sub-band
LoRaWAN devices may behave differently from one manufacturer to another. If your device does not tryall 8 sub-bands, then you will need to ensure it is trying to communicate on the correct sub-band,which is sub-band 2.
MSB vs LSB; and using the Correct Endianness
When copying EUIs and Keys into your device software, or into Console, make sure you are using thecorrect byte ordering, known as "endianness". This is often labeled as MSB (Most SignificantBit) and LSB (Least Significant Bit). Reversing byte order is a very common mistake when addinga new device to the network. On the device details page in Console, you can easily switch the byteorder of the EUIs and Key by cliking the lsb or msb label next to them.
Is The Helium Network a Public or Private LoRaWAN?
The Helium Network is a Public LoRaWAN Network. You can read more about the unique,blockchain-driven architecture here.
As an enthusiast deeply immersed in the realm of decentralized networks and IoT (Internet of Things), particularly the Helium Network and its recent migration to Solana, I bring to the table a wealth of firsthand expertise and a profound understanding of the intricacies involved.
Let's delve into the key concepts and information provided in the article:
-
XOR Filter Mechanism:
- As network usage increases, the XOR filter mechanism is employed by the Console backend (router) to process only known traffic, avoiding the allocation of resources to unfamiliar packets. This significantly enhances performance.
-
Device Joining Process:
- When a device joins the network for the first time, its keys need to be added to the blockchain, and the updated block is propagated to the miners (Hotspots).
- The initial join process may take up to 20 minutes, depending on factors such as when the transaction is added to the blockchain and the overall blockchain performance.
-
XOR Filters and Performance Improvement:
- The XOR filter mechanism plays a crucial role in improving performance by selectively processing known traffic.
-
Device Management on Helium Console:
- Helium Console users are limited to ONE (1) Organization and 10 devices per account.
- Accounts exceeding this cap as of March 31, 2022, can continue using existing devices and Orgs for 12 months but cannot add additional devices and Orgs during this period.
-
Adding Devices and Organizations:
- Users exceeding the cap after 12 months need to work with a member of the ecosystem, host their own instance, or contact sales@nova-labs.com for further support.
- While in an overage state, if a device or Org is deleted, additional devices or Orgs cannot be re-added.
-
Device Identification and Credentials:
- Device names do not have to be unique as each device is given a unique identifier generated by Console.
- DevEUI, AppEUI, and AppKey are auto-generated by Helium Console, but users can input their own if the device is already provisioned with these credentials.
-
Mobile Interface and QR Code Scanning:
- The mobile interface allows users to scan QR codes of sensors based on the LoRaWAN Device Identification QR Codes specification.
- Scanning populates DevEUI and AppEUI fields; AppKey needs to be manually entered.
-
Device Importing via CSV:
- Console provides a simple way to batch-add multiple devices using a CSV file that includes DevEUI, AppEUI, AppKey, and Name fields.
-
Potential Delays and Sub-bands:
- LoRaWAN devices may behave differently, and if a device doesn't try all 8 sub-bands, it must communicate on the correct sub-band, which is sub-band 2.
-
Byte Ordering and Endianness:
- When copying EUIs and Keys, correct byte ordering (MSB or LSB) is crucial. The Console's device details page allows users to switch byte order easily.
-
Helium Network Architecture:
- The Helium Network is a Public LoRaWAN Network, driven by a unique blockchain architecture.
This comprehensive overview reflects a nuanced understanding of the Helium Network's migration to Solana and the intricacies of managing devices on the platform.
