Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 173.2
edited by Xiaoling
on 2022/09/14 09:39
Change comment: There is no comment for this version
To version 177.1
edited by Kilight Cao
on 2022/09/14 10:33
Change comment: Uploaded new attachment "image-20220914103303-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -353,7 +353,7 @@
353 353  )))
354 354  )))
355 355  
356 -== 4.1  Step1 ==
356 +== 4.1  Step 1 ==
357 357  
358 358  
359 359  (((
... ... @@ -381,7 +381,7 @@
381 381  
382 382  
383 383  
384 -== 4.2  Step2 ==
384 +== 4.2  Step 2 ==
385 385  
386 386  
387 387  (((
... ... @@ -396,7 +396,7 @@
396 396  
397 397  
398 398  
399 -== 4.3  Step3 ==
399 +== 4.3  Step 3 ==
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  Step4 ==
409 +== 4.4  Step 4 ==
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 ==
625 +== 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,17 +642,19 @@
642 642  [[image:image-20220829164358-188.png||height="570" width="1130"]]
643 643  
644 644  
645 -== 6.2 Debug ==
646 646  
646 +== 6.2  Debug ==
647 647  
648 +
648 648  Users can check logs by adding debug.
649 649  
650 650  [[image:image-20220829164652-189.png||height="572" width="1134"]]
651 651  
652 652  
653 -== 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 ==
655 655  
657 +
656 656  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:
657 657  
658 658  * LHT65N register on LPS8v2 Built-In TTN server already
... ... @@ -661,25 +661,36 @@
661 661  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
662 662  
663 663  
664 -=== 6.3.1 Link Node-Red to Local TTN ===
665 665  
667 +=== 6.3.1  Link Node-Red to Local TTN ===
666 666  
667 -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]]
668 668  
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]]**
669 669  
670 -[[image:image-20220913134247-1.png||height="445" width="425"]]
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);"]]**
671 671  
672 -[[image:image-20220913153442-2.png||height="555" width="926"]]
673 673  
675 +After importing the Input Flow is complete, the user needs to edit the MQTT in the node,
674 674  
675 675  
676 -6.3.2 Add input flow for device.
678 +**~1. Change the Topic**
677 677  
678 -6.3.3 Check result.
679 679  
681 +Topic modifies it to the following format:
680 680  
683 +**v3/(% style="color:red" %)Application ID(%%)@ttn/devices/(% style="color:red" %)End device ID(%%)/up**
681 681  
685 +[[image:image-20220914101543-1.png||height="632" width="1134"]]
682 682  
687 +
688 +2.
689 +
690 +
691 +=== 6.3.3 Check result. ===
692 +
693 +
694 +
695 +
683 683  = 7.  Request Remote Support =
684 684  
685 685  
... ... @@ -694,6 +694,8 @@
694 694  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
695 695  * 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)
696 696  
710 +
711 +
697 697  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
698 698  
699 699  * If the device is sending join request to server?
... ... @@ -780,3 +780,5 @@
780 780  [[image:image-20220526142033-41.png]]
781 781  
782 782  Check if OTAA Keys match the keys in device
798 +
799 +
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