Azure (LNS)

CSIO (US) is lns.mydevices.com
CSIO (FR) is lns.eu.mydevices.com

General

Identifying UDP vs non-UDP when registering devices

todo

Gateway Registration

By script

Batch registration can be done by script. You will need to use the correct script based on whether you are registering to the CSIO (US) or different.

Usage syntax:

brent@computer:~$ ./gateway-bulk-import.sh help

     Simple script to bulk upload gateways to Chirpstack (lns.mydevices.com)

     Network ID:
        EU868: 26
        AS923: 25
        AU915: 24
        US915: 8
     Organization IDs:
        myDevices: 4
        Primeorigins: 12

     Usage:
        gateway-bulk-import [CSV_FILE] [NETWORK_ID] [ORG_ID]

     CSV File format:
        gateway_id
        01020304050607

So normally this would be adding to US-915 and on our Organization.

brent@computer:~$ ./gateway-bulk-import.sh femto_chirpstack_03172022.csv 8 4

Which would register the gateways in file femto_chirpstack_03172022.csv to the US915 network and our myDevices Org.

Device Specific Notes

Vutility

When UDP is being used (which is generally what you’d find for 3rd party external devices)
Application 87 (myDevices Network Server
Device-Profile: US915 - Class A - 1.0.2/B - UDP (352ca76d-8cba-4330-a340-2b26328eefa4)
If UDP is not called for, this is common for legacy Azure usage.
Example: Vutility Hotdrop 2.0 on legacy Azure
Application 39 (US915-vutility-legacy-azure)
Device Profile: US915 - Class A - 1.0.3/A (2e324e95-570a-4a09-9891-e9601f077377)

Support & QA