Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 223.1
edited by Bei Jinggeng
on 2023/10/19 11:31
Change comment: Uploaded new attachment "image-20231019113131-2.png", version {1}
To version 198.1
edited by Bei Jinggeng
on 2023/02/21 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
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="616" width="1323"]]
54 +[[image:image-20220526134633-2.png||height="616" width="1323"]]
53 53  
54 54  Register Gateway
55 55  
56 56  
57 57  
58 -[[image:image-20220526134826-4.png||_mstalt="432237"]]
60 +[[image:image-20220526134826-4.png]]
59 59  
60 60  Put Gateway ID
61 61  
62 62  
63 63  
64 -[[image:image-20220526134759-3.png||_mstalt="433550"]]
66 +[[image:image-20220526134759-3.png]]
65 65  
66 66  Choose Frequency Band
67 67  
... ... @@ -82,17 +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 87  
88 88  
89 -[[image:image-20220526134919-5.png||_mstalt="433602"]]
91 +[[image:image-20220526134919-5.png]]
90 90  
91 91  Show Status
92 92  
93 93  
96 +
94 94  == 2.2  Secondary LoRaWAN Server ==
95 95  
99 +
96 96  === 2.2.1  Introduction ===
97 97  
98 98  
... ... @@ -99,6 +99,7 @@
99 99  The Dragino gateway has supports the Secondary server settings.
100 100  
101 101  
106 +
102 102  === 2.2.2  Below list the support products and Requirements: ===
103 103  
104 104  
... ... @@ -111,6 +111,7 @@
111 111  )))
112 112  
113 113  
119 +
114 114  === 2.2.3  Example ===
115 115  
116 116  
... ... @@ -117,6 +117,7 @@
117 117  The following takes Helium as a Secondary LoRaWAN server as an example
118 118  
119 119  
126 +
120 120  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
121 121  
122 122  
... ... @@ -123,11 +123,12 @@
123 123  The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
124 124  
125 125  
126 -[[image:image-20220526135049-6.png||_mstalt="432432"]]
133 +[[image:image-20220526135049-6.png]]
127 127  
128 128  Download and Install gateway-rs
129 129  
130 130  
138 +
131 131  === 2.2.5  Step 2: Back to Semtech UDP page ===
132 132  
133 133  
... ... @@ -134,22 +134,22 @@
134 134  Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
135 135  
136 136  
137 -​​​​[[image:image-20220526135125-7.png||_mstalt="431106"]]
145 +​​​​[[image:image-20220526135125-7.png]]
138 138  
139 139  Configuration of helium
140 140  
141 141  
150 +
142 142  = 3.  Gateway Registration for Basics Station =
143 143  
153 +
144 144  == 3.1  Introduction ==
145 145  
146 146  
147 147  (((
148 148  (((
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/]]
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/]]
150 150  
151 -(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
152 -
153 153  
154 154  )))
155 155  )))
... ... @@ -171,7 +171,7 @@
171 171  )))
172 172  
173 173  (((
174 -(% style="color:blue" %)**What do you need to prepare?**
182 +(% style="color:blue" %)**What do you need to prepare**
175 175  )))
176 176  
177 177  (((
... ... @@ -178,83 +178,73 @@
178 178  (((
179 179  A gateway that can access the internet normally
180 180  
189 +
181 181  
182 182  )))
183 183  )))
184 184  
185 -== 3.2  Step 1: Register Gateway ==
194 +== 3.2  Step 1: Add Gateway ==
186 186  
187 187  
188 188  (((
189 189  (((
190 -(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
199 +(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
191 191  )))
192 192  )))
193 193  
194 194  (((
195 195  (((
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"]]
205 +User can add your gateway into The Things Network V3 according to the previous step
199 199  )))
200 200  )))
201 201  
202 -[[image:image-20230728143449-2.png||_mstalt="433108"]]
209 +(((
210 +(((
211 +Following picture is the successful added.
203 203  
204 -Register Gateway
213 +
214 +)))
215 +)))
205 205  
217 +[[image:image-20220526135316-8.png]]
206 206  
207 -== 3.3  Step 2: Create the API key ==
219 +Add Gateway
208 208  
209 209  
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
211 211  
223 +== 3.3  Step 2: Create the API key ==
212 212  
213 213  
226 +user need to create the CUPS API key and LNS API key.
214 214  
215 -**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png||_mstalt="431132"]]
216 216  
229 +[[image:image-20220526135349-9.png]]
217 217  
218 -=== **1.) Generated by TTH** ===
231 +Create CUPS API key
219 219  
220 220  
221 -Users need to download these two key files and fill them into the gateway's TTN Basics Station configuration,
222 222  
223 -[[image:image-20230728150521-2.png||height="664" width="1019"]]
235 +[[image:image-20220526135428-10.png]]
224 224  
237 +Create LNS API key
225 225  
226 -(% style="color:red" %)**Note:**(%%) The "**Authorization: Bearer** " field should not be entered in the TTN Basics Station configuration of the gateway
227 227  
228 -[[image:image-20230728151807-3.png||height="599" width="1450"]]
240 +(% style="color:red" %)**Note : Please copy the API key.**
229 229  
230 -=== **2.) Manually create API KEY: ** ===
231 231  
232 232  
233 -==== CUPS API KEY ====
244 +== 3.4  Step 3: Update the gateway setting ==
234 234  
235 -[[image:image-20220526135349-9.png||_mstalt="434460"]]
236 236  
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 -
250 250  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
251 251  
252 252  
253 -[[image:image-20220526135528-11.png||_mstalt="454480"]]
250 +[[image:image-20220526135528-11.png]]
254 254  
255 255  paste the API key
256 256  
257 257  
255 +
258 258  == 3.5  Step 4: Access the gateway GUI ==
259 259  
260 260  
... ... @@ -261,11 +261,12 @@
261 261  User need to update the API key and install the Certificate
262 262  
263 263  
264 -[[image:image-20220526135601-12.png||_mstalt="452153"]]
262 +[[image:image-20220526135601-12.png]]
265 265  
266 266  Access the gateway GUI
267 267  
268 268  
267 +
269 269  == 3.6  Step 5: Configure Station ==
270 270  
271 271  
... ... @@ -276,17 +276,18 @@
276 276  
277 277  (% class="box" %)
278 278  (((
279 - CUPS Server URI  ~-~->  Server Address, Example: https:~/~/eu1.cloud.thethings.network:443
278 + CUPS Server URI  ~-~->  Server Adress
280 280   CUPS Authorization Key         ~-~->  Server CUPS API Key
281 281   LNS Authorization Key  ~-~->  Server LNS API Key
282 282   CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
283 283  )))
284 284  
285 -[[image:image-20220526135654-13.png||_mstalt="455169"]]
284 +[[image:image-20220526135654-13.png]]
286 286  
287 287  Congfigure Station
288 288  
289 289  
289 +
290 290  == 3.7  Start Station ==
291 291  
292 292  
... ... @@ -293,6 +293,7 @@
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 +
296 296  
297 297  )))
298 298  
... ... @@ -302,11 +302,12 @@
302 302  If user completes the above steps,which will see live date in the TTN.
303 303  
304 304  
305 -[[image:image-20220526135734-14.png||_mstalt="455208"]]
306 +[[image:image-20220526135734-14.png]]
306 306  
307 307  Station live date
308 308  
309 309  
311 +
310 310  == 3.9  Trouble Shooting ==
311 311  
312 312  
... ... @@ -313,7 +313,7 @@
313 313  User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
314 314  
315 315  
316 -[[image:image-20220526135845-15.png||_mstalt="456560"]]
318 +[[image:image-20220526135845-15.png]]
317 317  
318 318  Station Log
319 319  
... ... @@ -321,11 +321,12 @@
321 321  
322 322  and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
323 323  
324 -[[image:image-20220526135940-16.png||_mstalt="455559"]]
326 +[[image:image-20220526135940-16.png]]
325 325  
326 326  Recore Log
327 327  
328 328  
331 +
329 329  = 4.  Configure node connection to TTNv3 =
330 330  
331 331  
... ... @@ -345,6 +345,7 @@
345 345  (((
346 346  (% style="color:#037691" %)**We take LES01 as an example.**
347 347  
351 +
348 348  
349 349  )))
350 350  )))
... ... @@ -370,21 +370,22 @@
370 370  )))
371 371  )))
372 372  
373 -[[image:image-20230221135445-1.png||_mstalt="428714" height="356" width="777"]]
377 +[[image:image-20230221135445-1.png||height="356" width="777"]]
374 374  
375 375  First create an application and fill in the custom information in it
376 376  
377 -[[image:image-20230221135520-2.png||_mstalt="427050" height="52" width="974"]]
381 +[[image:image-20230221135520-2.png||height="52" width="974"]]
378 378  
379 -[[image:image-20230221135810-3.png||_mstalt="428025" height="400" width="638"]]
383 +[[image:image-20230221135810-3.png||height="400" width="638"]]
380 380  
381 381  
382 382  Add a node device to the application
383 383  
384 384  
385 -[[image:image-20220526140044-18.png||_mstalt="453648"]]
389 +[[image:image-20220526140044-18.png]]
386 386  
387 387  
392 +
388 388  == 4.2  Step 2 ==
389 389  
390 390  
... ... @@ -392,11 +392,13 @@
392 392  (((
393 393  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.
394 394  
395 -[[image:image-20230221164809-2.png||_mstalt="430937" height="525" width="617"]]
400 +[[image:image-20230221164809-2.png||height="525" width="617"]]
396 396  )))
397 397  )))
398 398  
399 399  
405 +
406 +
400 400  == 4.3  Step 3 ==
401 401  
402 402  
... ... @@ -403,9 +403,10 @@
403 403  Add APP EUI in the application:
404 404  
405 405  
406 -[[image:image-20230221140131-4.png||_mstalt="425984" height="569" width="674"]]
413 +[[image:image-20230221140131-4.png||height="569" width="674"]]
407 407  
408 408  
416 +
409 409  == 4.4  Step 4 ==
410 410  
411 411  
... ... @@ -412,11 +412,13 @@
412 412  **Add APP KEY and DEV EUI:**
413 413  
414 414  
415 -[[image:image-20230221140448-6.png||_mstalt="430339" height="535" width="647"]]
423 +[[image:image-20230221140448-6.png||height="535" width="647"]]
416 416  
417 417  
426 +
418 418  = 5.  TTN V3 integrated into MQTT server =
419 419  
429 +
420 420  == 5.1  Introduction ==
421 421  
422 422  
... ... @@ -424,6 +424,7 @@
424 424  (((
425 425  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.
426 426  
437 +
427 427  
428 428  )))
429 429  )))
... ... @@ -451,13 +451,13 @@
451 451  )))
452 452  )))
453 453  
454 -[[image:image-20220526140347-22.png||_mstalt="453700"]]
465 +[[image:image-20220526140347-22.png]]
455 455  
456 456  Fill in the username and password into MQTT.
457 457  
458 458  
459 459  
460 -[[image:image-20220526140420-23.png||_mstalt="451373"]]
471 +[[image:image-20220526140420-23.png]]
461 461  
462 462  
463 463  The Application Server publishes uplink traffic on the following topics:
... ... @@ -485,7 +485,7 @@
485 485  )))
486 486  )))
487 487  
488 -[[image:image-20220526140452-24.png||_mstalt="453401"]]
499 +[[image:image-20220526140452-24.png]]
489 489  
490 490  
491 491  (((
... ... @@ -494,7 +494,7 @@
494 494  )))
495 495  )))
496 496  
497 -[[image:image-20220526140708-25.png||_mstalt="455117"]]
508 +[[image:image-20220526140708-25.png]]
498 498  
499 499  (((
500 500  (((
... ... @@ -518,7 +518,7 @@
518 518  )))
519 519  )))
520 520  
521 -[[image:image-20220526140856-26.png||_mstalt="456755"]]
532 +[[image:image-20220526140856-26.png]]
522 522  
523 523  (((
524 524  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:
... ... @@ -532,9 +532,10 @@
532 532  
533 533  )))
534 534  
535 -[[image:image-20220526140936-27.png||_mstalt="456794"]]
546 +[[image:image-20220526140936-27.png]]
536 536  
537 537  
549 +
538 538  == 5.3  Send Downlink message ==
539 539  
540 540  
... ... @@ -552,7 +552,7 @@
552 552  
553 553  )))
554 554  
555 -[[image:image-20220526141021-28.png||_mstalt="452647"]]
567 +[[image:image-20220526141021-28.png]]
556 556  
557 557  downlink
558 558  
... ... @@ -560,7 +560,7 @@
560 560  
561 561  After sending, you can view it in live data.
562 562  
563 -[[image:image-20220526141052-29.png||_mstalt="454337"]]
575 +[[image:image-20220526141052-29.png]]
564 564  
565 565  downlink
566 566  
... ... @@ -576,7 +576,7 @@
576 576  
577 577  )))
578 578  
579 -[[image:image-20220526141116-30.png||_mstalt="451672"]]
591 +[[image:image-20220526141116-30.png]]
580 580  
581 581  downlink
582 582  
... ... @@ -607,17 +607,19 @@
607 607  )))
608 608  )))
609 609  
610 -[[image:image-20220526141149-31.png||_mstalt="454038"]]
622 +[[image:image-20220526141149-31.png]]
611 611  
612 612  downlink
613 613  
614 614  
627 +
615 615  = 6.  Route TTN data to Node-Red =
616 616  
617 617  
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"]]"
631 +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]]"
619 619  
620 620  
634 +
621 621  == 6.1  Edit mqtt-broker node ==
622 622  
623 623  
... ... @@ -630,22 +630,24 @@
630 630  **Port  :** 1883
631 631  )))
632 632  
633 -[[image:image-20220829160224-187.jpeg||_mstalt="526292" height="569" width="1128"]]
647 +[[image:image-20220829160224-187.jpeg||height="569" width="1128"]]
634 634  
635 635  
636 636  **Enter Username and Password**
637 637  
638 -[[image:image-20220829164358-188.png||_mstalt="486174" height="570" width="1130"]]
652 +[[image:image-20220829164358-188.png||height="570" width="1130"]]
639 639  
640 640  
655 +
641 641  == 6.2  Debug ==
642 642  
643 643  
644 644  Users can check logs by adding debug.
645 645  
646 -[[image:image-20220829164652-189.png||_mstalt="485472" height="572" width="1134"]]
661 +[[image:image-20220829164652-189.png||height="572" width="1134"]]
647 647  
648 648  
664 +
649 649  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
650 650  
651 651  
... ... @@ -657,6 +657,7 @@
657 657  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
658 658  
659 659  
676 +
660 660  === 6.3.1  Link Node-Red to Local TTN ===
661 661  
662 662  
... ... @@ -675,7 +675,7 @@
675 675  
676 676  **v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
677 677  
678 -[[image:image-20221018100743-1.png||_mstalt="427739"]]
695 +[[image:image-20221018100743-1.png]]
679 679  
680 680  
681 681  
... ... @@ -682,11 +682,11 @@
682 682  (% style="color:blue" %)**2. Enter the MQTT configuration information**
683 683  
684 684  
685 -[[image:image-20221018100947-2.png||_mstalt="430079"]]
702 +[[image:image-20221018100947-2.png]]
686 686  
687 687  
688 688  
689 -[[image:image-20221018101102-3.png||_mstalt="425256"]]
706 +[[image:image-20221018101102-3.png]]
690 690  
691 691  (% class="wikigeneratedid" %)
692 692  (% style="color:blue" %)**Finally, click "Update" and Deploy**
... ... @@ -696,23 +696,27 @@
696 696  "Connected" indicates that the Link Node-red to Local TTN is normal.
697 697  
698 698  (% class="wikigeneratedid" %)
699 -[[image:image-20220914140918-5.png||_mstalt="432523" height="602" width="1121"]]
716 +[[image:image-20220914140918-5.png||height="602" width="1121"]]
700 700  
701 701  
719 +
702 702  === 6.3.2 Check result. ===
703 703  
704 704  
705 705  Users can check logs by adding debug.
706 706  
707 -[[image:image-20220914140841-4.png||_mstalt="430456" height="600" width="1119"]]
725 +[[image:image-20220914140841-4.png||height="600" width="1119"]]
708 708  
709 709  
728 +
710 710  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.
711 711  
712 712  
713 -[[image:image-20220914142021-7.png||_mstalt="429000" height="517" width="1346"]]
714 714  
733 +[[image:image-20220914142021-7.png||height="517" width="1346"]]
715 715  
735 +
736 +
716 716  = 7.  Request Remote Support =
717 717  
718 718  
... ... @@ -722,22 +722,17 @@
722 722  )))
723 723  
724 724  * End node is connected to serial port to show the Join frequency and DR. (If possible)
725 -
726 726  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
727 -
728 728  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
729 -
730 730  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
731 -
732 732  * 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)
733 733  
734 734  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
735 735  
736 736  * If the device is sending join request to server?
737 -
738 738  * What frequency the device is sending?
739 739  
740 -[[image:image-20220526141308-33.png||_mstalt="453778"]]
756 +[[image:image-20220526141308-33.png]]
741 741  
742 742  Console Output from End device to see the transmit frequency
743 743  
... ... @@ -746,7 +746,7 @@
746 746  
747 747  * 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)
748 748  
749 -[[image:image-20220526141612-36.png||_mstalt="454142"]]
765 +[[image:image-20220526141612-36.png]]
750 750  
751 751  
752 752  Console Output from End device to see the transmit frequency
... ... @@ -765,7 +765,7 @@
765 765  
766 766  )))
767 767  
768 -[[image:image-20220526141739-37.png||_mstalt="457847"]]
784 +[[image:image-20220526141739-37.png]]
769 769  
770 770  Console Output from Gateway to see packets between end node and server.
771 771  
... ... @@ -786,13 +786,13 @@
786 786  
787 787  )))
788 788  
789 -[[image:image-20220526141823-38.png||_mstalt="456183" height="501" width="1144"]]
805 +[[image:image-20220526141823-38.png||height="501" width="1144"]]
790 790  
791 791  The Traffic for the End node in the server, use TTNv3 as example
792 792  
793 793  
794 794  
795 -[[image:image-20220526141917-39.png||_mstalt="457899"]]
811 +[[image:image-20220526141917-39.png]]
796 796  
797 797  The Traffic for the End node in the server, use TTNv3 as example
798 798  
... ... @@ -806,7 +806,7 @@
806 806  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.
807 807  
808 808  
809 -[[image:image-20220526141956-40.png||_mstalt="455832"]]
825 +[[image:image-20220526141956-40.png]]
810 810  )))
811 811  )))
812 812  )))
... ... @@ -815,151 +815,6 @@
815 815  
816 816  
817 817  
818 -[[image:image-20220526142033-41.png||_mstalt="452036"]]
834 +[[image:image-20220526142033-41.png]]
819 819  
820 820  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,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