Changes to Device Profiles

Viewed 2

We have just updated to v4.19.0 and I was a bit surprised by the changes to the device profiles.
From the changelog, I was under the impression that the import of vendor- and community provided device profiles was optional and that it would still be possible to manually add global device profiles similar to the way it was before: Adding device profile templates on the NS makes these accessible for all tenants.

But when I click on "add Vendor" on the NS, i get sent to the Github repo.
I think this is a great feature, just wondering whether it would still be possible to add global device profiles directly on the Chirpstack UI, instead of using the external UI and then importing it.

Am I missing something or is that how it's supposed to work from now on?
Thanks!

1 Answers

just wondering whether it would still be possible to add global device profiles directly on the Chirpstack UI, instead of using the external UI and then importing it.

This is indeed no longer supported. The main use-case of the global device-profiles is to build a publicly available repository of device-profiles that users can use and contribute to.

You could still create device-profiles through the UI and import these without creating a PR (e.g. in case these are profiles for devices that are not publicly available). At this moment adding UI interfaces for managing global device-profiles in ChirpStack itself is not planned.