Adding a Device to the MetSci Chirpstack Console

How to add a Device to your MeteoScientific Chirpstack Console
𝐌𝐞𝐭𝐒𝐜𝐢 𝐂𝐨𝐧𝐬𝐨𝐥𝐞: metsci.ai/ms-c...
𝐁𝐮𝐲 𝐒𝐨𝐢𝐥 𝐌𝐨𝐢𝐬𝐭𝐮𝐫𝐞 𝐒𝐞𝐧𝐬𝐨𝐫: metsci.ai/LW-s...
𝐏𝐫𝐨𝐠𝐫𝐚𝐦 𝐒𝐞𝐧𝐬𝐨𝐫 𝐖𝐢𝐭𝐡 𝐓𝐡𝐢𝐬: metsci.ai/usb-...
𝐕𝐢𝐬𝐢𝐭: metsci.ai/home
𝐁𝐞𝐟𝐨𝐫𝐞 𝐲𝐨𝐮 𝐛𝐞𝐠𝐢𝐧, 𝐲𝐨𝐮'𝐥𝐥 𝐧𝐞𝐞𝐝:
-Device
-DevEUI
-AppEU
-AppKey
Template:
Naming convention: Device name - last 4 of DevEUI - position
Location:
Setup Date:
Use:
Last battery change:
Notes:
**
Events contain information from the SENSOR
Frames are from the GATEWAY. Frames can be received from multiple gateways. Frames have events in them plus some physical LoRaWAN layer data

[@kadirozdinc6065]

I have a question about AppEUI, according to 1.0.3, it is said that AppEUI must be unique but when I read chirpstack documentation, it says it is used only in JoinReq frame, should be just 0000000000000000. I am a little bit confused about it ? Could you please make it clear ? How must I provision my devices ?

[@meteoscientific]

It depends on the device and manufacturer. I've seen it work both with 16 zeros and with a unique AppEUI. As a rule of thumb, I'd use the unique one if you have it. Does that help?

[@kadirozdinc6065]

​@@meteoscientific I dont have any unique key. At first glance, AppEUI sounds identifer of application in Chirpstack when I read 1.0.3 spec and should be unique per application.Chirstack documentation says when provisioning, needed keys are only DevEUI and Appkey, let AppEUI be zeros for all application.
Lets say I have different application in chirpstack and if all AppEUI's are same, is any kind of collision possible ?

[@grayhatguycompany1074]

The zero out is more for devices that do not have an appeui assigned. It basically creates a placeholder so cs can onboard and assign apps/integrations. It does this dif than other consoles. If you have an existing appeui assigned to an integration through a previous console integration or OEM that you wish to use after migration to cs then use the existing appeui not 0s. **Chirptack applications can hold multiple deveuis that differentiate the data so no collisions. The appeui is not associated with the cs application so more reasons for no collision** see rest api for more details of applications integrations and associated devs

[@meteoscientific]

@@kadirozdinc6065 via a pro (Mark Twain IV)
"The zeroe are more for devices that do not have an appeui assigned. It basically creates a placeholder so Chirpstack (CS) can onboard and assign apps/integrations.
If you have an existing appeui assigned to an integration through a previous console integration or OEM that you wish to use after migration to CS then use the existing appeui not zeros.
Chirpstack applications can hold multiple deveuis that differentiate the data, so no collisions. The appeui is not associated with the CS application so more reasons for no collision. See rest api for more details of applications integrations and associated devs."

[@kadirozdinc6065]

Thank you all so much for your great explanations

[@fereal3505]

How can i acces this data? Tried with mqtt, but it doesn`t work.

[@meteoscientific]

We don't have a solid MQTT integration yet, here are docs on how to use it: github.com/disk91/helium-chirpstack-community/wiki/Helium-compatible-Integration#mqtt-integration

[@fereal3505]

@@meteoscientific thank you