"Roaming" Helium Devices over Regions

Helium is a global network, it support devices deployed on any regions. Chirpstack is a Region based LNS: it support mulitple region but a device is attached to a given region (US915, EU868...) so Chirpstack has some limitation in regard of what you can do with Helium.

• You are selling devices & services over distribution channels, devices are pre-setup with credentials, you don't know when they are switched on in what region they will. End user select it but you don't.

• You have device that can move from a region to another (mapper, tracker applications) they can be in a given region (Let say EU868) and then move to another (let say US915).

With chirpstack natively, you can't really address these situations as the device is declared in a single region.

• By detecting a device is trying to join from a different region than the one currently setup, it will search for a device_profile using the same name but in the right region and dynamically update the device_profile used by that device.

• A device can automatically set the right region dynamically
• A device need to rejoin to switch region dynamically
• The first Join in the new Region is lost and a second join is required

The only thing that needs to be configure to enable this feature is to create different device profile with similar name in the tenant for each of the region you want to support.

The device_profile name contains the region and the name, make sure you maintain this name structure in your setup.