Device Pre-Provisioning via ChirpStack Platform
Overview
This tutorial systematically guides through the process of configuring LoRa devices via the ChirpStack platform, covering the complete path from obtaining basic parameters to verifying device network onboarding.
1. ChirpStack Platform Operations
Step 1. Log in to ChirpStack Platform
Log in to the chirpstack platform to view/register devices (contact Neuron technical support for account credentials)
Select the tenant to which devices need to be added
Neuron Demo is used as an example here. The specific tenant should be determined by the tenant pre-configured for the platform account by Neuron technical support.
Step 2. Configure Device Profiles
Before adding device configurations, you need to know the device's frequency band and channels:
- AS923 is used by default in Hong Kong
- CN470 is used by default in mainland China
Note frequency band distinction: Milesight's 470-band gateways and devices are pre-configured with 470_1 by default, which corresponds to CN470 channels 8-15.
2.1 Access Profile Configuration Page
2.2 Add Profile Information
- Profile name and description
- Device frequency band
- Device channels (can be ignored for Hong Kong frequency bands)
- Use default settings for other parameters
2.3 Enable ClassA or ClassC
Class A devices automatically enter sleep mode when not in reporting cycles; if reverse control is supported, they only respond to command delivery during reporting windows.
Class C devices do not sleep outside reporting times and support real-time command delivery.
Class A is enabled by default. Typically, battery-powered devices only require Class A.
DC-powered devices require Class C
Step 3. Create Device
3.1 Access Applications Under Tenant
This section displays all Applications created by the user under this tenant.
3.2 Access Application Sub-items
This section displays all devices registered by the user under this Application sub-item.
3.3 Add Device
Access device addition page
Fill in device information
- Device name
- Device description
- Device DevEUI: Usually printed on the device as its unique identifier
- Device profile
Add Application key
Application key is the credential for devices to join the gateway, provided by the manufacturer. Default Milesight Application key
see below
Create device after confirming information is correct
Note: DevEUI cannot be incorrect. It cannot be modified after saving, while other parameters support editing.
Step 4. Verify Device Network Onboarding Status
After adding the device, verify whether network onboarding is successful. Check the last reported time, activation parameters, or Events options to determine onboarding status.
Data reported - device onboarded
Activation parameters present - device onboarded
Join event and data reporting event present - device onboarded
Onboarding failure:
Last reported time shows "Never" - device not onboarded
No activation parameters - device not onboarded
No join event - device not onboarded
2. Device Access to Neuron Data Platform
Refer to LoRaWAN Device Access to register devices on the Neuron platform.