Changes for page Azure IoT

Last modified by Xiaoling on 2024/05/30 16:46
<
From version < 18.2 >
edited by Xiaoling
on 2023/01/05 13:59
To version < 15.1 >
edited by Xiaoling
on 2023/01/05 13:43
>
Change comment: Uploaded new attachment "image-20230105134348-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,9 @@
1 1  **Table of Contents：**
2 2  
3 -{{toc/}}
4 4  
5 5  
6 6  
7 7  
8 -
9 9  = 1. Deployment Guide =
10 10  
11 11  
... ... @@ -15,11 +15,10 @@
15 15  == 1.1 Prerequisites ==
16 16  
17 17  
18 -1.  Access to an Azure account. [[Create a new account>>url:https://signup.azure.com/]]
16 +1. Access to an Azure account. [[Create a new account>>url:https://signup.azure.com/]]
19 19  
20 -2. An application in The Things Stack. [[See instructions>>url:https://www.thethingsindustries.com/docs/integrations/adding-applications/]]
18 +1. An application in The Things Stack. [[See instructions>>url:https://www.thethingsindustries.com/docs/integrations/adding-applications/]]
21 21  
22 -
23 23  == 1.2 Create API Key ==
24 24  
25 25  
... ... @@ -61,7 +61,7 @@
61 61  
62 62  [[image:image-20230105112836-2.png]]
63 63  
64 -Click (% style="color:blue" %)**Review + Create**(%%), then (% style="color:blue" %)**Create**.
61 +Click (% style="color:blue" %)**Review + Create**(%%), then (% style="color:#037691" %)**Create**.
65 65  
66 66  
67 67  (% style="color:red" %)**Note:**
... ... @@ -68,19 +68,17 @@
68 68  
69 69  Creating all resources can take up to five minutes. ☕
70 70  
71 -When the deployment is done, you’ll see the status .Your deployment is complete.
68 +When the deployment is done, you’ll see the status .Your deployment is complete
72 72  
73 -
74 74  [[image:image-20230105112836-3.png]]
75 75  
76 76  
77 77  After the deployment has finished, click (% style="color:blue" %)**Outputs**.
78 78  
79 -[[image:image-20230105135055-2.png]]
75 +[[image:image-20230105112836-4.png]]
80 80  
77 +The two outputs can now be copied into your integration settings as (% style="color:blue" %)**Azure IoT Hub hostname**(%%) and (% style="color:#037691" %)**Azure IoT Hub access key**(%%). Click on (% style="color:blue" %)**Enable/Update Azure IoT Hub integration**.
81 81  
82 -The two outputs can now be copied into your integration settings as (% style="color:blue" %)**Azure IoT Hub hostname**(%%) and (% style="color:blue" %)**Azure IoT Hub access key**(%%). Click on (% style="color:blue" %)**Enable/Update Azure IoT Hub integration**.
83 -
84 84  [[image:image-20230105112836-5.png]]
85 85  
86 86  
... ... @@ -102,9 +102,8 @@
102 102  Devices are created automatically as they join the network or send an uplink message. For the name of new devices, the end device ID in The Things Stack is used as the device ID in Azure IoT Hub.
103 103  
104 104  
105 -== 2.1 Creating Devices ==
100 +(% style="color:blue" %)**Creating Devices:**
106 106  
107 -
108 108  You can use Azure IoT Hub to create and claim devices in The Things Stack. This is useful to manage all your devices in one place, without having to use The Things Stack Console, CLI or API.
109 109  
110 110  (% style="color:blue" %)**Creating**(%%) a device allows you to add any LoRaWAN device by manually entering its information and security keys.
... ... @@ -115,10 +115,8 @@
115 115  
116 116  [[image:image-20230105112836-6.png]]
117 117  
118 -
119 119  As (% style="color:blue" %)**Device ID**(%%), enter any device ID you like. Hit (% style="color:blue" %)**Save**.
120 120  
121 -
122 122  (% style="color:red" %)**Note:**
123 123  
124 124  See [[ID and EUI constraints>>url:https://www.thethingsindustries.com/docs/reference/id-eui-constraints/]] for guidelines about choosing a unique ID.
... ... @@ -125,41 +125,38 @@
125 125  
126 126  [[image:image-20230105112836-7.png]]
127 127  
128 -
129 129  You will now have to setup the LoRaWAN specific settings of the device. Click on (% style="color:blue" %)**Device Twin**.
130 130  
131 -[[image:image-20230105134348-1.png]]
122 +[[image:image-20230105112836-8.png]]
132 132  
133 -
134 134  You will now be presented with a JSON document containing the Device Twin. You now have to add a new object called tags, which will contain an object called lorawan with the LoRaWAN specific tags. You will have to specify the following tags:
135 135  
136 -* (% style="color:#037691" %)**devEui:**(%%) the hexadecimal LoRaWAN DevEUI.
126 +* (% style="color:#037691" %)devEui:(%%) the hexadecimal LoRaWAN DevEUI.
137 137  
138 -* (% style="color:#037691" %)**joinEui:**(%%)** **the hexadecimal LoRaWAN JoinEUI (or AppEUI).
128 +* (% style="color:#037691" %)joinEui:(%%) the hexadecimal LoRaWAN JoinEUI (or AppEUI).
139 139  
140 -* (% style="color:#037691" %)**lorawanVersion:**(%%) either 1.0, 1.0.1, 1.0.2, 1.0.3 or 1.1.
130 +* (% style="color:#037691" %)lorawanVersion:(%%) either 1.0, 1.0.1, 1.0.2, 1.0.3 or 1.1.
141 141  
142 -* (% style="color:#037691" %)**regionalParametersVersion:**(%%) either 1.0, 1.0.1, 1.0.2 (or 1.0.2-a), 1.0.2-b, 1.0.3-a, 1.1-a or 1.1-b.
132 +* (% style="color:#037691" %)regionalParametersVersion:(%%) either 1.0, 1.0.1, 1.0.2 (or 1.0.2-a), 1.0.2-b, 1.0.3-a, 1.1-a or 1.1-b.
143 143  
144 -* (% style="color:#037691" %)**appKey:**(%%) the hexadecimal LoRaWAN AppKey.
134 +* (% style="color:#037691" %)appKey:(%%) the hexadecimal LoRaWAN AppKey.
145 145  
146 -* (% style="color:#037691" %)**nwkKey:**(%%) the hexadecimal LoRaWAN NwkKey (only when using LoRaWAN 1.1 or higher).
136 +* (% style="color:#037691" %)nwkKey:(%%) the hexadecimal LoRaWAN NwkKey (only when using LoRaWAN 1.1 or higher).
147 147  
148 -* (% style="color:#037691" %)**frequencyPlanId:**(%%) the frequency plan ID. See [[Frequency Plans>>url:https://www.thethingsindustries.com/docs/reference/frequency-plans/]] for the supported values.
138 +* (% style="color:#037691" %)frequencyPlanId:(%%) the frequency plan ID. See [[Frequency Plans>>url:https://www.thethingsindustries.com/docs/reference/frequency-plans/]] for the supported values.
149 149  
150 150  If your end device is a part of the [[LoRaWAN Device Repository>>url:https://www.thethingsindustries.com/docs/integrations/payload-formatters/device-repo/]], you may provide the identifiers of the device as part of an optional versionIdentifiers object. You can specify the following information as part of the identifiers:
151 151  
152 -* (% style="color:#037691" %)**bandId:**(%%) the band ID.
142 +* (% style="color:#037691" %)bandId:(%%) the band ID.
153 153  
154 -* (% style="color:#037691" %)**brandId:**(%%) the brand ID.
144 +* (% style="color:#037691" %)brandId:(%%) the brand ID.
155 155  
156 -* (% style="color:#037691" %)**firmwareVersion:**(%%) the firmware version.
146 +* (% style="color:#037691" %)firmwareVersion:(%%) the firmware version.
157 157  
158 -* (% style="color:#037691" %)**hardwareVersion:**(%%) the hardware version.
148 +* (% style="color:#037691" %)hardwareVersion:(%%) the hardware version.
159 159  
160 -* (% style="color:#037691" %)**modelId:**(%%) the model ID.
150 +* (% style="color:#037691" %)modelId:(%%) the model ID.
161 161  
162 -
163 163  (% style="color:red" %)**Note:**
164 164  
165 165  If the version identifiers are provided, the end device will automatically load the [[Payload Formatters>>url:https://www.thethingsindustries.com/docs/integrations/payload-formatters/]] from [[LoRaWAN Device Repository>>url:https://www.thethingsindustries.com/docs/integrations/payload-formatters/device-repo/]].
... ... @@ -200,15 +200,12 @@
200 200  
201 201  }
202 202  
203 -
204 204  [[image:image-20230105112836-9.png]]
205 205  
206 206  Click on (% style="color:blue" %)**Save**(%%) in the top-left corner. The end device will now be created in The Things Stack.
207 207  
196 +(% style="color:blue" %)**Deleting Devices:**
208 208  
209 -== 2.2 Deleting Devices ==
210 -
211 -
212 212  In the Azure Console, open your Azure IoT Hub resource. In the menu on the left, click (% style="color:blue" %)**IoT Devices**.
213 213  
214 214  Click on the checkbox in front of the device you want to delete, then click (% style="color:blue" %)**Delete**.
... ... @@ -217,18 +217,15 @@
217 217  
218 218  The end device will be deleted from Azure IoT Hub and The Things Stack.
219 219  
206 +(% style="color:blue" %)Example(TrackerD):
220 220  
221 -(% style="color:blue" %)**Example(TrackerD):**
222 -
223 223  [[image:image-20230105112836-11.png]]
224 224  
225 -
226 226  [[image:image-20230105112836-12.png]]
227 227  
228 228  
229 -(% style="color:blue" %)**Example(LHT65N):**
213 +(% style="color:blue" %)Example(LHT65N):
230 230  
231 -[[image:image-20230105135558-2.png||height="495" width="1360"]]
215 +[[image:image-20230105112836-13.png]]
232 232  
233 -
234 234  [[image:image-20230105112836-14.png]]
image-20230105135055-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20230105135507-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20230105135558-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -106.1 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0