The following will help guide in how to upload devices into your own Organization instance on our Azure Chirpstack LNS. This will allow you to directly upload Device IDs and register hardware for use with Chirpstack without having to contact myDevices.
Please contact us if you have not received your login information to your organization on Chirpstack. Organization access to upload devices directly to the LNS must be granted by myDevices.
Things you will need to get started
Your IoT Console credentials - You will use the IoT Console to upload Device IDs and to register devices into the LNS.
Your Chirpstack Login credentials - You will need to reference your Application ID and Device Profile IDs when registering hardware as found in the Chirpstack console.
Upload process for Chirpstack Devices
The following will show you how to upload devices so that they appear in the IoT Console (for app usage) and are registered in the Chirpstack LNS (for network connectivity).
We strongly recommend using the IoT Console to register devices on Chripstack. Not only does this save you a step, it is an easier and less trouble prone method than manually adding them from the Chirpstack console directly.
<video showing them how to do this, covering:
Device Registry screen - upload device dialog
How to Locate their Organizations ID and Device-Profile to specify in the dialog
How do I find my Application ID?
After logging into the Chirpstack console you can select Applications link and you will find your Application ID. You can reference the above video that demonstrates this.
You will use the numerical ID value during registration.
Where do I find the list of Device Profile IDs?
After logging into the Chirpstack console you can select the Device-profiles link and you will find a list of profiles for your use. You can reference the above video that demonstrates this.
From the Device-profiles screen, locate the correct profile for this hardware & deployment. If you need help identifying which Profile to use, please see our tips.
You will use the numerical ID value of the profile when registering it in the Console.
For example, in the below URL for a device-profile you will use the bolded ID portion.
https://lns.mydevices.com/#/organizations/20/device-profiles/f8b56210-d87f-4098-be8d-d41cc5eb8f1f
Tips for selecting Device Profiles / which Device Class to use
Depending upon the complexity of your organization, you may see several Device-Profiles to choose from. You should select the profile which most closely matches with the hardware being added.
1: Match the sensor to the correct Frequency and Gateway
For example, if you are adding a device that uses the EU868 band and is being connected to an EU UDP gateway you should look for something such as “EU868-UDP”.
See: List of frequencies by country
2: Match the sensor to the correct Device Class
In some cases you may see a profile for Class A versus Class C devices. If you are uncertain which Class of device the sensor is, please refer to the manufacturer datasheets and information. You may find this type of resource linked in our dashboard under the Resources tab in Device Settings.
As a sort of general rule:
Class A for battery powered devices that wake up to communicate and have long battery life.
Class C for devices are often hardwired and stay awake so that they can react quickly to commands, such as actuators.
Device was already in Console but I still need to add it to Chirpstack
You can still use the IoT Console to register it! Simply follow the exact same process as if you were adding a new piece of hardware. During the registration step the dialog will indicate that it Skipped adding it into the Registry, but it will still proceed with registering the device on Chirpstack.
We strongly recommend doing all operations from the IoT Console where possible. Although there is an option to manually register sensors in Chirpstack’s console, there are greater chances of mistakes being made.