Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 172.1
edited by Kilight Cao
on 2022/09/13 15:34
Change comment: Uploaded new attachment "image-20220913153442-2.png", version {1}
To version 178.1
edited by Kilight Cao
on 2022/09/14 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -69,9 +69,9 @@
69 69  
70 70  
71 71  
72 -Note:
72 +(% style="color:red" %)**Note:**
73 73  
74 -DRAGINO - Frequency Plan list  ~-~-~-~--  The Thing Network Frequency Plan List
74 +DRAGINO - Frequency Plan list  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  The Thing Network Frequency Plan List
75 75  
76 76  AS923-1 (920-923)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
77 77  
... ... @@ -83,6 +83,7 @@
83 83  
84 84  AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
85 85  
86 +
86 86  [[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"]]
87 87  
88 88  
... ... @@ -352,7 +352,7 @@
352 352  )))
353 353  )))
354 354  
355 -== 4.1  Step1 ==
356 +== 4.1  Step 1 ==
356 356  
357 357  
358 358  (((
... ... @@ -380,7 +380,7 @@
380 380  
381 381  
382 382  
383 -== 4.2  Step2 ==
384 +== 4.2  Step 2 ==
384 384  
385 385  
386 386  (((
... ... @@ -395,7 +395,7 @@
395 395  
396 396  
397 397  
398 -== 4.3  Step3 ==
399 +== 4.3  Step 3 ==
399 399  
400 400  
401 401  Add APP EUI in the application:
... ... @@ -405,7 +405,7 @@
405 405  
406 406  
407 407  
408 -== 4.4  Step4 ==
409 +== 4.4  Step 4 ==
409 409  
410 410  
411 411  **Add APP KEY and DEV EUI:**
... ... @@ -621,7 +621,7 @@
621 621  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]]"
622 622  
623 623  
624 -== 6.1 Edit mqtt-broker node ==
625 +== 6.1  Edit mqtt-broker node ==
625 625  
626 626  
627 627  Users need to configure the TTN MQTT server address and port, Such as:
... ... @@ -641,33 +641,61 @@
641 641  [[image:image-20220829164358-188.png||height="570" width="1130"]]
642 642  
643 643  
644 -== 6.2 Debug ==
645 645  
646 +== 6.2  Debug ==
646 646  
648 +
647 647  Users can check logs by adding debug.
648 648  
649 649  [[image:image-20220829164652-189.png||height="572" width="1134"]]
650 650  
651 651  
652 -== 6.3 Example: Use Local Server TTN and Node-Red in LPS8v2 ==
653 653  
654 -LPS8v2 includes a local TTN Server and Node-Red. This example shows how to configure LHT65N to use with local Node-Red server. This example assumes user already have:
655 +== 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
655 655  
657 +
658 +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:
659 +
656 656  * LHT65N register on LPS8v2 Built-In TTN server already
657 657  * The user is able to see the data on the built-in TTN server device page.
658 658  
659 -Below are the steps to plot the sensor data on LPS8v2 Node Red.
663 +Below are the steps to plot the sensor data on LPS8v2 Node-Red.
660 660  
661 661  
662 -6.3.1 Link Node-Red to Local TTN
663 663  
664 -6.3.2 Add input flow for device.
667 +=== 6.3.1  Link Node-Red to Local TTN ===
665 665  
666 -6.3.3 Check result.
667 667  
670 +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]]**
668 668  
672 +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);"]]**
669 669  
670 670  
675 +After importing the Input Flow is complete, the user needs to edit the MQTT in the node
676 +
677 +
678 +**~1. Change the Topic**
679 +
680 +
681 +Topic modifies it to the following format:
682 +
683 +**v3/(% style="color:red" %)Application ID(%%)@ttn/devices/(% style="color:red" %)End device ID(%%)/up**
684 +
685 +[[image:image-20220914101543-1.png||height="632" width="1134"]]
686 +
687 +
688 +2.
689 +
690 +[[image:image-20220914103142-2.png]]
691 +
692 +
693 +[[image:image-20220914103303-3.png]]
694 +
695 +=== 6.3.3 Check result. ===
696 +
697 +
698 +
699 +
671 671  = 7.  Request Remote Support =
672 672  
673 673  
... ... @@ -682,6 +682,7 @@
682 682  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
683 683  * 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)
684 684  
714 +
685 685  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
686 686  
687 687  * If the device is sending join request to server?
... ... @@ -768,3 +768,4 @@
768 768  [[image:image-20220526142033-41.png]]
769 769  
770 770  Check if OTAA Keys match the keys in device
801 +
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