Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 197.1
edited by Bei Jinggeng
on 2023/02/21 16:48
Change comment: Uploaded new attachment "image-20230221164809-2.png", version {1}
To version 214.1
edited by Xiaoye
on 2023/07/28 14:34
Change comment: Uploaded new attachment "image-20230728143449-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoye
Content
... ... @@ -6,10 +6,8 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 -
10 10  == 1.1  Introduction ==
11 11  
12 -
13 13  === 1.1.1  What is The Things Network ===
14 14  
15 15  
... ... @@ -20,7 +20,6 @@
20 20  (((
21 21  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.
22 22  
23 -
24 24  
25 25  )))
26 26  
... ... @@ -34,7 +34,6 @@
34 34  (((
35 35  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 36  
37 -
38 38  
39 39  )))
40 40  
... ... @@ -44,10 +44,12 @@
44 44  LoRaWAN Gateway model: Existing Gateway
45 45  
46 46  
47 -
48 48  = 2.  Gateway Registration for Semtech UDP =
49 49  
50 50  
46 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
47 +
48 +
51 51  == 2.1  Primary LoRaWAN Server ==
52 52  
53 53  
... ... @@ -93,10 +93,8 @@
93 93  Show Status
94 94  
95 95  
96 -
97 97  == 2.2  Secondary LoRaWAN Server ==
98 98  
99 -
100 100  === 2.2.1  Introduction ===
101 101  
102 102  
... ... @@ -103,7 +103,6 @@
103 103  The Dragino gateway has supports the Secondary server settings.
104 104  
105 105  
106 -
107 107  === 2.2.2  Below list the support products and Requirements: ===
108 108  
109 109  
... ... @@ -116,7 +116,6 @@
116 116  )))
117 117  
118 118  
119 -
120 120  === 2.2.3  Example ===
121 121  
122 122  
... ... @@ -123,7 +123,6 @@
123 123  The following takes Helium as a Secondary LoRaWAN server as an example
124 124  
125 125  
126 -
127 127  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
128 128  
129 129  
... ... @@ -135,7 +135,6 @@
135 135  Download and Install gateway-rs
136 136  
137 137  
138 -
139 139  === 2.2.5  Step 2: Back to Semtech UDP page ===
140 140  
141 141  
... ... @@ -147,17 +147,17 @@
147 147  Configuration of helium
148 148  
149 149  
150 -
151 151  = 3.  Gateway Registration for Basics Station =
152 152  
153 -
154 154  == 3.1  Introduction ==
155 155  
156 156  
157 157  (((
158 158  (((
159 -The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
149 +The LoRa Basics™ Station protocol simplifies the management of large-scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
160 160  
151 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
152 +
161 161  
162 162  )))
163 163  )))
... ... @@ -186,7 +186,6 @@
186 186  (((
187 187  A gateway that can access the internet normally
188 188  
189 -
190 190  
191 191  )))
192 192  )))
... ... @@ -219,7 +219,6 @@
219 219  Add Gateway
220 220  
221 221  
222 -
223 223  == 3.3  Step 2: Create the API key ==
224 224  
225 225  
... ... @@ -237,10 +237,9 @@
237 237  Create LNS API key
238 238  
239 239  
240 -(% style="color:red" %)**Note : Please copy the API key.**
230 +(% style="color:red" %)**Note: Please copy the API key.**
241 241  
242 242  
243 -
244 244  == 3.4  Step 3: Update the gateway setting ==
245 245  
246 246  
... ... @@ -252,7 +252,6 @@
252 252  paste the API key
253 253  
254 254  
255 -
256 256  == 3.5  Step 4: Access the gateway GUI ==
257 257  
258 258  
... ... @@ -264,7 +264,6 @@
264 264  Access the gateway GUI
265 265  
266 266  
267 -
268 268  == 3.6  Step 5: Configure Station ==
269 269  
270 270  
... ... @@ -286,7 +286,6 @@
286 286  Congfigure Station
287 287  
288 288  
289 -
290 290  == 3.7  Start Station ==
291 291  
292 292  
... ... @@ -293,7 +293,6 @@
293 293  (((
294 294  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
295 295  
296 -
297 297  
298 298  )))
299 299  
... ... @@ -308,7 +308,6 @@
308 308  Station live date
309 309  
310 310  
311 -
312 312  == 3.9  Trouble Shooting ==
313 313  
314 314  
... ... @@ -328,7 +328,6 @@
328 328  Recore Log
329 329  
330 330  
331 -
332 332  = 4.  Configure node connection to TTNv3 =
333 333  
334 334  
... ... @@ -348,7 +348,6 @@
348 348  (((
349 349  (% style="color:#037691" %)**We take LES01 as an example.**
350 350  
351 -
352 352  
353 353  )))
354 354  )))
... ... @@ -389,7 +389,6 @@
389 389  [[image:image-20220526140044-18.png]]
390 390  
391 391  
392 -
393 393  == 4.2  Step 2 ==
394 394  
395 395  
... ... @@ -397,14 +397,11 @@
397 397  (((
398 398  There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
399 399  
400 -
381 +[[image:image-20230221164809-2.png||height="525" width="617"]]
401 401  )))
402 402  )))
403 403  
404 -[[image:image-20220526140132-19.png]]
405 405  
406 -
407 -
408 408  == 4.3  Step 3 ==
409 409  
410 410  
... ... @@ -414,7 +414,6 @@
414 414  [[image:image-20230221140131-4.png||height="569" width="674"]]
415 415  
416 416  
417 -
418 418  == 4.4  Step 4 ==
419 419  
420 420  
... ... @@ -424,10 +424,8 @@
424 424  [[image:image-20230221140448-6.png||height="535" width="647"]]
425 425  
426 426  
427 -
428 428  = 5.  TTN V3 integrated into MQTT server =
429 429  
430 -
431 431  == 5.1  Introduction ==
432 432  
433 433  
... ... @@ -435,7 +435,6 @@
435 435  (((
436 436  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.
437 437  
438 -
439 439  
440 440  )))
441 441  )))
... ... @@ -547,7 +547,6 @@
547 547  [[image:image-20220526140936-27.png]]
548 548  
549 549  
550 -
551 551  == 5.3  Send Downlink message ==
552 552  
553 553  
... ... @@ -625,7 +625,6 @@
625 625  downlink
626 626  
627 627  
628 -
629 629  = 6.  Route TTN data to Node-Red =
630 630  
631 631  
... ... @@ -632,7 +632,6 @@
632 632  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]]"
633 633  
634 634  
635 -
636 636  == 6.1  Edit mqtt-broker node ==
637 637  
638 638  
... ... @@ -653,7 +653,6 @@
653 653  [[image:image-20220829164358-188.png||height="570" width="1130"]]
654 654  
655 655  
656 -
657 657  == 6.2  Debug ==
658 658  
659 659  
... ... @@ -662,7 +662,6 @@
662 662  [[image:image-20220829164652-189.png||height="572" width="1134"]]
663 663  
664 664  
665 -
666 666  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
667 667  
668 668  
... ... @@ -674,7 +674,6 @@
674 674  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
675 675  
676 676  
677 -
678 678  === 6.3.1  Link Node-Red to Local TTN ===
679 679  
680 680  
... ... @@ -717,7 +717,6 @@
717 717  [[image:image-20220914140918-5.png||height="602" width="1121"]]
718 718  
719 719  
720 -
721 721  === 6.3.2 Check result. ===
722 722  
723 723  
... ... @@ -726,15 +726,12 @@
726 726  [[image:image-20220914140841-4.png||height="600" width="1119"]]
727 727  
728 728  
729 -
730 730  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.
731 731  
732 732  
733 -
734 734  [[image:image-20220914142021-7.png||height="517" width="1346"]]
735 735  
736 736  
737 -
738 738  = 7.  Request Remote Support =
739 739  
740 740  
... ... @@ -744,14 +744,19 @@
744 744  )))
745 745  
746 746  * End node is connected to serial port to show the Join frequency and DR. (If possible)
711 +
747 747  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
713 +
748 748  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
715 +
749 749  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
717 +
750 750  * 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)
751 751  
752 752  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
753 753  
754 754  * If the device is sending join request to server?
723 +
755 755  * What frequency the device is sending?
756 756  
757 757  [[image:image-20220526141308-33.png]]
... ... @@ -835,3 +835,148 @@
835 835  [[image:image-20220526142033-41.png]]
836 836  
837 837  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,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +140.9 KB
Content
image-20230423154040-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.0 KB
Content
image-20230423154105-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +188.5 KB
Content
image-20230423154125-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +102.1 KB
Content
image-20230728143343-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
image-20230728143449-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content