Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 175.1
edited by Kilight Cao
on 2022/09/14 10:29
Change comment: There is no comment for this version
To version 173.1
edited by Kilight Cao
on 2022/09/13 17:02
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 -(% style="color:red" %)**Note:**
72 +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,7 +83,6 @@
83 83  
84 84  AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
85 85  
86 -
87 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"]]
88 88  
89 89  
... ... @@ -353,7 +353,7 @@
353 353  )))
354 354  )))
355 355  
356 -== 4.1  Step 1 ==
355 +== 4.1  Step1 ==
357 357  
358 358  
359 359  (((
... ... @@ -381,7 +381,7 @@
381 381  
382 382  
383 383  
384 -== 4.2  Step 2 ==
383 +== 4.2  Step2 ==
385 385  
386 386  
387 387  (((
... ... @@ -396,7 +396,7 @@
396 396  
397 397  
398 398  
399 -== 4.3  Step 3 ==
398 +== 4.3  Step3 ==
400 400  
401 401  
402 402  Add APP EUI in the application:
... ... @@ -406,7 +406,7 @@
406 406  
407 407  
408 408  
409 -== 4.4  Step 4 ==
408 +== 4.4  Step4 ==
410 410  
411 411  
412 412  **Add APP KEY and DEV EUI:**
... ... @@ -622,7 +622,7 @@
622 622  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]]"
623 623  
624 624  
625 -== 6.1  Edit mqtt-broker node ==
624 +== 6.1 Edit mqtt-broker node ==
626 626  
627 627  
628 628  Users need to configure the TTN MQTT server address and port, Such as:
... ... @@ -642,19 +642,17 @@
642 642  [[image:image-20220829164358-188.png||height="570" width="1130"]]
643 643  
644 644  
644 +== 6.2 Debug ==
645 645  
646 -== 6.2  Debug ==
647 647  
648 -
649 649  Users can check logs by adding debug.
650 650  
651 651  [[image:image-20220829164652-189.png||height="572" width="1134"]]
652 652  
653 653  
652 +== 6.3 Example: Use Local Server TTN and Node-Red in LPS8v2 ==
654 654  
655 -== 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
656 656  
657 -
658 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 659  
660 660  * LHT65N register on LPS8v2 Built-In TTN server already
... ... @@ -663,36 +663,25 @@
663 663  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
664 664  
665 665  
663 +=== 6.3.1 Link Node-Red to Local TTN ===
666 666  
667 -=== 6.3.1  Link Node-Red to Local TTN ===
668 668  
666 +Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  [[dragino-end-node-decoder/LHT65N.json at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/LHT65N.json]]
669 669  
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]]**
671 671  
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 +[[image:image-20220913134247-1.png||height="445" width="425"]]
673 673  
671 +[[image:image-20220913153442-2.png||height="555" width="926"]]
674 674  
675 -After importing the Input Flow is complete, the user needs to edit the MQTT in the node,
676 676  
677 677  
678 -**~1. Change the Topic**
675 +6.3.2 Add input flow for device.
679 679  
677 +6.3.3 Check result.
680 680  
681 -Topic modifies it to the following format:
682 682  
683 -**v3/(% style="color:red" %)Application ID(%%)@ttn/devices/(% style="color:red" %)End device ID(%%)/up**
684 684  
685 -[[image:image-20220914101543-1.png||height="632" width="1134"]]
686 686  
687 -
688 -2.
689 -
690 -
691 -=== 6.3.3 Check result. ===
692 -
693 -
694 -
695 -
696 696  = 7.  Request Remote Support =
697 697  
698 698  
... ... @@ -707,8 +707,6 @@
707 707  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
708 708  * 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)
709 709  
710 -
711 -
712 712  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
713 713  
714 714  * If the device is sending join request to server?
... ... @@ -795,5 +795,3 @@
795 795  [[image:image-20220526142033-41.png]]
796 796  
797 797  Check if OTAA Keys match the keys in device
798 -
799 -
image-20220914101543-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -148.7 KB
Content