Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 197.1
edited by Bei Jinggeng
on 2023/02/21 16:48
Change comment: Uploaded new attachment "image-20230221164809-2.png", version {1}
To version 222.1
edited by Bei Jinggeng
on 2023/10/19 11:30
Change comment: Uploaded new attachment "image-20231019113039-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -6,10 +6,8 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 -
10 10  == 1.1  Introduction ==
11 11  
12 -
13 13  === 1.1.1  What is The Things Network ===
14 14  
15 15  
... ... @@ -20,7 +20,6 @@
20 20  (((
21 21  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.
22 22  
23 -
24 24  
25 25  )))
26 26  
... ... @@ -34,7 +34,6 @@
34 34  (((
35 35  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 36  
37 -
38 38  
39 39  )))
40 40  
... ... @@ -44,26 +44,28 @@
44 44  LoRaWAN Gateway model: Existing Gateway
45 45  
46 46  
47 -
48 48  = 2.  Gateway Registration for Semtech UDP =
49 49  
50 50  
46 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
47 +
48 +
51 51  == 2.1  Primary LoRaWAN Server ==
52 52  
53 53  
54 -[[image:image-20220526134633-2.png||height="616" width="1323"]]
52 +[[image:image-20220526134633-2.png||_mstalt="430196" height="616" width="1323"]]
55 55  
56 56  Register Gateway
57 57  
58 58  
59 59  
60 -[[image:image-20220526134826-4.png]]
58 +[[image:image-20220526134826-4.png||_mstalt="432237"]]
61 61  
62 62  Put Gateway ID
63 63  
64 64  
65 65  
66 -[[image:image-20220526134759-3.png]]
64 +[[image:image-20220526134759-3.png||_mstalt="433550"]]
67 67  
68 68  Choose Frequency Band
69 69  
... ... @@ -84,19 +84,17 @@
84 84  AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
85 85  
86 86  
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"]]
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"]]
88 88  
89 89  
90 90  
91 -[[image:image-20220526134919-5.png]]
89 +[[image:image-20220526134919-5.png||_mstalt="433602"]]
92 92  
93 93  Show Status
94 94  
95 95  
96 -
97 97  == 2.2  Secondary LoRaWAN Server ==
98 98  
99 -
100 100  === 2.2.1  Introduction ===
101 101  
102 102  
... ... @@ -103,7 +103,6 @@
103 103  The Dragino gateway has supports the Secondary server settings.
104 104  
105 105  
106 -
107 107  === 2.2.2  Below list the support products and Requirements: ===
108 108  
109 109  
... ... @@ -116,7 +116,6 @@
116 116  )))
117 117  
118 118  
119 -
120 120  === 2.2.3  Example ===
121 121  
122 122  
... ... @@ -123,7 +123,6 @@
123 123  The following takes Helium as a Secondary LoRaWAN server as an example
124 124  
125 125  
126 -
127 127  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
128 128  
129 129  
... ... @@ -130,12 +130,11 @@
130 130  The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
131 131  
132 132  
133 -[[image:image-20220526135049-6.png]]
126 +[[image:image-20220526135049-6.png||_mstalt="432432"]]
134 134  
135 135  Download and Install gateway-rs
136 136  
137 137  
138 -
139 139  === 2.2.5  Step 2: Back to Semtech UDP page ===
140 140  
141 141  
... ... @@ -142,22 +142,22 @@
142 142  Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
143 143  
144 144  
145 -​​​​[[image:image-20220526135125-7.png]]
137 +​​​​[[image:image-20220526135125-7.png||_mstalt="431106"]]
146 146  
147 147  Configuration of helium
148 148  
149 149  
150 -
151 151  = 3.  Gateway Registration for Basics Station =
152 152  
153 -
154 154  == 3.1  Introduction ==
155 155  
156 156  
157 157  (((
158 158  (((
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/]]
149 +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/]]
160 160  
151 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
152 +
161 161  
162 162  )))
163 163  )))
... ... @@ -179,7 +179,7 @@
179 179  )))
180 180  
181 181  (((
182 -(% style="color:blue" %)**What do you need to prepare**
174 +(% style="color:blue" %)**What do you need to prepare?**
183 183  )))
184 184  
185 185  (((
... ... @@ -186,73 +186,83 @@
186 186  (((
187 187  A gateway that can access the internet normally
188 188  
189 -
190 190  
191 191  )))
192 192  )))
193 193  
194 -== 3.2  Step 1: Add Gateway ==
185 +== 3.2  Step 1: Register Gateway ==
195 195  
196 196  
197 197  (((
198 198  (((
199 -(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
190 +(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
200 200  )))
201 201  )))
202 202  
203 203  (((
204 204  (((
205 -User can add your gateway into The Things Network V3 according to the previous step
196 +Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page.
197 +
198 +[[image:image-20230728144218-7.png||_mstalt="433290" height="128" width="836"]]
206 206  )))
207 207  )))
208 208  
209 -(((
210 -(((
211 -Following picture is the successful added.
202 +[[image:image-20230728143449-2.png||_mstalt="433108"]]
212 212  
213 -
214 -)))
215 -)))
204 +Register Gateway
216 216  
217 -[[image:image-20220526135316-8.png]]
218 218  
219 -Add Gateway
207 +== 3.3  Step 2: Create the API key ==
220 220  
221 221  
210 +**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
222 222  
223 -== 3.3  Step 2: Create the API key ==
224 224  
225 225  
226 -user need to create the CUPS API key and LNS API key.
227 227  
215 +**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png||_mstalt="431132"]]
228 228  
229 -[[image:image-20220526135349-9.png]]
230 230  
231 -Create CUPS API key
218 +=== **1.) Generated by TTH** ===
232 232  
233 233  
221 +Users need to download these two key files and fill them into the gateway's TTN Basics Station configuration,
234 234  
235 -[[image:image-20220526135428-10.png]]
223 +[[image:image-20230728150521-2.png||height="664" width="1019"]]
236 236  
237 -Create LNS API key
238 238  
226 +(% style="color:red" %)**Note:**(%%) The "**Authorization: Bearer** " field should not be entered in the TTN Basics Station configuration of the gateway
239 239  
240 -(% style="color:red" %)**Note : Please copy the API key.**
228 +[[image:image-20230728151807-3.png||height="599" width="1450"]]
241 241  
230 +=== **2.) Manually create API KEY: ** ===
242 242  
243 243  
244 -== 3.4  Step 3: Update the gateway setting ==
233 +==== CUPS API KEY ====
245 245  
235 +[[image:image-20220526135349-9.png||_mstalt="434460"]]
246 246  
237 +
238 +
239 +==== LNS API KEY ====
240 +
241 +[[image:image-20220526135428-10.png||_mstalt="453791"]]
242 +
243 +
244 +(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.**
245 +
246 +
247 +==== Update the gateway setting ====
248 +
249 +
247 247  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
248 248  
249 249  
250 -[[image:image-20220526135528-11.png]]
253 +[[image:image-20220526135528-11.png||_mstalt="454480"]]
251 251  
252 252  paste the API key
253 253  
254 254  
255 -
256 256  == 3.5  Step 4: Access the gateway GUI ==
257 257  
258 258  
... ... @@ -259,12 +259,11 @@
259 259  User need to update the API key and install the Certificate
260 260  
261 261  
262 -[[image:image-20220526135601-12.png]]
264 +[[image:image-20220526135601-12.png||_mstalt="452153"]]
263 263  
264 264  Access the gateway GUI
265 265  
266 266  
267 -
268 268  == 3.6  Step 5: Configure Station ==
269 269  
270 270  
... ... @@ -275,18 +275,17 @@
275 275  
276 276  (% class="box" %)
277 277  (((
278 - CUPS Server URI  ~-~->  Server Adress
279 + CUPS Server URI  ~-~->  Server Address, Example: https:~/~/eu1.cloud.thethings.network:443
279 279   CUPS Authorization Key         ~-~->  Server CUPS API Key
280 280   LNS Authorization Key  ~-~->  Server LNS API Key
281 281   CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
282 282  )))
283 283  
284 -[[image:image-20220526135654-13.png]]
285 +[[image:image-20220526135654-13.png||_mstalt="455169"]]
285 285  
286 286  Congfigure Station
287 287  
288 288  
289 -
290 290  == 3.7  Start Station ==
291 291  
292 292  
... ... @@ -293,7 +293,6 @@
293 293  (((
294 294  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
295 295  
296 -
297 297  
298 298  )))
299 299  
... ... @@ -303,12 +303,11 @@
303 303  If user completes the above steps,which will see live date in the TTN.
304 304  
305 305  
306 -[[image:image-20220526135734-14.png]]
305 +[[image:image-20220526135734-14.png||_mstalt="455208"]]
307 307  
308 308  Station live date
309 309  
310 310  
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]]
316 +[[image:image-20220526135845-15.png||_mstalt="456560"]]
319 319  
320 320  Station Log
321 321  
... ... @@ -323,12 +323,11 @@
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]]
324 +[[image:image-20220526135940-16.png||_mstalt="455559"]]
327 327  
328 328  Recore Log
329 329  
330 330  
331 -
332 332  = 4.  Configure node connection to TTNv3 =
333 333  
334 334  
... ... @@ -348,7 +348,6 @@
348 348  (((
349 349  (% style="color:#037691" %)**We take LES01 as an example.**
350 350  
351 -
352 352  
353 353  )))
354 354  )))
... ... @@ -374,22 +374,21 @@
374 374  )))
375 375  )))
376 376  
377 -[[image:image-20230221135445-1.png||height="356" width="777"]]
373 +[[image:image-20230221135445-1.png||_mstalt="428714" height="356" width="777"]]
378 378  
379 379  First create an application and fill in the custom information in it
380 380  
381 -[[image:image-20230221135520-2.png||height="52" width="974"]]
377 +[[image:image-20230221135520-2.png||_mstalt="427050" height="52" width="974"]]
382 382  
383 -[[image:image-20230221135810-3.png||height="400" width="638"]]
379 +[[image:image-20230221135810-3.png||_mstalt="428025" height="400" width="638"]]
384 384  
385 385  
386 386  Add a node device to the application
387 387  
388 388  
389 -[[image:image-20220526140044-18.png]]
385 +[[image:image-20220526140044-18.png||_mstalt="453648"]]
390 390  
391 391  
392 -
393 393  == 4.2  Step 2 ==
394 394  
395 395  
... ... @@ -397,14 +397,11 @@
397 397  (((
398 398  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.
399 399  
400 -
395 +[[image:image-20230221164809-2.png||_mstalt="430937" height="525" width="617"]]
401 401  )))
402 402  )))
403 403  
404 -[[image:image-20220526140132-19.png]]
405 405  
406 -
407 -
408 408  == 4.3  Step 3 ==
409 409  
410 410  
... ... @@ -411,10 +411,9 @@
411 411  Add APP EUI in the application:
412 412  
413 413  
414 -[[image:image-20230221140131-4.png||height="569" width="674"]]
406 +[[image:image-20230221140131-4.png||_mstalt="425984" height="569" width="674"]]
415 415  
416 416  
417 -
418 418  == 4.4  Step 4 ==
419 419  
420 420  
... ... @@ -421,13 +421,11 @@
421 421  **Add APP KEY and DEV EUI:**
422 422  
423 423  
424 -[[image:image-20230221140448-6.png||height="535" width="647"]]
415 +[[image:image-20230221140448-6.png||_mstalt="430339" height="535" width="647"]]
425 425  
426 426  
427 -
428 428  = 5.  TTN V3 integrated into MQTT server =
429 429  
430 -
431 431  == 5.1  Introduction ==
432 432  
433 433  
... ... @@ -435,7 +435,6 @@
435 435  (((
436 436  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.
437 437  
438 -
439 439  
440 440  )))
441 441  )))
... ... @@ -463,13 +463,13 @@
463 463  )))
464 464  )))
465 465  
466 -[[image:image-20220526140347-22.png]]
454 +[[image:image-20220526140347-22.png||_mstalt="453700"]]
467 467  
468 468  Fill in the username and password into MQTT.
469 469  
470 470  
471 471  
472 -[[image:image-20220526140420-23.png]]
460 +[[image:image-20220526140420-23.png||_mstalt="451373"]]
473 473  
474 474  
475 475  The Application Server publishes uplink traffic on the following topics:
... ... @@ -497,7 +497,7 @@
497 497  )))
498 498  )))
499 499  
500 -[[image:image-20220526140452-24.png]]
488 +[[image:image-20220526140452-24.png||_mstalt="453401"]]
501 501  
502 502  
503 503  (((
... ... @@ -506,7 +506,7 @@
506 506  )))
507 507  )))
508 508  
509 -[[image:image-20220526140708-25.png]]
497 +[[image:image-20220526140708-25.png||_mstalt="455117"]]
510 510  
511 511  (((
512 512  (((
... ... @@ -530,7 +530,7 @@
530 530  )))
531 531  )))
532 532  
533 -[[image:image-20220526140856-26.png]]
521 +[[image:image-20220526140856-26.png||_mstalt="456755"]]
534 534  
535 535  (((
536 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:
... ... @@ -544,10 +544,9 @@
544 544  
545 545  )))
546 546  
547 -[[image:image-20220526140936-27.png]]
535 +[[image:image-20220526140936-27.png||_mstalt="456794"]]
548 548  
549 549  
550 -
551 551  == 5.3  Send Downlink message ==
552 552  
553 553  
... ... @@ -565,7 +565,7 @@
565 565  
566 566  )))
567 567  
568 -[[image:image-20220526141021-28.png]]
555 +[[image:image-20220526141021-28.png||_mstalt="452647"]]
569 569  
570 570  downlink
571 571  
... ... @@ -573,7 +573,7 @@
573 573  
574 574  After sending, you can view it in live data.
575 575  
576 -[[image:image-20220526141052-29.png]]
563 +[[image:image-20220526141052-29.png||_mstalt="454337"]]
577 577  
578 578  downlink
579 579  
... ... @@ -589,7 +589,7 @@
589 589  
590 590  )))
591 591  
592 -[[image:image-20220526141116-30.png]]
579 +[[image:image-20220526141116-30.png||_mstalt="451672"]]
593 593  
594 594  downlink
595 595  
... ... @@ -620,19 +620,17 @@
620 620  )))
621 621  )))
622 622  
623 -[[image:image-20220526141149-31.png]]
610 +[[image:image-20220526141149-31.png||_mstalt="454038"]]
624 624  
625 625  downlink
626 626  
627 627  
628 -
629 629  = 6.  Route TTN data to Node-Red =
630 630  
631 631  
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 +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"]]"
633 633  
634 634  
635 -
636 636  == 6.1  Edit mqtt-broker node ==
637 637  
638 638  
... ... @@ -645,24 +645,22 @@
645 645  **Port  :** 1883
646 646  )))
647 647  
648 -[[image:image-20220829160224-187.jpeg||height="569" width="1128"]]
633 +[[image:image-20220829160224-187.jpeg||_mstalt="526292" height="569" width="1128"]]
649 649  
650 650  
651 651  **Enter Username and Password**
652 652  
653 -[[image:image-20220829164358-188.png||height="570" width="1130"]]
638 +[[image:image-20220829164358-188.png||_mstalt="486174" height="570" width="1130"]]
654 654  
655 655  
656 -
657 657  == 6.2  Debug ==
658 658  
659 659  
660 660  Users can check logs by adding debug.
661 661  
662 -[[image:image-20220829164652-189.png||height="572" width="1134"]]
646 +[[image:image-20220829164652-189.png||_mstalt="485472" height="572" width="1134"]]
663 663  
664 664  
665 -
666 666  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
667 667  
668 668  
... ... @@ -674,7 +674,6 @@
674 674  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
675 675  
676 676  
677 -
678 678  === 6.3.1  Link Node-Red to Local TTN ===
679 679  
680 680  
... ... @@ -693,7 +693,7 @@
693 693  
694 694  **v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
695 695  
696 -[[image:image-20221018100743-1.png]]
678 +[[image:image-20221018100743-1.png||_mstalt="427739"]]
697 697  
698 698  
699 699  
... ... @@ -700,11 +700,11 @@
700 700  (% style="color:blue" %)**2. Enter the MQTT configuration information**
701 701  
702 702  
703 -[[image:image-20221018100947-2.png]]
685 +[[image:image-20221018100947-2.png||_mstalt="430079"]]
704 704  
705 705  
706 706  
707 -[[image:image-20221018101102-3.png]]
689 +[[image:image-20221018101102-3.png||_mstalt="425256"]]
708 708  
709 709  (% class="wikigeneratedid" %)
710 710  (% style="color:blue" %)**Finally, click "Update" and Deploy**
... ... @@ -714,27 +714,23 @@
714 714  "Connected" indicates that the Link Node-red to Local TTN is normal.
715 715  
716 716  (% class="wikigeneratedid" %)
717 -[[image:image-20220914140918-5.png||height="602" width="1121"]]
699 +[[image:image-20220914140918-5.png||_mstalt="432523" height="602" width="1121"]]
718 718  
719 719  
720 -
721 721  === 6.3.2 Check result. ===
722 722  
723 723  
724 724  Users can check logs by adding debug.
725 725  
726 -[[image:image-20220914140841-4.png||height="600" width="1119"]]
707 +[[image:image-20220914140841-4.png||_mstalt="430456" height="600" width="1119"]]
727 727  
728 728  
729 -
730 730  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.
731 731  
732 732  
713 +[[image:image-20220914142021-7.png||_mstalt="429000" height="517" width="1346"]]
733 733  
734 -[[image:image-20220914142021-7.png||height="517" width="1346"]]
735 735  
736 -
737 -
738 738  = 7.  Request Remote Support =
739 739  
740 740  
... ... @@ -744,17 +744,22 @@
744 744  )))
745 745  
746 746  * End node is connected to serial port to show the Join frequency and DR. (If possible)
725 +
747 747  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
727 +
748 748  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
729 +
749 749  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
731 +
750 750  * 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)
751 751  
752 752  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
753 753  
754 754  * If the device is sending join request to server?
737 +
755 755  * What frequency the device is sending?
756 756  
757 -[[image:image-20220526141308-33.png]]
740 +[[image:image-20220526141308-33.png||_mstalt="453778"]]
758 758  
759 759  Console Output from End device to see the transmit frequency
760 760  
... ... @@ -763,7 +763,7 @@
763 763  
764 764  * 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)
765 765  
766 -[[image:image-20220526141612-36.png]]
749 +[[image:image-20220526141612-36.png||_mstalt="454142"]]
767 767  
768 768  
769 769  Console Output from End device to see the transmit frequency
... ... @@ -782,7 +782,7 @@
782 782  
783 783  )))
784 784  
785 -[[image:image-20220526141739-37.png]]
768 +[[image:image-20220526141739-37.png||_mstalt="457847"]]
786 786  
787 787  Console Output from Gateway to see packets between end node and server.
788 788  
... ... @@ -803,13 +803,13 @@
803 803  
804 804  )))
805 805  
806 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
789 +[[image:image-20220526141823-38.png||_mstalt="456183" height="501" width="1144"]]
807 807  
808 808  The Traffic for the End node in the server, use TTNv3 as example
809 809  
810 810  
811 811  
812 -[[image:image-20220526141917-39.png]]
795 +[[image:image-20220526141917-39.png||_mstalt="457899"]]
813 813  
814 814  The Traffic for the End node in the server, use TTNv3 as example
815 815  
... ... @@ -823,7 +823,7 @@
823 823  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.
824 824  
825 825  
826 -[[image:image-20220526141956-40.png]]
809 +[[image:image-20220526141956-40.png||_mstalt="455832"]]
827 827  )))
828 828  )))
829 829  )))
... ... @@ -832,6 +832,151 @@
832 832  
833 833  
834 834  
835 -[[image:image-20220526142033-41.png]]
818 +[[image:image-20220526142033-41.png||_mstalt="452036"]]
836 836  
837 837  Check if OTAA Keys match the keys in device
821 +
822 +
823 += 8.  FAQ =
824 +
825 +== 8.1 How to import devices keys to server. ==
826 +
827 +
828 +**For TTS in LPS8v2**
829 +
830 +Open your application and click the button **Import end devices**
831 +
832 +[[image:image-20230423154012-1.png||_mstalt="426738" height="472" width="755"]]
833 +
834 +
835 +Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv
836 +
837 +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.
838 +
839 +You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated.
840 +
841 +Start the import by clicking the **Import end devices** button.
842 +
843 +[[image:image-20230423154040-2.png||_mstalt="427401" height="470" width="749"]]
844 +
845 +
846 +Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console.
847 +
848 +[[image:image-20230423154105-3.png||_mstalt="428467" height="478" width="763"]]
849 +
850 +
851 +If the import was successful, your devices are added to the list of end devices in your application.
852 +
853 +[[image:image-20230423154125-4.png||_mstalt="429481" height="480" width="766"]]
854 +
855 +Devices are now registered on The Things Stack.
856 +
857 +
858 +=== **JSON File Reference** ===
859 +
860 +
861 +The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices.
862 +
863 +Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions.
864 +
865 +Here is an example of an OTAA device description in the file:devices.json
866 +
867 +{{{{
868 + "ids": {
869 + "device_id": "my-device",
870 + "dev_eui": "0102030405060708",
871 + "join_eui": "0102030405060708"
872 + },
873 + "name": "My Device",
874 + "description": "Living room temperature sensor",
875 + "lorawan_version": "MAC_V1_0_2",
876 + "lorawan_phy_version": "PHY_V1_0_2_REV_B",
877 + "frequency_plan_id": "EU_863_870_TTN",
878 + "supports_join": true,
879 + "root_keys": {
880 + "app_key": {
881 + "key": "01020304050607080102030405060708"
882 + }
883 + }
884 +}
885 +}}}
886 +
887 +Multiple end devices can also be contained in a single file like so:devices.json
888 +
889 +{{{{
890 + /* device 1 */
891 +}
892 +{
893 + /* device 2 */
894 +}
895 +}}}
896 +
897 +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
898 +
899 +
900 +=== **CSV File Reference** ===
901 +
902 +
903 +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.
904 +
905 +The CSV import in The Things Stack uses the following settings:
906 +
907 +* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient;
908 +
909 +* Header row is required
910 +
911 +* On each row, the same number of fields as on the header line
912 +
913 +* Use quotes to use in a field value;
914 +
915 +* Use double quotes to escape quotes
916 +
917 +* Unknown header columns are permitted and ignored
918 +
919 +* Name and id cannot have capital letters and special characters
920 +
921 +* Example column lorawan_phy_version is not needed
922 +
923 +(% style="display:none" %)
924 +
925 +
926 +
927 +=== **Example** ===
928 +
929 +
930 +Minimal example:
931 +
932 +{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key
933 +1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111
934 +2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222
935 +3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333
936 +}}}
937 +
938 +All columns for a LoRaWAN 1.0.4 device:
939 +
940 +{{{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
941 +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
942 +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
943 +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
944 +}}}
945 +
946 +
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 += 9. Trouble Shooting. =
955 +
956 +== 9.1 How to solve the problem of MIC Mismatch？ ==
957 +
958 +
959 +Please refer to the link below:
960 +
961 +[[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]]
962 +
963 +
964 +
965 +
image-20230423154012-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +140.9 KB
Content
image-20230423154040-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.0 KB
Content
image-20230423154105-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +188.5 KB
Content
image-20230423154125-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +102.1 KB
Content
image-20230728143343-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
image-20230728143449-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
image-20230728143505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +16.7 KB
Content
image-20230728144218-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20230728145557-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +53.6 KB
Content
image-20230728150521-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.9 KB
Content
image-20230728151807-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +149.0 KB
Content
image-20231019113039-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content