Add devices - disk91/helium-chirpstack-community GitHub Wiki

Migrate devices from a legacy Helium console

A wizard has been created to simplify the mass migration of devices from Helium Legacy to Chirpstack LNS. We recommend to migrate a first device to check that everything is correct. You will have to manually create your integration with your application server as currently this can't be automatically setup. Please notice that the payload format from chirpstack is different from the one helium legacy used. Once the end-to-end communication is working, you can migrate the rest of the fleet.

Only if your device was on a legacy console with the same OUI as the Chirpstack console (same connectivity provider) it can be live migrated. In the other situation your device will have to rejoin to communicate on the network. Well developed devices will rejoin on their own after a certain time ( can be up to 1-2 days ), other will require a reboot.

Manually add a device into chirpstack

You can add a device into chripstack in a normal way... but ... you have a certain consideration to care about appEUI: Chripstack does not use appEUI and as a consequence it is setup to 0. Helium cares about appEUI. So if your device is setup with an appEUI set to 0, nothing special needs to be done. If your device has an appEUI already setup you will have to let Helium knows that appEUI.

Since version 1.4, the appEUI can be setup in the new field JOIN_EUI you see on device setup you can setup your appEUI in the JoinEui field.

The previous method is also working, you can setup the appEUI as a Device Variable named app_eui with the appEUI hextstring value. This second method must be used if you want to have the appEUI field in the http/mqtt helium payload using the forwarder component.

...