Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 165.1
edited by Kilight Cao
on 2022/08/29 16:06
Change comment: There is no comment for this version
To version 174.1
edited by Kilight Cao
on 2022/09/14 10:15
Change comment: Uploaded new attachment "image-20220914101543-1.png", version {1}

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:**
... ... @@ -618,10 +618,71 @@
618 618  = 6.  Route TTN data to Node-Red =
619 619  
620 620  
621 -Users can create an MQTT integration by following the steps described in "5.TTN V3 Integrated into MQTT Server"
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]]"
622 622  
623 -[[image:image-20220829160224-187.jpeg]]
624 624  
625 +== 6.1  Edit mqtt-broker node ==
626 +
627 +
628 +Users need to configure the TTN MQTT server address and port, Such as:
629 +
630 +(% class="box infomessage" %)
631 +(((
632 +**Server :** eu1.cloud.thethings.network
633 +
634 +**Port  :** 1883
635 +)))
636 +
637 +[[image:image-20220829160224-187.jpeg||height="569" width="1128"]]
638 +
639 +
640 +**Enter Username and Password**
641 +
642 +[[image:image-20220829164358-188.png||height="570" width="1130"]]
643 +
644 +
645 +
646 +== 6.2  Debug ==
647 +
648 +
649 +Users can check logs by adding debug.
650 +
651 +[[image:image-20220829164652-189.png||height="572" width="1134"]]
652 +
653 +
654 +
655 +== 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
656 +
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 +
660 +* LHT65N register on LPS8v2 Built-In TTN server already
661 +* The user is able to see the data on the built-in TTN server device page.
662 +
663 +Below are the steps to plot the sensor data on LPS8v2 Node-Red.
664 +
665 +
666 +
667 +=== 6.3.1  Link Node-Red to Local TTN ===
668 +
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 at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/LHT65N.json]]
671 +
672 +
673 +[[image:image-20220913134247-1.png||height="445" width="425"]]
674 +
675 +
676 +[[image:image-20220913153442-2.png||height="555" width="926"]]
677 +
678 +
679 +
680 +6.3.2 Add input flow for device.
681 +
682 +6.3.3 Check result.
683 +
684 +
685 +
686 +
625 625  = 7.  Request Remote Support =
626 626  
627 627  
... ... @@ -636,6 +636,9 @@
636 636  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
637 637  * 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)
638 638  
701 +
702 +
703 +
639 639  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
640 640  
641 641  * If the device is sending join request to server?
... ... @@ -722,3 +722,5 @@
722 722  [[image:image-20220526142033-41.png]]
723 723  
724 724  Check if OTAA Keys match the keys in device
790 +
791 +
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