Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 199.1
edited by Xiaoye
on 2023/03/09 13:44
Change comment: There is no comment for this version
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
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,12 +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  
51 51  (% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
52 52  
48 +
53 53  == 2.1  Primary LoRaWAN Server ==
54 54  
55 55  
... ... @@ -95,10 +95,8 @@
95 95  Show Status
96 96  
97 97  
98 -
99 99  == 2.2  Secondary LoRaWAN Server ==
100 100  
101 -
102 102  === 2.2.1  Introduction ===
103 103  
104 104  
... ... @@ -105,7 +105,6 @@
105 105  The Dragino gateway has supports the Secondary server settings.
106 106  
107 107  
108 -
109 109  === 2.2.2  Below list the support products and Requirements: ===
110 110  
111 111  
... ... @@ -118,7 +118,6 @@
118 118  )))
119 119  
120 120  
121 -
122 122  === 2.2.3  Example ===
123 123  
124 124  
... ... @@ -125,7 +125,6 @@
125 125  The following takes Helium as a Secondary LoRaWAN server as an example
126 126  
127 127  
128 -
129 129  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
130 130  
131 131  
... ... @@ -137,7 +137,6 @@
137 137  Download and Install gateway-rs
138 138  
139 139  
140 -
141 141  === 2.2.5  Step 2: Back to Semtech UDP page ===
142 142  
143 143  
... ... @@ -149,10 +149,8 @@
149 149  Configuration of helium
150 150  
151 151  
152 -
153 153  = 3.  Gateway Registration for Basics Station =
154 154  
155 -
156 156  == 3.1  Introduction ==
157 157  
158 158  
... ... @@ -190,7 +190,6 @@
190 190  (((
191 191  A gateway that can access the internet normally
192 192  
193 -
194 194  
195 195  )))
196 196  )))
... ... @@ -223,7 +223,6 @@
223 223  Add Gateway
224 224  
225 225  
226 -
227 227  == 3.3  Step 2: Create the API key ==
228 228  
229 229  
... ... @@ -244,7 +244,6 @@
244 244  (% style="color:red" %)**Note: Please copy the API key.**
245 245  
246 246  
247 -
248 248  == 3.4  Step 3: Update the gateway setting ==
249 249  
250 250  
... ... @@ -256,7 +256,6 @@
256 256  paste the API key
257 257  
258 258  
259 -
260 260  == 3.5  Step 4: Access the gateway GUI ==
261 261  
262 262  
... ... @@ -268,7 +268,6 @@
268 268  Access the gateway GUI
269 269  
270 270  
271 -
272 272  == 3.6  Step 5: Configure Station ==
273 273  
274 274  
... ... @@ -290,7 +290,6 @@
290 290  Congfigure Station
291 291  
292 292  
293 -
294 294  == 3.7  Start Station ==
295 295  
296 296  
... ... @@ -297,7 +297,6 @@
297 297  (((
298 298  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
299 299  
300 -
301 301  
302 302  )))
303 303  
... ... @@ -312,7 +312,6 @@
312 312  Station live date
313 313  
314 314  
315 -
316 316  == 3.9  Trouble Shooting ==
317 317  
318 318  
... ... @@ -332,7 +332,6 @@
332 332  Recore Log
333 333  
334 334  
335 -
336 336  = 4.  Configure node connection to TTNv3 =
337 337  
338 338  
... ... @@ -352,7 +352,6 @@
352 352  (((
353 353  (% style="color:#037691" %)**We take LES01 as an example.**
354 354  
355 -
356 356  
357 357  )))
358 358  )))
... ... @@ -393,7 +393,6 @@
393 393  [[image:image-20220526140044-18.png]]
394 394  
395 395  
396 -
397 397  == 4.2  Step 2 ==
398 398  
399 399  
... ... @@ -406,8 +406,6 @@
406 406  )))
407 407  
408 408  
409 -
410 -
411 411  == 4.3  Step 3 ==
412 412  
413 413  
... ... @@ -417,7 +417,6 @@
417 417  [[image:image-20230221140131-4.png||height="569" width="674"]]
418 418  
419 419  
420 -
421 421  == 4.4  Step 4 ==
422 422  
423 423  
... ... @@ -427,10 +427,8 @@
427 427  [[image:image-20230221140448-6.png||height="535" width="647"]]
428 428  
429 429  
430 -
431 431  = 5.  TTN V3 integrated into MQTT server =
432 432  
433 -
434 434  == 5.1  Introduction ==
435 435  
436 436  
... ... @@ -438,7 +438,6 @@
438 438  (((
439 439  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.
440 440  
441 -
442 442  
443 443  )))
444 444  )))
... ... @@ -550,7 +550,6 @@
550 550  [[image:image-20220526140936-27.png]]
551 551  
552 552  
553 -
554 554  == 5.3  Send Downlink message ==
555 555  
556 556  
... ... @@ -628,7 +628,6 @@
628 628  downlink
629 629  
630 630  
631 -
632 632  = 6.  Route TTN data to Node-Red =
633 633  
634 634  
... ... @@ -635,7 +635,6 @@
635 635  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]]"
636 636  
637 637  
638 -
639 639  == 6.1  Edit mqtt-broker node ==
640 640  
641 641  
... ... @@ -656,7 +656,6 @@
656 656  [[image:image-20220829164358-188.png||height="570" width="1130"]]
657 657  
658 658  
659 -
660 660  == 6.2  Debug ==
661 661  
662 662  
... ... @@ -665,7 +665,6 @@
665 665  [[image:image-20220829164652-189.png||height="572" width="1134"]]
666 666  
667 667  
668 -
669 669  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
670 670  
671 671  
... ... @@ -677,7 +677,6 @@
677 677  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
678 678  
679 679  
680 -
681 681  === 6.3.1  Link Node-Red to Local TTN ===
682 682  
683 683  
... ... @@ -720,7 +720,6 @@
720 720  [[image:image-20220914140918-5.png||height="602" width="1121"]]
721 721  
722 722  
723 -
724 724  === 6.3.2 Check result. ===
725 725  
726 726  
... ... @@ -729,15 +729,12 @@
729 729  [[image:image-20220914140841-4.png||height="600" width="1119"]]
730 730  
731 731  
732 -
733 733  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.
734 734  
735 735  
736 -
737 737  [[image:image-20220914142021-7.png||height="517" width="1346"]]
738 738  
739 739  
740 -
741 741  = 7.  Request Remote Support =
742 742  
743 743  
... ... @@ -747,14 +747,19 @@
747 747  )))
748 748  
749 749  * End node is connected to serial port to show the Join frequency and DR. (If possible)
711 +
750 750  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
713 +
751 751  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
715 +
752 752  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
717 +
753 753  * 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)
754 754  
755 755  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
756 756  
757 757  * If the device is sending join request to server?
723 +
758 758  * What frequency the device is sending?
759 759  
760 760  [[image:image-20220526141308-33.png]]
... ... @@ -838,3 +838,148 @@
838 838  [[image:image-20220526142033-41.png]]
839 839  
840 840  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