Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 241.1
edited by Mengting Qiu
on 2024/08/20 17:29
Change comment: Uploaded new attachment "image-20240820172909-4.png", version {1}
To version 197.1
edited by Bei Jinggeng
on 2023/02/21 16:48
Change comment: Uploaded new attachment "image-20230221164809-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Bei
Content
... ... @@ -6,8 +6,10 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 +
9 9  == 1.1  Introduction ==
10 10  
12 +
11 11  === 1.1.1  What is The Things Network ===
12 12  
13 13  
... ... @@ -18,6 +18,7 @@
18 18  (((
19 19  The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
20 20  
23 +
21 21  
22 22  )))
23 23  
... ... @@ -31,6 +31,7 @@
31 31  (((
32 32  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
33 33  
37 +
34 34  
35 35  )))
36 36  
... ... @@ -40,28 +40,26 @@
40 40  LoRaWAN Gateway model: Existing Gateway
41 41  
42 42  
47 +
43 43  = 2.  Gateway Registration for Semtech UDP =
44 44  
45 45  
46 -(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
47 -
48 -
49 49  == 2.1  Primary LoRaWAN Server ==
50 50  
51 51  
52 -[[image:image-20220526134633-2.png||_mstalt="430196" height="540" width="1160"]]
54 +[[image:image-20220526134633-2.png||height="616" width="1323"]]
53 53  
54 54  Register Gateway
55 55  
56 56  
57 -[[image:image-20231121092510-1.png||height="617" width="1157"]]
58 58  
60 +[[image:image-20220526134826-4.png]]
59 59  
60 60  Put Gateway ID
61 61  
62 62  
63 -[[image:image-20231121092543-2.png||height="613" width="1159"]]
64 64  
66 +[[image:image-20220526134759-3.png]]
65 65  
66 66  Choose Frequency Band
67 67  
... ... @@ -71,7 +71,7 @@
71 71  
72 72  DRAGINO - Frequency Plan list  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  The Thing Network Frequency Plan List
73 73  
74 -AS923-1 (920-923)  (% style="display:none" %) (%%) ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
76 +AS923-1 (920-923)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
75 75  
76 76  AS923-1 (923-925)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-928 Mhz (AS923 Group 1)with only default channels
77 77  
... ... @@ -82,18 +82,19 @@
82 82  AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
83 83  
84 84  
85 -[[image:image-20220726134642-1.png||_mstalt="430287" height="344" width="660"]][[image:image-20220726135827-3.png||_mstalt="432978" height="214" width="394"]][[image:image-20220726135759-2.png||_mstalt="433953" height="218" width="554"]]
87 +[[image:image-20220726134642-1.png||height="344" width="660"]][[image:image-20220726135827-3.png||height="214" width="394"]][[image:image-20220726135759-2.png||height="218" width="554"]]
86 86  
87 -[[image:image-20231121092627-3.png||height="617" width="1174"]]
88 88  
89 89  
90 -[[image:image-20220526134919-5.png||_mstalt="433602"]]
91 +[[image:image-20220526134919-5.png]]
91 91  
92 92  Show Status
93 93  
94 94  
96 +
95 95  == 2.2  Secondary LoRaWAN Server ==
96 96  
99 +
97 97  === 2.2.1  Introduction ===
98 98  
99 99  
... ... @@ -100,6 +100,7 @@
100 100  The Dragino gateway has supports the Secondary server settings.
101 101  
102 102  
106 +
103 103  === 2.2.2  Below list the support products and Requirements: ===
104 104  
105 105  
... ... @@ -112,6 +112,7 @@
112 112  )))
113 113  
114 114  
119 +
115 115  === 2.2.3  Example ===
116 116  
117 117  
... ... @@ -118,6 +118,7 @@
118 118  The following takes Helium as a Secondary LoRaWAN server as an example
119 119  
120 120  
126 +
121 121  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
122 122  
123 123  
... ... @@ -124,11 +124,12 @@
124 124  The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
125 125  
126 126  
127 -[[image:image-20220526135049-6.png||_mstalt="432432"]]
133 +[[image:image-20220526135049-6.png]]
128 128  
129 129  Download and Install gateway-rs
130 130  
131 131  
138 +
132 132  === 2.2.5  Step 2: Back to Semtech UDP page ===
133 133  
134 134  
... ... @@ -135,22 +135,22 @@
135 135  Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
136 136  
137 137  
138 -​​​​[[image:image-20220526135125-7.png||_mstalt="431106"]]
145 +​​​​[[image:image-20220526135125-7.png]]
139 139  
140 140  Configuration of helium
141 141  
142 142  
150 +
143 143  = 3.  Gateway Registration for Basics Station =
144 144  
153 +
145 145  == 3.1  Introduction ==
146 146  
147 147  
148 148  (((
149 149  (((
150 -The LoRa Basics™ Station protocol simplifies the management of large-scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
159 +The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
151 151  
152 -(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
153 -
154 154  
155 155  )))
156 156  )))
... ... @@ -172,7 +172,7 @@
172 172  )))
173 173  
174 174  (((
175 -(% style="color:blue" %)**What do you need to prepare?**
182 +(% style="color:blue" %)**What do you need to prepare**
176 176  )))
177 177  
178 178  (((
... ... @@ -179,84 +179,73 @@
179 179  (((
180 180  A gateway that can access the internet normally
181 181  
189 +
182 182  
183 183  )))
184 184  )))
185 185  
186 -== 3.2  Step 1: Register Gateway ==
194 +== 3.2  Step 1: Add Gateway ==
187 187  
188 188  
189 189  (((
190 190  (((
191 -(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
199 +(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
192 192  )))
193 193  )))
194 194  
195 195  (((
196 196  (((
197 -Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page.
198 -
199 -[[image:image-20230728144218-7.png||_mstalt="433290" height="128" width="836"]]
205 +User can add your gateway into The Things Network V3 according to the previous step
200 200  )))
201 201  )))
202 202  
203 -[[image:image-20230728143449-2.png||_mstalt="433108"]]
209 +(((
210 +(((
211 +Following picture is the successful added.
204 204  
205 -Register Gateway
213 +
214 +)))
215 +)))
206 206  
217 +[[image:image-20220526135316-8.png]]
207 207  
208 -== 3.3  Step 2: Create the API key ==
219 +Add Gateway
209 209  
210 210  
211 -**API Key can be created manually**  ~-~-->  if users forgot to check the check box or switch to basic station mode from the Semtech UDP mode
212 212  
223 +== 3.3  Step 2: Create the API key ==
213 213  
214 214  
226 +user need to create the CUPS API key and LNS API key.
215 215  
216 -**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png||_mstalt="431132"]]
217 217  
229 +[[image:image-20220526135349-9.png]]
218 218  
219 -=== **1.) Generated by TTH** ===
231 +Create CUPS API key
220 220  
221 221  
222 -Users need to download these two key files and fill them into the gateway's TTN Basics Station configuration,
223 223  
224 -[[image:image-20230728150521-2.png||height="664" width="1019"]]
235 +[[image:image-20220526135428-10.png]]
225 225  
237 +Create LNS API key
226 226  
227 -(% style="color:red" %)**Note:**(%%) The "**Authorization: Bearer** " field should not be entered in the TTN Basics Station configuration of the gateway
228 228  
229 -[[image:image-20230728151807-3.png||height="423" width="1024"]]
240 +(% style="color:red" %)**Note : Please copy the API key.**
230 230  
231 231  
232 -=== **2.) Manually create API KEY: ** ===
233 233  
244 +== 3.4  Step 3: Update the gateway setting ==
234 234  
235 -==== CUPS API KEY ====
236 236  
237 -[[image:image-20220526135349-9.png||_mstalt="434460"]]
238 -
239 -
240 -
241 -==== LNS API KEY ====
242 -
243 -[[image:image-20220526135428-10.png||_mstalt="453791"]]
244 -
245 -
246 -(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.**
247 -
248 -
249 -==== Update the gateway setting ====
250 -
251 -
252 252  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
253 253  
254 254  
255 -[[image:image-20220526135528-11.png||_mstalt="454480"]]
250 +[[image:image-20220526135528-11.png]]
256 256  
257 257  paste the API key
258 258  
259 259  
255 +
260 260  == 3.5  Step 4: Access the gateway GUI ==
261 261  
262 262  
... ... @@ -263,11 +263,12 @@
263 263  User need to update the API key and install the Certificate
264 264  
265 265  
266 -[[image:image-20220526135601-12.png||_mstalt="452153"]]
262 +[[image:image-20220526135601-12.png]]
267 267  
268 268  Access the gateway GUI
269 269  
270 270  
267 +
271 271  == 3.6  Step 5: Configure Station ==
272 272  
273 273  
... ... @@ -278,17 +278,18 @@
278 278  
279 279  (% class="box" %)
280 280  (((
281 - CUPS Server URI  ~-~->  Server Address, Example: https:~/~/eu1.cloud.thethings.network:443
278 + CUPS Server URI  ~-~->  Server Adress
282 282   CUPS Authorization Key         ~-~->  Server CUPS API Key
283 283   LNS Authorization Key  ~-~->  Server LNS API Key
284 284   CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
285 285  )))
286 286  
287 -[[image:image-20220526135654-13.png||_mstalt="455169"]]
284 +[[image:image-20220526135654-13.png]]
288 288  
289 289  Congfigure Station
290 290  
291 291  
289 +
292 292  == 3.7  Start Station ==
293 293  
294 294  
... ... @@ -295,20 +295,22 @@
295 295  (((
296 296  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
297 297  
296 +
298 298  
299 299  )))
300 300  
301 -== 3.8  Successful Connection ==
300 +== 3.8  Siccessful Connection ==
302 302  
303 303  
304 304  If user completes the above steps,which will see live date in the TTN.
305 305  
306 306  
307 -[[image:image-20220526135734-14.png||_mstalt="455208"]]
306 +[[image:image-20220526135734-14.png]]
308 308  
309 309  Station live date
310 310  
311 311  
311 +
312 312  == 3.9  Trouble Shooting ==
313 313  
314 314  
... ... @@ -315,7 +315,7 @@
315 315  User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
316 316  
317 317  
318 -[[image:image-20220526135845-15.png||_mstalt="456560"]]
318 +[[image:image-20220526135845-15.png]]
319 319  
320 320  Station Log
321 321  
... ... @@ -323,11 +323,12 @@
323 323  
324 324  and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
325 325  
326 -[[image:image-20220526135940-16.png||_mstalt="455559"]]
326 +[[image:image-20220526135940-16.png]]
327 327  
328 328  Recore Log
329 329  
330 330  
331 +
331 331  = 4.  Configure node connection to TTNv3 =
332 332  
333 333  
... ... @@ -347,6 +347,7 @@
347 347  (((
348 348  (% style="color:#037691" %)**We take LES01 as an example.**
349 349  
351 +
350 350  
351 351  )))
352 352  )))
... ... @@ -372,21 +372,22 @@
372 372  )))
373 373  )))
374 374  
375 -[[image:image-20230221135445-1.png||_mstalt="428714" height="356" width="777"]]
377 +[[image:image-20230221135445-1.png||height="356" width="777"]]
376 376  
377 377  First create an application and fill in the custom information in it
378 378  
379 -[[image:image-20230221135520-2.png||_mstalt="427050" height="52" width="974"]]
381 +[[image:image-20230221135520-2.png||height="52" width="974"]]
380 380  
381 -[[image:image-20230221135810-3.png||_mstalt="428025" height="400" width="638"]]
383 +[[image:image-20230221135810-3.png||height="400" width="638"]]
382 382  
383 383  
384 384  Add a node device to the application
385 385  
386 386  
387 -[[image:image-20220526140044-18.png||_mstalt="453648"]]
389 +[[image:image-20220526140044-18.png]]
388 388  
389 389  
392 +
390 390  == 4.2  Step 2 ==
391 391  
392 392  
... ... @@ -394,11 +394,14 @@
394 394  (((
395 395  There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
396 396  
397 -[[image:image-20230221164809-2.png||_mstalt="430937" height="525" width="617"]]
400 +
398 398  )))
399 399  )))
400 400  
404 +[[image:image-20220526140132-19.png]]
401 401  
406 +
407 +
402 402  == 4.3  Step 3 ==
403 403  
404 404  
... ... @@ -405,9 +405,10 @@
405 405  Add APP EUI in the application:
406 406  
407 407  
408 -[[image:image-20230221140131-4.png||_mstalt="425984" height="569" width="674"]]
414 +[[image:image-20230221140131-4.png||height="569" width="674"]]
409 409  
410 410  
417 +
411 411  == 4.4  Step 4 ==
412 412  
413 413  
... ... @@ -414,11 +414,13 @@
414 414  **Add APP KEY and DEV EUI:**
415 415  
416 416  
417 -[[image:image-20230221140448-6.png||_mstalt="430339" height="535" width="647"]]
424 +[[image:image-20230221140448-6.png||height="535" width="647"]]
418 418  
419 419  
427 +
420 420  = 5.  TTN V3 integrated into MQTT server =
421 421  
430 +
422 422  == 5.1  Introduction ==
423 423  
424 424  
... ... @@ -426,6 +426,7 @@
426 426  (((
427 427  The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
428 428  
438 +
429 429  
430 430  )))
431 431  )))
... ... @@ -453,13 +453,13 @@
453 453  )))
454 454  )))
455 455  
456 -[[image:image-20220526140347-22.png||_mstalt="453700"]]
466 +[[image:image-20220526140347-22.png]]
457 457  
458 458  Fill in the username and password into MQTT.
459 459  
460 460  
461 461  
462 -[[image:image-20220526140420-23.png||_mstalt="451373"]]
472 +[[image:image-20220526140420-23.png]]
463 463  
464 464  
465 465  The Application Server publishes uplink traffic on the following topics:
... ... @@ -487,7 +487,7 @@
487 487  )))
488 488  )))
489 489  
490 -[[image:image-20220526140452-24.png||_mstalt="453401"]]
500 +[[image:image-20220526140452-24.png]]
491 491  
492 492  
493 493  (((
... ... @@ -496,7 +496,7 @@
496 496  )))
497 497  )))
498 498  
499 -[[image:image-20220526140708-25.png||_mstalt="455117"]]
509 +[[image:image-20220526140708-25.png]]
500 500  
501 501  (((
502 502  (((
... ... @@ -520,20 +520,24 @@
520 520  )))
521 521  )))
522 522  
523 -[[image:image-20220526140856-26.png||_mstalt="456755"]]
533 +[[image:image-20220526140856-26.png]]
524 524  
525 525  (((
526 -To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents: **vu8=**, which is the Base64 format for Hex BE EF  . **[[HEX to Base64 online converter tool>>https://base64.guru/converter/encode/hex]]**.
536 +To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
527 527  
528 -[[image:image-20240325082631-1.png||height="393" width="815"]]
538 +
539 +)))
529 529  
541 +(((
542 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
530 530  
531 -Below is the TTN output for this downlink command.
544 +
532 532  )))
533 533  
534 -[[image:image-20220526140936-27.png||_mstalt="456794"]]
547 +[[image:image-20220526140936-27.png]]
535 535  
536 536  
550 +
537 537  == 5.3  Send Downlink message ==
538 538  
539 539  
... ... @@ -551,7 +551,7 @@
551 551  
552 552  )))
553 553  
554 -[[image:image-20220526141021-28.png||_mstalt="452647"]]
568 +[[image:image-20220526141021-28.png]]
555 555  
556 556  downlink
557 557  
... ... @@ -559,7 +559,7 @@
559 559  
560 560  After sending, you can view it in live data.
561 561  
562 -[[image:image-20220526141052-29.png||_mstalt="454337"]]
576 +[[image:image-20220526141052-29.png]]
563 563  
564 564  downlink
565 565  
... ... @@ -575,7 +575,7 @@
575 575  
576 576  )))
577 577  
578 -[[image:image-20220526141116-30.png||_mstalt="451672"]]
592 +[[image:image-20220526141116-30.png]]
579 579  
580 580  downlink
581 581  
... ... @@ -606,17 +606,19 @@
606 606  )))
607 607  )))
608 608  
609 -[[image:image-20220526141149-31.png||_mstalt="454038"]]
623 +[[image:image-20220526141149-31.png]]
610 610  
611 611  downlink
612 612  
613 613  
628 +
614 614  = 6.  Route TTN data to Node-Red =
615 615  
616 616  
617 -Users can create an MQTT integration by following the steps described in "[[5.TTN V3 Integrated into MQTT Server>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20TTN/#H5.A0TTNV3integratedintoMQTTserver||_mstmutation="1"]]"
632 +Users can create an MQTT integration by following the steps described in "[[5.TTN V3 Integrated into MQTT Server>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20TTN/#H5.A0TTNV3integratedintoMQTTserver]]"
618 618  
619 619  
635 +
620 620  == 6.1  Edit mqtt-broker node ==
621 621  
622 622  
... ... @@ -629,22 +629,24 @@
629 629  **Port  :** 1883
630 630  )))
631 631  
632 -[[image:image-20220829160224-187.jpeg||_mstalt="526292" height="569" width="1128"]]
648 +[[image:image-20220829160224-187.jpeg||height="569" width="1128"]]
633 633  
634 634  
635 635  **Enter Username and Password**
636 636  
637 -[[image:image-20220829164358-188.png||_mstalt="486174" height="570" width="1130"]]
653 +[[image:image-20220829164358-188.png||height="570" width="1130"]]
638 638  
639 639  
656 +
640 640  == 6.2  Debug ==
641 641  
642 642  
643 643  Users can check logs by adding debug.
644 644  
645 -[[image:image-20220829164652-189.png||_mstalt="485472" height="572" width="1134"]]
662 +[[image:image-20220829164652-189.png||height="572" width="1134"]]
646 646  
647 647  
665 +
648 648  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
649 649  
650 650  
... ... @@ -656,9 +656,10 @@
656 656  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
657 657  
658 658  
659 -=== 6.3.1 Link Node-Red to Local TTN ===
660 660  
678 +=== 6.3.1  Link Node-Red to Local TTN ===
661 661  
680 +
662 662  Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  **[[dragino-end-node-decoder/LHT65N.json (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/LHT65N.json]]**
663 663  
664 664  For more information on importing Input Flow, check out this link: **[[Import Input Flow for Dragino Sensors>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0ImportInputFlowforDraginoSensors||style="background-color: rgb(255, 255, 255);"]]**
... ... @@ -674,7 +674,7 @@
674 674  
675 675  **v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
676 676  
677 -[[image:image-20221018100743-1.png||_mstalt="427739" height="573" width="1120"]](% style="display:none" %)
696 +[[image:image-20221018100743-1.png]]
678 678  
679 679  
680 680  
... ... @@ -681,11 +681,11 @@
681 681  (% style="color:blue" %)**2. Enter the MQTT configuration information**
682 682  
683 683  
684 -[[image:image-20221018100947-2.png||_mstalt="430079" height="560" width="1123"]](% style="display:none" %)
703 +[[image:image-20221018100947-2.png]]
685 685  
686 686  
687 687  
688 -[[image:image-20221018101102-3.png||_mstalt="425256" height="580" width="1121"]]
707 +[[image:image-20221018101102-3.png]]
689 689  
690 690  (% class="wikigeneratedid" %)
691 691  (% style="color:blue" %)**Finally, click "Update" and Deploy**
... ... @@ -695,23 +695,27 @@
695 695  "Connected" indicates that the Link Node-red to Local TTN is normal.
696 696  
697 697  (% class="wikigeneratedid" %)
698 -[[image:image-20220914140918-5.png||_mstalt="432523" height="602" width="1121"]]
717 +[[image:image-20220914140918-5.png||height="602" width="1121"]]
699 699  
700 700  
720 +
701 701  === 6.3.2 Check result. ===
702 702  
703 703  
704 704  Users can check logs by adding debug.
705 705  
706 -[[image:image-20220914140841-4.png||_mstalt="430456" height="600" width="1119"]]
726 +[[image:image-20220914140841-4.png||height="600" width="1119"]]
707 707  
708 708  
729 +
709 709  In addition,Users can access the lps8v2 gateway's built-in as server of **Node-Red Chart UI **via the URL((% style="background-color:yellow" %)__**//http:~/~/<hostname>:1880/ui or http:~/~/<local-IPV4-address>:1880/ui//**__(%%)) in your browser.
710 710  
711 711  
712 -[[image:image-20220914142021-7.png||_mstalt="429000" height="439" width="1143"]](% style="display:none" %)
713 713  
734 +[[image:image-20220914142021-7.png||height="517" width="1346"]]
714 714  
736 +
737 +
715 715  = 7.  Request Remote Support =
716 716  
717 717  
... ... @@ -721,22 +721,17 @@
721 721  )))
722 722  
723 723  * End node is connected to serial port to show the Join frequency and DR. (If possible)
724 -
725 725  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
726 -
727 727  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
728 -
729 729  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
730 -
731 731  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
732 732  
733 733  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
734 734  
735 735  * If the device is sending join request to server?
736 -
737 737  * What frequency the device is sending?
738 738  
739 -[[image:image-20220526141308-33.png||_mstalt="453778"]]
757 +[[image:image-20220526141308-33.png]]
740 740  
741 741  Console Output from End device to see the transmit frequency
742 742  
... ... @@ -745,7 +745,7 @@
745 745  
746 746  * Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
747 747  
748 -[[image:image-20220526141612-36.png||_mstalt="454142"]]
766 +[[image:image-20220526141612-36.png]]
749 749  
750 750  
751 751  Console Output from End device to see the transmit frequency
... ... @@ -764,7 +764,7 @@
764 764  
765 765  )))
766 766  
767 -[[image:image-20220526141739-37.png||_mstalt="457847"]]
785 +[[image:image-20220526141739-37.png]]
768 768  
769 769  Console Output from Gateway to see packets between end node and server.
770 770  
... ... @@ -785,13 +785,13 @@
785 785  
786 786  )))
787 787  
788 -[[image:image-20220526141823-38.png||_mstalt="456183" height="501" width="1144"]]
806 +[[image:image-20220526141823-38.png||height="501" width="1144"]]
789 789  
790 790  The Traffic for the End node in the server, use TTNv3 as example
791 791  
792 792  
793 793  
794 -[[image:image-20220526141917-39.png||_mstalt="457899"]]
812 +[[image:image-20220526141917-39.png]]
795 795  
796 796  The Traffic for the End node in the server, use TTNv3 as example
797 797  
... ... @@ -805,7 +805,7 @@
805 805  If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
806 806  
807 807  
808 -[[image:image-20220526141956-40.png||_mstalt="455832"]]
826 +[[image:image-20220526141956-40.png]]
809 809  )))
810 810  )))
811 811  )))
... ... @@ -814,181 +814,6 @@
814 814  
815 815  
816 816  
817 -[[image:image-20220526142033-41.png||_mstalt="452036"]]
835 +[[image:image-20220526142033-41.png]]
818 818  
819 819  Check if OTAA Keys match the keys in device
820 -
821 -
822 -= 8.  FAQ =
823 -
824 -== 8.1 How to import devices keys to TTN. ==
825 -
826 -
827 -**For TTS in LPS8v2**
828 -
829 -Open your application and click the button **Import end devices**
830 -
831 -[[image:image-20230423154012-1.png||_mstalt="426738" height="472" width="755"]]
832 -
833 -
834 -Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv
835 -
836 -You can specify **Fallback values** for Frequency plan and LoRaWAN and Regional Parameters version, in case the import file does not specify these settings for the device.
837 -
838 -You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated.
839 -
840 -Start the import by clicking the **Import end devices** button.
841 -
842 -[[image:image-20230423154040-2.png||_mstalt="427401" height="470" width="749"]]
843 -
844 -
845 -Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console.
846 -
847 -[[image:image-20230423154105-3.png||_mstalt="428467" height="478" width="763"]]
848 -
849 -
850 -If the import was successful, your devices are added to the list of end devices in your application.
851 -
852 -[[image:image-20230423154125-4.png||_mstalt="429481" height="480" width="766"]]
853 -
854 -Devices are now registered on The Things Stack.
855 -
856 -
857 -=== **JSON File Reference** ===
858 -
859 -
860 -The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices.
861 -
862 -Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions.
863 -
864 -Here is an example of an OTAA device description in the file:devices.json
865 -
866 -{{{{
867 - "ids": {
868 - "device_id": "my-device",
869 - "dev_eui": "0102030405060708",
870 - "join_eui": "0102030405060708"
871 - },
872 - "name": "My Device",
873 - "description": "Living room temperature sensor",
874 - "lorawan_version": "MAC_V1_0_2",
875 - "lorawan_phy_version": "PHY_V1_0_2_REV_B",
876 - "frequency_plan_id": "EU_863_870_TTN",
877 - "supports_join": true,
878 - "root_keys": {
879 - "app_key": {
880 - "key": "01020304050607080102030405060708"
881 - }
882 - }
883 -}
884 -}}}
885 -
886 -Multiple end devices can also be contained in a single file like so:devices.json
887 -
888 -{{{{
889 - /* device 1 */
890 -}
891 -{
892 - /* device 2 */
893 -}
894 -}}}
895 -
896 -The format above is considered by the Console and CLI as a JSON stream, processing one object at a time. For more details in how to use the file
897 -
898 -
899 -=== **CSV File Reference** ===
900 -
901 -
902 -The Things Stack has support for importing end devices from CSV (comma-separated values) files. This is useful when batches of end devices are managed in Microsoft Excel or any other spreadsheet or database that can export to CSV file.
903 -
904 -The CSV import in The Things Stack uses the following settings:
905 -
906 -* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient;
907 -
908 -* Header row is required
909 -
910 -* On each row, the same number of fields as on the header line
911 -
912 -* Use quotes to use in a field value;
913 -
914 -* Use double quotes to escape quotes
915 -
916 -* Unknown header columns are permitted and ignored
917 -
918 -* Name and id cannot have capital letters and special characters
919 -
920 -* Example column lorawan_phy_version is not needed
921 -
922 -(% style="display:none" %)
923 -
924 -
925 -
926 -=== **Example** ===
927 -
928 -
929 -Minimal example:
930 -
931 -{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key
932 -1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111
933 -2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222
934 -3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333
935 -}}}
936 -
937 -All columns for a LoRaWAN 1.0.4 device:
938 -
939 -{{{id;dev_eui;join_eui;name;frequency_plan_id;lorawan_version;lorawan_phy_version;brand_id;model_id;hardware_version;firmware_version;band_id;app_key
940 -test-one;1111111111111111;1111111111111111;Device 1;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;11111111111111111111111111111111
941 -test-two;2222222222222222;2222222222222222;Device 2;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;22222222222222222222222222222222
942 -test-three;3333333333333333;3333333333333333;Device 3;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;33333333333333333333333333333333
943 -}}}
944 -
945 -
946 -(% style="display:none" %) (%%)
947 -
948 -=== **Excel Template** ===
949 -
950 -
951 -[[Download the Excel template>>url:https://www.thethingsindustries.com/docs/getting-started/migrating/tts-end-devices-csv-template.xlsx]]. You can remove all columns that are not required (see above).
952 -
953 -
954 -== 8.2 How to download and analyze End Device's log？(% style="display:none" %) (%%) ==
955 -
956 -
957 -~1. Get information about a single node
958 -
959 -Download this file in the node's live data interface
960 -
961 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20of%20Dragino%20LoRaWAN%20Packet%20Analyze%20Tool/WebHome/image-20230928163751-2.png?width=1278&height=506&rev=1.1||alt="image-20230928163751-2.png" height="506" width="1278"]]
962 -
963 -
964 -2. Get information about the entire Application
965 -
966 -Click the "See all activity" button on the main interface of the application
967 -
968 -[[image:image-20231019113039-1.png||height="678" width="1312"]]
969 -
970 -
971 -Download this file in application  live data interface
972 -
973 -[[image:image-20231019113212-4.png||height="567" width="1277"]]
974 -
975 -
976 -After the data collection is completed, you can send this file directly to our technical support personnel for analysis.
977 -
978 -
979 -You can also use the packet analysis tool developed by our company to check it yourself. Please refer to the following [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20of%20Dragino%20LoRaWAN%20Packet%20Analyze%20Tool/#H3.ThethingsNetwork]] to use this tool.
980 -
981 -[[image:image-20240117170517-1.png]]
982 -
983 -
984 -
985 -= 9. Trouble Shooting. =
986 -
987 -== 9.1 How to solve the problem of MIC Mismatch？ ==
988 -
989 -
990 -Please refer to the link below:
991 -
992 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F>>url:http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F]]
993 -
994 -
image-20230423154012-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -140.9 KB
Content
image-20230423154040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.0 KB
Content
image-20230423154105-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -188.5 KB
Content
image-20230423154125-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -102.1 KB
Content
image-20230728143343-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -43.2 KB
Content
image-20230728143449-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -43.2 KB
Content
image-20230728143505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -16.7 KB
Content
image-20230728144218-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20230728145557-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -53.6 KB
Content
image-20230728150521-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.9 KB
Content
image-20230728151807-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -149.0 KB
Content
image-20231019113039-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
image-20231019113131-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -207.7 KB
Content
image-20231019113137-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -207.7 KB
Content
image-20231019113212-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -168.8 KB
Content
image-20231121092510-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -126.5 KB
Content
image-20231121092543-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -121.0 KB
Content
image-20231121092627-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -125.3 KB
Content
image-20240117170517-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -63.1 KB
Content
image-20240325082631-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -55.9 KB
Content
image-20240325082714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -55.9 KB
Content
image-20240820171935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -92.6 KB
Content
image-20240820172327-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -79.9 KB
Content
image-20240820172513-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -45.8 KB
Content
image-20240820172909-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content