chirpstack / chirpstack

ChirpStack open-source LoRaWAN Network Server
https://www.chirpstack.io/
MIT License
468 stars 133 forks source link

Feature request: Pass vendor information from device-profile template #125

Open trivialkettle opened 1 year ago

trivialkettle commented 1 year ago

Hi, I could need the vendor (and model) information of a device. The device-profile templates contain vendor information (and sometimes model information in the name).

Would it be possible to pass the vendor information from a device-profile template to the actual device profil? Or do I just miss any API call to get this information for a device?

Another way I can think of to get vendor/model information into a device profile would be to enter it in description (e.g. as JSON). Is there a better way?

Do you accept PRs for the lorawan-devices-repository you forked from TTN?

Best Regards

rsebi commented 1 month ago

I think this should be updated as TTN as some updates that came in.

trivialkettle commented 1 month ago

TTN updated their license, so its not possible to use a newer version

rsebi commented 1 month ago

I could not find license info from their repo however found a contributor license.

Can we use codecs from respective manufacturers github repo which they made available? From my test none of browan codec are correct. However Laird and Tektelic are still working fine.

trivialkettle commented 1 month ago

@rsebi The related issue: https://github.com/chirpstack/chirpstack/pull/61

rsebi commented 3 weeks ago

@rsebi The related issue: #61

Forgive my ignorance i just went through the whole convo regarding this subject here and across forum posts. As things stand might @brocaar start accepting for PR for the device profiles given that manufacturers create the codec (with licenses) so that as a community we can start somewhere. Alternatively @brocaar could provide an insight/update on how to chirpstack plan to move forward on this matter without pulling any troubles. Some could even reach out to manufacturers (respective use cases) and seek permission for codec use, and thus i believe over time, together we will be able to have a sizable database of devices ready for chirpstack.

Given I work on chirpstack extensively, would love to spare sometime for community as do others which I am quite sure.