Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 99.13
edited by Xiaoling
on 2022/07/25 08:54
Change comment: There is no comment for this version
To version 199.1
edited by Xiaoye
on 2023/03/09 13:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Xiaoye
Content
... ... @@ -48,6 +48,8 @@
48 48  = 2.  Gateway Registration for Semtech UDP =
49 49  
50 50  
51 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
52 +
51 51  == 2.1  Primary LoRaWAN Server ==
52 52  
53 53  
... ... @@ -69,6 +69,25 @@
69 69  
70 70  
71 71  
74 +(% style="color:red" %)**Note:**
75 +
76 +DRAGINO - Frequency Plan list  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  The Thing Network Frequency Plan List
77 +
78 +AS923-1 (920-923)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
79 +
80 +AS923-1 (923-925)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-928 Mhz (AS923 Group 1)with only default channels
81 +
82 +AS923-2 (921.4-922.8)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz (AS923 Group 2)with only default channels
83 +
84 +AS923-3 (916.6-918.2)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-921 Mhz (AS923 Group 3)with only default channels
85 +
86 +AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
87 +
88 +
89 +[[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"]]
90 +
91 +
92 +
72 72  [[image:image-20220526134919-5.png]]
73 73  
74 74  Show Status
... ... @@ -84,15 +84,16 @@
84 84  The Dragino gateway has supports the Secondary server settings.
85 85  
86 86  
108 +
87 87  === 2.2.2  Below list the support products and Requirements: ===
88 88  
89 89  
90 90  (((
91 -~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
113 +1.  LoRaWAN Gateway model:  [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
92 92  )))
93 93  
94 94  (((
95 -2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
117 +2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
96 96  )))
97 97  
98 98  
... ... @@ -107,8 +107,9 @@
107 107  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 108  
109 109  
110 -The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
132 +The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
111 111  
134 +
112 112  [[image:image-20220526135049-6.png]]
113 113  
114 114  Download and Install gateway-rs
... ... @@ -118,8 +118,9 @@
118 118  === 2.2.5  Step 2: Back to Semtech UDP page ===
119 119  
120 120  
121 -Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
144 +Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
122 122  
146 +
123 123  ​​​​[[image:image-20220526135125-7.png]]
124 124  
125 125  Configuration of helium
... ... @@ -134,8 +134,10 @@
134 134  
135 135  (((
136 136  (((
137 -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/]]
161 +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/]]
138 138  
163 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
164 +
139 139  
140 140  )))
141 141  )))
... ... @@ -146,14 +146,12 @@
146 146  
147 147  (((
148 148  (((
149 -1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
175 +1. LoRaWAN Gateway model:  [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
150 150  )))
151 151  
152 152  (((
153 - 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
179 + 2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
154 154  
155 -
156 -
157 157  
158 158  )))
159 159  )))
... ... @@ -176,7 +176,7 @@
176 176  
177 177  (((
178 178  (((
179 -The example for **EU**
203 +(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
180 180  )))
181 181  )))
182 182  
... ... @@ -217,7 +217,7 @@
217 217  Create LNS API key
218 218  
219 219  
220 -(% style="color:red" %)**Note : Please copy the API key.**
244 +(% style="color:red" %)**Note: Please copy the API key.**
221 221  
222 222  
223 223  
... ... @@ -292,7 +292,7 @@
292 292  == 3.9  Trouble Shooting ==
293 293  
294 294  
295 -User can check the station log in the logread/system log page.
319 +User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
296 296  
297 297  
298 298  [[image:image-20220526135845-15.png]]
... ... @@ -301,7 +301,7 @@
301 301  
302 302  
303 303  
304 -and recode the station log in the system/Recode log page.
328 +and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
305 305  
306 306  [[image:image-20220526135940-16.png]]
307 307  
... ... @@ -326,7 +326,7 @@
326 326  
327 327  (((
328 328  (((
329 -We take LES01 as an example.
353 +(% style="color:#037691" %)**We take LES01 as an example.**
330 330  
331 331  
332 332  
... ... @@ -333,8 +333,9 @@
333 333  )))
334 334  )))
335 335  
336 -== 4.1 Step1 ==
360 +== 4.1  Step 1 ==
337 337  
362 +
338 338  (((
339 339  (((
340 340  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -353,50 +353,74 @@
353 353  )))
354 354  )))
355 355  
356 -[[image:image-20220526140015-17.png]]
381 +[[image:image-20230221135445-1.png||height="356" width="777"]]
357 357  
383 +First create an application and fill in the custom information in it
384 +
385 +[[image:image-20230221135520-2.png||height="52" width="974"]]
386 +
387 +[[image:image-20230221135810-3.png||height="400" width="638"]]
388 +
389 +
390 +Add a node device to the application
391 +
392 +
358 358  [[image:image-20220526140044-18.png]]
359 359  
360 360  
361 -== 4.2 Step2 ==
362 362  
397 +== 4.2  Step 2 ==
398 +
399 +
363 363  (((
364 364  (((
365 365  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.
403 +
404 +[[image:image-20230221164809-2.png||height="525" width="617"]]
366 366  )))
367 367  )))
368 368  
369 -[[image:image-20220526140132-19.png]]
370 370  
371 371  
372 -== 4.3 Step3 ==
373 373  
411 +== 4.3  Step 3 ==
412 +
413 +
374 374  Add APP EUI in the application:
375 375  
376 -[[image:image-20220526140205-20.png]]
377 377  
417 +[[image:image-20230221140131-4.png||height="569" width="674"]]
378 378  
379 -== 4.4 Step4 ==
380 380  
381 -Add APP KEY and DEV EUI:
382 382  
383 -[[image:image-20220526140251-21.png]]
421 +== 4.4  Step 4 ==
384 384  
385 385  
386 -= 5. TTN V3 integrated into MQTT server =
424 +**Add APP KEY and DEV EUI:**
387 387  
388 -== 5.1 Introduction ==
389 389  
427 +[[image:image-20230221140448-6.png||height="535" width="647"]]
428 +
429 +
430 +
431 += 5.  TTN V3 integrated into MQTT server =
432 +
433 +
434 +== 5.1  Introduction ==
435 +
436 +
390 390  (((
391 391  (((
392 392  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.
393 393  
441 +
394 394  
395 395  )))
396 396  )))
397 397  
398 -== 5.2 Create device steps at MQTT ==
446 +== 5.2  Create device steps at MQTT ==
399 399  
448 +
400 400  (((
401 401  (((
402 402  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -412,6 +412,8 @@
412 412  (((
413 413  (((
414 414  Fill in Broker Address and Broker port.
464 +
465 +
415 415  )))
416 416  )))
417 417  
... ... @@ -420,8 +420,10 @@
420 420  Fill in the username and password into MQTT.
421 421  
422 422  
474 +
423 423  [[image:image-20220526140420-23.png]]
424 424  
477 +
425 425  The Application Server publishes uplink traffic on the following topics:
426 426  
427 427  (% class="box" %)
... ... @@ -438,13 +438,18 @@
438 438  )))
439 439  
440 440  (((
494 +
495 +
441 441  (((
442 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
497 +(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
498 +
499 +
443 443  )))
444 444  )))
445 445  
446 446  [[image:image-20220526140452-24.png]]
447 447  
505 +
448 448  (((
449 449  (((
450 450  While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
... ... @@ -461,7 +461,11 @@
461 461  
462 462  (((
463 463  (((
464 -**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
522 +
523 +
524 +(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
525 +
526 +
465 465  )))
466 466  )))
467 467  
... ... @@ -475,17 +475,23 @@
475 475  
476 476  (((
477 477  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:
540 +
541 +
478 478  )))
479 479  
480 480  (((
481 -**Note**: Use this handy tool to convert hexadecimal to base64.
545 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
546 +
547 +
482 482  )))
483 483  
484 484  [[image:image-20220526140936-27.png]]
485 485  
486 486  
487 -== 5.3 Send Downlink message ==
488 488  
554 +== 5.3  Send Downlink message ==
555 +
556 +
489 489  (((
490 490  How to configure downlink in TTN V3?
491 491  )))
... ... @@ -495,7 +495,9 @@
495 495  )))
496 496  
497 497  (((
498 -Downlink command:01 00 00 5A
566 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
567 +
568 +
499 499  )))
500 500  
501 501  [[image:image-20220526141021-28.png]]
... ... @@ -503,6 +503,7 @@
503 503  downlink
504 504  
505 505  
576 +
506 506  After sending, you can view it in live data.
507 507  
508 508  [[image:image-20220526141052-29.png]]
... ... @@ -510,12 +510,15 @@
510 510  downlink
511 511  
512 512  
584 +
513 513  (((
514 514  When downlink is successfully sent, the downlink information can be received on the serial port.
515 515  )))
516 516  
517 517  (((
518 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
590 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
591 +
592 +
519 519  )))
520 520  
521 521  [[image:image-20220526141116-30.png]]
... ... @@ -531,13 +531,13 @@
531 531  
532 532  (((
533 533  (((
534 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
608 +If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
535 535  )))
536 536  )))
537 537  
538 538  (((
539 539  (((
540 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
614 +If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
541 541  )))
542 542  )))
543 543  
... ... @@ -544,6 +544,8 @@
544 544  (((
545 545  (((
546 546  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
621 +
622 +
547 547  )))
548 548  )))
549 549  
... ... @@ -552,9 +552,120 @@
552 552  downlink
553 553  
554 554  
555 -= 6. Request Remote Support =
556 556  
632 += 6.  Route TTN data to Node-Red =
633 +
634 +
635 +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]]"
636 +
637 +
638 +
639 +== 6.1  Edit mqtt-broker node ==
640 +
641 +
642 +Users need to configure the TTN MQTT server address and port, Such as:
643 +
644 +(% class="box infomessage" %)
557 557  (((
646 +**Server :** eu1.cloud.thethings.network
647 +
648 +**Port  :** 1883
649 +)))
650 +
651 +[[image:image-20220829160224-187.jpeg||height="569" width="1128"]]
652 +
653 +
654 +**Enter Username and Password**
655 +
656 +[[image:image-20220829164358-188.png||height="570" width="1130"]]
657 +
658 +
659 +
660 +== 6.2  Debug ==
661 +
662 +
663 +Users can check logs by adding debug.
664 +
665 +[[image:image-20220829164652-189.png||height="572" width="1134"]]
666 +
667 +
668 +
669 +== 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
670 +
671 +
672 +LPS8v2 includes a local TTN Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
673 +
674 +* LHT65N register on LPS8v2 Built-In TTN server already
675 +* The user is able to see the data on the built-in TTN server device page.
676 +
677 +Below are the steps to plot the sensor data on LPS8v2 Node-Red.
678 +
679 +
680 +
681 +=== 6.3.1  Link Node-Red to Local TTN ===
682 +
683 +
684 +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]]**
685 +
686 +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);"]]**
687 +
688 +
689 +After importing the Input Flow is complete, the user needs to edit the MQTT in the node
690 +
691 +
692 +(% style="color:blue" %)**1. Change the Topic**
693 +
694 +
695 +Topic modifies it to the following format:
696 +
697 +**v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
698 +
699 +[[image:image-20221018100743-1.png]]
700 +
701 +
702 +
703 +(% style="color:blue" %)**2. Enter the MQTT configuration information**
704 +
705 +
706 +[[image:image-20221018100947-2.png]]
707 +
708 +
709 +
710 +[[image:image-20221018101102-3.png]]
711 +
712 +(% class="wikigeneratedid" %)
713 +(% style="color:blue" %)**Finally, click "Update" and Deploy**
714 +
715 +
716 +(% class="wikigeneratedid" %)
717 +"Connected" indicates that the Link Node-red to Local TTN is normal.
718 +
719 +(% class="wikigeneratedid" %)
720 +[[image:image-20220914140918-5.png||height="602" width="1121"]]
721 +
722 +
723 +
724 +=== 6.3.2 Check result. ===
725 +
726 +
727 +Users can check logs by adding debug.
728 +
729 +[[image:image-20220914140841-4.png||height="600" width="1119"]]
730 +
731 +
732 +
733 +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.
734 +
735 +
736 +
737 +[[image:image-20220914142021-7.png||height="517" width="1346"]]
738 +
739 +
740 +
741 += 7.  Request Remote Support =
742 +
743 +
744 +(((
558 558  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
559 559  \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
560 560  )))
... ... @@ -565,7 +565,7 @@
565 565  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
566 566  * 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)
567 567  
568 -**~1. End Device Join Screen shot, we can check:**
755 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
569 569  
570 570  * If the device is sending join request to server?
571 571  * What frequency the device is sending?
... ... @@ -574,10 +574,11 @@
574 574  
575 575  Console Output from End device to see the transmit frequency
576 576  
577 -User can run **AT+CFG **command to print configuration information.
578 578  
579 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
765 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
580 580  
767 +* 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)
768 +
581 581  [[image:image-20220526141612-36.png]]
582 582  
583 583  
... ... @@ -584,13 +584,17 @@
584 584  Console Output from End device to see the transmit frequency
585 585  
586 586  
587 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
588 588  
776 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
777 +
589 589  * (((
590 590  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
591 591  )))
592 592  * (((
593 593  If the gateway gets the Join Accept message from server and transmit it via LoRa?
783 +
784 +
785 +
594 594  )))
595 595  
596 596  [[image:image-20220526141739-37.png]]
... ... @@ -598,8 +598,9 @@
598 598  Console Output from Gateway to see packets between end node and server.
599 599  
600 600  
601 -**3. Gateway Traffic Page in LoRaWAN Server**
602 602  
794 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
795 +
603 603  * (((
604 604  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
605 605  )))
... ... @@ -608,6 +608,9 @@
608 608  )))
609 609  * (((
610 610  If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
804 +
805 +
806 +
611 611  )))
612 612  
613 613  [[image:image-20220526141823-38.png||height="501" width="1144"]]
... ... @@ -615,18 +615,21 @@
615 615  The Traffic for the End node in the server, use TTNv3 as example
616 616  
617 617  
814 +
618 618  [[image:image-20220526141917-39.png]]
619 619  
620 620  The Traffic for the End node in the server, use TTNv3 as example
621 621  
622 622  
623 -**4. Data Page in LoRaWAN server**
624 624  
821 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
822 +
625 625  (((
626 626  (((
627 627  (((
628 628  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.
629 629  
828 +
630 630  [[image:image-20220526141956-40.png]]
631 631  )))
632 632  )))
... ... @@ -635,6 +635,7 @@
635 635  The data for the end device set in server
636 636  
637 637  
837 +
638 638  [[image:image-20220526142033-41.png]]
639 639  
640 640  Check if OTAA Keys match the keys in device
image-20220726134642-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20220726135759-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.5 KB
Content
image-20220726135827-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.1 KB
Content
image-20220829153628-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20220829153716-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +173.6 KB
Content
image-20220829155610-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +79.4 KB
Content
image-20220829160114-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160115-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160115-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-7.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-8.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-9.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160125-41.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160128-57.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160130-65.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160132-77.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160132-78.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160133-81.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160134-86.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160134-90.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-146.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-147.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-148.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-149.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-150.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-151.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-152.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-153.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-154.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-155.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-156.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-157.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-158.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-159.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-160.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-161.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-162.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-163.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-164.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-165.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-166.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-167.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-168.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-169.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-170.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-171.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-172.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-173.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-174.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-175.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-176.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-177.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-178.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-179.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-180.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-181.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-182.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-183.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-184.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-185.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-186.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160224-187.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829164358-188.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +176.0 KB
Content
image-20220829164652-189.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +148.8 KB
Content
image-20220913134247-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +23.6 KB
Content
image-20220913153442-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
image-20220914101543-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +148.7 KB
Content
image-20220914103142-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +174.7 KB
Content
image-20220914103303-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content
image-20220914140841-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +283.8 KB
Content
image-20220914140918-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +284.6 KB
Content
image-20220914141502-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +87.7 KB
Content
image-20220914142021-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +81.3 KB
Content
image-20221018100743-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +98.5 KB
Content
image-20221018100947-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +130.6 KB
Content
image-20221018101102-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +90.5 KB
Content
image-20230221135445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20230221135520-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +4.4 KB
Content
image-20230221135810-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.2 KB
Content
image-20230221140131-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230221140327-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20230221140448-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +42.9 KB
Content
image-20230221164647-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +59.6 KB
Content
image-20230221164809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +59.9 KB
Content