...
Log In / Choose Environment
To login, proceed to http://lns.az.mydevices.com and login. Everyone has his/her own account for logging in.
...
To begin, make sure that you have mydevices-live selected in the dropdown. This Organization includes both IoT in a Box Staging & Production (and may include others such as Dev). A bit more information can be found in Find Application ID or Device Profile IDs.
...
Hardware Lookup
Look up specific hardware by its ID using the search field at the top.
...
| Info |
|---|
Gateway Note: Gateways should not include the eui- portion. Although we include this moniker as part of our Device IDS, technically this is not allowed for ID nomenclature and Azure will not find the gateway if you include it. Just leave off the “eui-” part and use the remaining hex code ID. |
...
Viewing Device Info
After looking up some hardware, clicking on its ID in the search list will drill down into device details.
...
Similar to usage on TTN, hardware models need to be fully defined in the LNS. This includes information such as the Class of LoRa hardware, Join methods supported, etc. You can find this information under the Device-Profiles section.
...
| Tip |
|---|
Reminder: Just to be clear, the LNS is similar to TTN where you are using the LNS to define models but we still continue to use our IoT Console to register individual pieces of hardware that then utilize these device profiles. |
| Info |
|---|
Note: Generally this only needs to be done once per model (or possibly per Manufacturer). For example, once Dragino is defined in the device profiles, we only need additional profiles if a new piece of hardware operates significantly differently (e.g. Class C vs A devices). |
...
After selecting the right environment, you can then create a new profile, specifying all the LoRa details to support the hardware. Any relevant additional tips or gotchas when doing so in the LNS can be added to this document our help articles to help you out.
...