Creating Chirpstack Organizations for myDevices Clients

This article covers giving our white label clients and partners access to their own Chirpstack instance (known as an Organization) so they can upload devices, view LNS logs and troubleshoot issues.

1. Log into Chripstack as an Global Admin user. (Rob or Adrian can provide this access)

2. In the left sidebar, click on Organizations, then +Create. Fill out the form as follows.
   
   

   Open

   

3. In the left sidebar, go to All Users, then +Create. Fill out the form with the user’s email address, a note about which realm they are associated with, and generate a random password for them and make a note about it. Check Is Active. Do NOT make them a Global Admin, as this would allow them access to everyone’s Chripstack Organization!
   
   Repeat this for each user who should have access to the new organization.
   
   

4. Pick the new organization from this picker:
   
   
   

   Open

   

   The Org picker does not let you browse all entries, you may need to type a few letters.

5. Go to Org. Users in the left sidebar, then +Add. Enter the email address for a user created in step #3. Typically we make one person the Organization Admin, all others can get the Device Admin / Gateway Admin checkboxes.

Repeat this for each user who should have access to the organization.

Please add Brent (bmeriwether@mydevices.com) as an Organization Admin as well, so he has visibility to all customer Orgs.

6. Go to Services-Profiles in the left sidebar and click +Create

Copy the settings for either US915 Azure or US915 UDP below. These can also be copied from an existing organization.

7. Go to Devices-Profiles in the left sidebar, then +Create

A device profile will need to be created for each Device Class/Frequency Region/Communication Type combo. You can copy the settings and naming for these from other whitelabels. Here are some examples:

US915 Azure Class A: https://lns.mydevices.com/#/organizations/23/device-profiles/f918bc01-d3bc-488c-90cd-004805207ce9

US915 Azure Class C: https://lns.mydevices.com/#/organizations/40/device-profiles/cfde4b64-85fd-43f6-a245-240cbec3a350

US915 UDP Class A: https://lns.mydevices.com/#/organizations/23/device-profiles/ecf60023-03a6-4ebc-832e-f5ef60a001d4

US915 UDP Class C: https://lns.mydevices.com/#/organizations/23/device-profiles/b29cea85-187e-4e6b-a4c6-a8f9fa1b0b8d

Be sure to copy the settings from every tab when copying the above device profiles.

8. Go to Applications in the left sidebar and click +Create

You can copy the settings from embeddedworks once again here, from the APPLICATION CONFIGURATION tab

US915 Azure: https://lns.mydevices.com/#/organizations/23/applications/115

US915 UDP: https://lns.mydevices.com/#/organizations/23/applications/114

9. Once each Application has been created, click on it, and go to the Integrations tab. Set up an HTTP Integration with the following settings:

Payload Marshaler: JSON (legacy, will be deprecated)

Endpoint URL for events: http://prometheus.default.svc.cluster.local/v1/networks/iotinabox.chirpstackio/uplink

10. As a final step, you need to add any users you created in Chripstack to Keycloak, in the mydevices-lns realm. Contact Adrian if you need Keycloak access for this.

Keycloak myDevices LNS URL: https://auth.mydevices.com/auth/admin/mydevices-lns/console
For each user:

A) Go to Users → Add User and fill out as pictured:

B) After creating the user, go to their Credentials tab and enter the password you generated for them in step #3 above. Leave the toggle set to Temporary, and click Set Password to finish.

That’s it! Now your users can log in at https://lns.mydevices.com/#/login and they’ll be prompted to set a new password on first login.