Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 215.1
edited by Xiaoye
on 2023/07/28 14:35
Change comment: Uploaded new attachment "image-20230728143505-3.png", version {1}
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
Content
... ... @@ -6,8 +6,10 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 +
9 9  == 1.1  Introduction ==
10 10  
12 +
11 11  === 1.1.1  What is The Things Network ===
12 12  
13 13  
... ... @@ -18,6 +18,7 @@
18 18  (((
19 19  The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
20 20  
23 +
21 21  
22 22  )))
23 23  
... ... @@ -31,6 +31,7 @@
31 31  (((
32 32  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
33 33  
37 +
34 34  
35 35  )))
36 36  
... ... @@ -40,12 +40,12 @@
40 40  LoRaWAN Gateway model: Existing Gateway
41 41  
42 42  
47 +
43 43  = 2.  Gateway Registration for Semtech UDP =
44 44  
45 45  
46 46  (% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
47 47  
48 -
49 49  == 2.1  Primary LoRaWAN Server ==
50 50  
51 51  
... ... @@ -91,8 +91,10 @@
91 91  Show Status
92 92  
93 93  
98 +
94 94  == 2.2  Secondary LoRaWAN Server ==
95 95  
101 +
96 96  === 2.2.1  Introduction ===
97 97  
98 98  
... ... @@ -99,6 +99,7 @@
99 99  The Dragino gateway has supports the Secondary server settings.
100 100  
101 101  
108 +
102 102  === 2.2.2  Below list the support products and Requirements: ===
103 103  
104 104  
... ... @@ -111,6 +111,7 @@
111 111  )))
112 112  
113 113  
121 +
114 114  === 2.2.3  Example ===
115 115  
116 116  
... ... @@ -117,6 +117,7 @@
117 117  The following takes Helium as a Secondary LoRaWAN server as an example
118 118  
119 119  
128 +
120 120  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
121 121  
122 122  
... ... @@ -128,6 +128,7 @@
128 128  Download and Install gateway-rs
129 129  
130 130  
140 +
131 131  === 2.2.5  Step 2: Back to Semtech UDP page ===
132 132  
133 133  
... ... @@ -139,8 +139,10 @@
139 139  Configuration of helium
140 140  
141 141  
152 +
142 142  = 3.  Gateway Registration for Basics Station =
143 143  
155 +
144 144  == 3.1  Introduction ==
145 145  
146 146  
... ... @@ -178,6 +178,7 @@
178 178  (((
179 179  A gateway that can access the internet normally
180 180  
193 +
181 181  
182 182  )))
183 183  )))
... ... @@ -210,6 +210,7 @@
210 210  Add Gateway
211 211  
212 212  
226 +
213 213  == 3.3  Step 2: Create the API key ==
214 214  
215 215  
... ... @@ -230,6 +230,7 @@
230 230  (% style="color:red" %)**Note: Please copy the API key.**
231 231  
232 232  
247 +
233 233  == 3.4  Step 3: Update the gateway setting ==
234 234  
235 235  
... ... @@ -241,6 +241,7 @@
241 241  paste the API key
242 242  
243 243  
259 +
244 244  == 3.5  Step 4: Access the gateway GUI ==
245 245  
246 246  
... ... @@ -252,6 +252,7 @@
252 252  Access the gateway GUI
253 253  
254 254  
271 +
255 255  == 3.6  Step 5: Configure Station ==
256 256  
257 257  
... ... @@ -273,6 +273,7 @@
273 273  Congfigure Station
274 274  
275 275  
293 +
276 276  == 3.7  Start Station ==
277 277  
278 278  
... ... @@ -279,6 +279,7 @@
279 279  (((
280 280  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
281 281  
300 +
282 282  
283 283  )))
284 284  
... ... @@ -293,6 +293,7 @@
293 293  Station live date
294 294  
295 295  
315 +
296 296  == 3.9  Trouble Shooting ==
297 297  
298 298  
... ... @@ -312,6 +312,7 @@
312 312  Recore Log
313 313  
314 314  
335 +
315 315  = 4.  Configure node connection to TTNv3 =
316 316  
317 317  
... ... @@ -331,6 +331,7 @@
331 331  (((
332 332  (% style="color:#037691" %)**We take LES01 as an example.**
333 333  
355 +
334 334  
335 335  )))
336 336  )))
... ... @@ -371,6 +371,7 @@
371 371  [[image:image-20220526140044-18.png]]
372 372  
373 373  
396 +
374 374  == 4.2  Step 2 ==
375 375  
376 376  
... ... @@ -383,6 +383,8 @@
383 383  )))
384 384  
385 385  
409 +
410 +
386 386  == 4.3  Step 3 ==
387 387  
388 388  
... ... @@ -392,6 +392,7 @@
392 392  [[image:image-20230221140131-4.png||height="569" width="674"]]
393 393  
394 394  
420 +
395 395  == 4.4  Step 4 ==
396 396  
397 397  
... ... @@ -401,8 +401,10 @@
401 401  [[image:image-20230221140448-6.png||height="535" width="647"]]
402 402  
403 403  
430 +
404 404  = 5.  TTN V3 integrated into MQTT server =
405 405  
433 +
406 406  == 5.1  Introduction ==
407 407  
408 408  
... ... @@ -410,6 +410,7 @@
410 410  (((
411 411  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.
412 412  
441 +
413 413  
414 414  )))
415 415  )))
... ... @@ -521,6 +521,7 @@
521 521  [[image:image-20220526140936-27.png]]
522 522  
523 523  
553 +
524 524  == 5.3  Send Downlink message ==
525 525  
526 526  
... ... @@ -598,6 +598,7 @@
598 598  downlink
599 599  
600 600  
631 +
601 601  = 6.  Route TTN data to Node-Red =
602 602  
603 603  
... ... @@ -604,6 +604,7 @@
604 604  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]]"
605 605  
606 606  
638 +
607 607  == 6.1  Edit mqtt-broker node ==
608 608  
609 609  
... ... @@ -624,6 +624,7 @@
624 624  [[image:image-20220829164358-188.png||height="570" width="1130"]]
625 625  
626 626  
659 +
627 627  == 6.2  Debug ==
628 628  
629 629  
... ... @@ -632,6 +632,7 @@
632 632  [[image:image-20220829164652-189.png||height="572" width="1134"]]
633 633  
634 634  
668 +
635 635  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
636 636  
637 637  
... ... @@ -643,6 +643,7 @@
643 643  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
644 644  
645 645  
680 +
646 646  === 6.3.1  Link Node-Red to Local TTN ===
647 647  
648 648  
... ... @@ -685,6 +685,7 @@
685 685  [[image:image-20220914140918-5.png||height="602" width="1121"]]
686 686  
687 687  
723 +
688 688  === 6.3.2 Check result. ===
689 689  
690 690  
... ... @@ -693,12 +693,15 @@
693 693  [[image:image-20220914140841-4.png||height="600" width="1119"]]
694 694  
695 695  
732 +
696 696  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.
697 697  
698 698  
736 +
699 699  [[image:image-20220914142021-7.png||height="517" width="1346"]]
700 700  
701 701  
740 +
702 702  = 7.  Request Remote Support =
703 703  
704 704  
... ... @@ -708,19 +708,14 @@
708 708  )))
709 709  
710 710  * End node is connected to serial port to show the Join frequency and DR. (If possible)
711 -
712 712  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
713 -
714 714  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
715 -
716 716  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
717 -
718 718  * 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)
719 719  
720 720  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
721 721  
722 722  * If the device is sending join request to server?
723 -
724 724  * What frequency the device is sending?
725 725  
726 726  [[image:image-20220526141308-33.png]]
... ... @@ -804,148 +804,3 @@
804 804  [[image:image-20220526142033-41.png]]
805 805  
806 806  Check if OTAA Keys match the keys in device
807 -
808 -
809 -= 8.  FAQ =
810 -
811 -== 8.1 How to import devices keys to server. ==
812 -
813 -
814 -**For TTS in LPS8v2**
815 -
816 -Open your application and click the button **Import end devices**
817 -
818 -[[image:image-20230423154012-1.png||height="472" width="755"]]
819 -
820 -
821 -Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv
822 -
823 -You can specify **Fallback values** for Frequency plan and LoRaWAN and Regional Parameters version, in case the import file does not specify these settings for the device.
824 -
825 -You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated.
826 -
827 -Start the import by clicking the **Import end devices** button.
828 -
829 -[[image:image-20230423154040-2.png||height="470" width="749"]]
830 -
831 -
832 -Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console.
833 -
834 -[[image:image-20230423154105-3.png||height="478" width="763"]]
835 -
836 -
837 -If the import was successful, your devices are added to the list of end devices in your application.
838 -
839 -[[image:image-20230423154125-4.png||height="480" width="766"]]
840 -
841 -Devices are now registered on The Things Stack.
842 -
843 -
844 -=== **JSON File Reference** ===
845 -
846 -
847 -The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices.
848 -
849 -Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions.
850 -
851 -Here is an example of an OTAA device description in the file:devices.json
852 -
853 -{{{{
854 - "ids": {
855 - "device_id": "my-device",
856 - "dev_eui": "0102030405060708",
857 - "join_eui": "0102030405060708"
858 - },
859 - "name": "My Device",
860 - "description": "Living room temperature sensor",
861 - "lorawan_version": "MAC_V1_0_2",
862 - "lorawan_phy_version": "PHY_V1_0_2_REV_B",
863 - "frequency_plan_id": "EU_863_870_TTN",
864 - "supports_join": true,
865 - "root_keys": {
866 - "app_key": {
867 - "key": "01020304050607080102030405060708"
868 - }
869 - }
870 -}
871 -}}}
872 -
873 -Multiple end devices can also be contained in a single file like so:devices.json
874 -
875 -{{{{
876 - /* device 1 */
877 -}
878 -{
879 - /* device 2 */
880 -}
881 -}}}
882 -
883 -The format above is considered by the Console and CLI as a JSON stream, processing one object at a time. For more details in how to use the file
884 -
885 -
886 -=== **CSV File Reference** ===
887 -
888 -
889 -The Things Stack has support for importing end devices from CSV (comma-separated values) files. This is useful when batches of end devices are managed in Microsoft Excel or any other spreadsheet or database that can export to CSV file.
890 -
891 -The CSV import in The Things Stack uses the following settings:
892 -
893 -* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient;
894 -
895 -* Header row is required
896 -
897 -* On each row, the same number of fields as on the header line
898 -
899 -* Use quotes to use in a field value;
900 -
901 -* Use double quotes to escape quotes
902 -
903 -* Unknown header columns are permitted and ignored
904 -
905 -* Name and id cannot have capital letters and special characters
906 -
907 -* Example column lorawan_phy_version is not needed
908 -
909 -(% style="display:none" %)
910 -
911 -
912 -
913 -=== **Example** ===
914 -
915 -
916 -Minimal example:
917 -
918 -{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key
919 -1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111
920 -2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222
921 -3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333
922 -}}}
923 -
924 -All columns for a LoRaWAN 1.0.4 device:
925 -
926 -{{{id;dev_eui;join_eui;name;frequency_plan_id;lorawan_version;lorawan_phy_version;brand_id;model_id;hardware_version;firmware_version;band_id;app_key
927 -test-one;1111111111111111;1111111111111111;Device 1;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;11111111111111111111111111111111
928 -test-two;2222222222222222;2222222222222222;Device 2;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;22222222222222222222222222222222
929 -test-three;3333333333333333;3333333333333333;Device 3;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;33333333333333333333333333333333
930 -}}}
931 -
932 -
933 -
934 -=== **Excel Template** ===
935 -
936 -
937 -[[Download the Excel template>>url:https://www.thethingsindustries.com/docs/getting-started/migrating/tts-end-devices-csv-template.xlsx]]. You can remove all columns that are not required (see above).
938 -
939 -
940 -= 9. Trouble Shooting. =
941 -
942 -== 9.1 How to solve the problem of MIC Mismatch？ ==
943 -
944 -
945 -Please refer to the link below:
946 -
947 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F>>url:http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F]]
948 -
949 -
950 -
951 -
image-20230423154012-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -140.9 KB
Content
image-20230423154040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.0 KB
Content
image-20230423154105-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -188.5 KB
Content
image-20230423154125-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -102.1 KB
Content
image-20230728143343-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -43.2 KB
Content
image-20230728143449-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -43.2 KB
Content
image-20230728143505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -16.7 KB
Content