Changes for page Notes for TTN
Last modified by Xiaoling on 2025/08/04 14:58
From version 217.1
edited by Xiaoye
on 2023/07/28 14:52
on 2023/07/28 14:52
Change comment:
There is no comment for this version
To version 195.1
edited by Bei Jinggeng
on 2023/02/21 14:05
on 2023/02/21 14:05
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoye1 +XWiki.Bei - 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,10 @@ 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 -(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them** 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 96 + 94 94 == 2.2 Secondary LoRaWAN Server == 95 95 99 + 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 106 + 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 119 + 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 126 + 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 138 + 131 131 === 2.2.5 Step 2: Back to Semtech UDP page === 132 132 133 133 ... ... @@ -139,17 +139,17 @@ 139 139 Configuration of helium 140 140 141 141 150 + 142 142 = 3. Gateway Registration for Basics Station = 143 143 153 + 144 144 == 3.1 Introduction == 145 145 146 146 147 147 ((( 148 148 ((( 149 -The LoRa Basics™ Station protocol simplifies themanagement 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/]]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/]] 150 150 151 -(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them** 152 - 153 153 154 154 ))) 155 155 ))) ... ... @@ -171,7 +171,7 @@ 171 171 ))) 172 172 173 173 ((( 174 -(% style="color:blue" %)**What do you need to prepare ?**182 +(% style="color:blue" %)**What do you need to prepare** 175 175 ))) 176 176 177 177 ((( ... ... @@ -178,69 +178,64 @@ 178 178 ((( 179 179 A gateway that can access the internet normally 180 180 189 + 181 181 182 182 ))) 183 183 ))) 184 184 185 -== 3.2 Step 1: RegisterGateway ==194 +== 3.2 Step 1: Add Gateway == 186 186 187 187 188 188 ((( 189 189 ((( 190 -(% style="color:blue" %)**The example for**(%%)** the(% style="color:red" %)EU:(%%)**199 +(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)** 191 191 ))) 192 192 ))) 193 193 194 194 ((( 195 195 ((( 196 -Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page. 197 - 198 -[[image:image-20230728144218-7.png||height="128" width="836"]] 205 +User can add your gateway into The Things Network V3 according to the previous step 199 199 ))) 200 200 ))) 201 201 202 -[[image:image-20230728143449-2.png]] 209 +((( 210 +((( 211 +Following picture is the successful added. 203 203 204 -Register Gateway 213 + 214 +))) 215 +))) 205 205 217 +[[image:image-20220526135316-8.png]] 206 206 207 - ==3.3 Step 2: Createthe API key==219 +Add Gateway 208 208 209 209 210 -**API Key can be created manually** ~-~--> if users forgot to check the check box or switch to basic station mode from the Semtech UDP mode 211 211 223 +== 3.3 Step 2: Create the API key == 212 212 213 213 226 +user need to create the CUPS API key and LNS API key. 214 214 215 -**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png]] 216 216 217 - 218 -=== **1.) Generated by TTH** === 219 - 220 -=== === 221 - 222 -=== === 223 - 224 -=== **2.) Manually create API KEY: ** === 225 - 226 - 227 -==== CUPS API KEY ==== 228 - 229 229 [[image:image-20220526135349-9.png]] 230 230 231 +Create CUPS API key 231 231 232 232 233 -==== LNS API KEY ==== 234 234 235 235 [[image:image-20220526135428-10.png]] 236 236 237 +Create LNS API key 237 237 238 -(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.** 239 239 240 +(% style="color:red" %)**Note : Please copy the API key.** 240 240 241 -==== Update the gateway setting ==== 242 242 243 243 244 +== 3.4 Step 3: Update the gateway setting == 245 + 246 + 244 244 In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step. 245 245 246 246 ... ... @@ -249,6 +249,7 @@ 249 249 paste the API key 250 250 251 251 255 + 252 252 == 3.5 Step 4: Access the gateway GUI == 253 253 254 254 ... ... @@ -260,6 +260,7 @@ 260 260 Access the gateway GUI 261 261 262 262 267 + 263 263 == 3.6 Step 5: Configure Station == 264 264 265 265 ... ... @@ -281,6 +281,7 @@ 281 281 Congfigure Station 282 282 283 283 289 + 284 284 == 3.7 Start Station == 285 285 286 286 ... ... @@ -287,6 +287,7 @@ 287 287 ((( 288 288 When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network. 289 289 296 + 290 290 291 291 ))) 292 292 ... ... @@ -301,6 +301,7 @@ 301 301 Station live date 302 302 303 303 311 + 304 304 == 3.9 Trouble Shooting == 305 305 306 306 ... ... @@ -320,6 +320,7 @@ 320 320 Recore Log 321 321 322 322 331 + 323 323 = 4. Configure node connection to TTNv3 = 324 324 325 325 ... ... @@ -339,6 +339,7 @@ 339 339 ((( 340 340 (% style="color:#037691" %)**We take LES01 as an example.** 341 341 351 + 342 342 343 343 ))) 344 344 ))) ... ... @@ -379,6 +379,7 @@ 379 379 [[image:image-20220526140044-18.png]] 380 380 381 381 392 + 382 382 == 4.2 Step 2 == 383 383 384 384 ... ... @@ -386,11 +386,14 @@ 386 386 ((( 387 387 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. 388 388 389 - [[image:image-20230221164809-2.png||height="525"width="617"]]400 + 390 390 ))) 391 391 ))) 392 392 404 +[[image:image-20220526140132-19.png]] 393 393 406 + 407 + 394 394 == 4.3 Step 3 == 395 395 396 396 ... ... @@ -400,6 +400,7 @@ 400 400 [[image:image-20230221140131-4.png||height="569" width="674"]] 401 401 402 402 417 + 403 403 == 4.4 Step 4 == 404 404 405 405 ... ... @@ -409,8 +409,10 @@ 409 409 [[image:image-20230221140448-6.png||height="535" width="647"]] 410 410 411 411 427 + 412 412 = 5. TTN V3 integrated into MQTT server = 413 413 430 + 414 414 == 5.1 Introduction == 415 415 416 416 ... ... @@ -418,6 +418,7 @@ 418 418 ((( 419 419 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. 420 420 438 + 421 421 422 422 ))) 423 423 ))) ... ... @@ -529,6 +529,7 @@ 529 529 [[image:image-20220526140936-27.png]] 530 530 531 531 550 + 532 532 == 5.3 Send Downlink message == 533 533 534 534 ... ... @@ -606,6 +606,7 @@ 606 606 downlink 607 607 608 608 628 + 609 609 = 6. Route TTN data to Node-Red = 610 610 611 611 ... ... @@ -612,6 +612,7 @@ 612 612 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]]" 613 613 614 614 635 + 615 615 == 6.1 Edit mqtt-broker node == 616 616 617 617 ... ... @@ -632,6 +632,7 @@ 632 632 [[image:image-20220829164358-188.png||height="570" width="1130"]] 633 633 634 634 656 + 635 635 == 6.2 Debug == 636 636 637 637 ... ... @@ -640,6 +640,7 @@ 640 640 [[image:image-20220829164652-189.png||height="572" width="1134"]] 641 641 642 642 665 + 643 643 == 6.3 Example: Use Local Server TTN and Node-Red in LPS8v2 == 644 644 645 645 ... ... @@ -651,6 +651,7 @@ 651 651 Below are the steps to plot the sensor data on LPS8v2 Node-Red. 652 652 653 653 677 + 654 654 === 6.3.1 Link Node-Red to Local TTN === 655 655 656 656 ... ... @@ -693,6 +693,7 @@ 693 693 [[image:image-20220914140918-5.png||height="602" width="1121"]] 694 694 695 695 720 + 696 696 === 6.3.2 Check result. === 697 697 698 698 ... ... @@ -701,12 +701,15 @@ 701 701 [[image:image-20220914140841-4.png||height="600" width="1119"]] 702 702 703 703 729 + 704 704 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. 705 705 706 706 733 + 707 707 [[image:image-20220914142021-7.png||height="517" width="1346"]] 708 708 709 709 737 + 710 710 = 7. Request Remote Support = 711 711 712 712 ... ... @@ -716,19 +716,14 @@ 716 716 ))) 717 717 718 718 * End node is connected to serial port to show the Join frequency and DR. (If possible) 719 - 720 720 * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible) 721 - 722 722 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible) 723 - 724 724 * End Node traffic (from server UI) to shows end node activity in server. (Normally possible) 725 - 726 726 * 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) 727 727 728 728 (% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 729 729 730 730 * If the device is sending join request to server? 731 - 732 732 * What frequency the device is sending? 733 733 734 734 [[image:image-20220526141308-33.png]] ... ... @@ -812,148 +812,3 @@ 812 812 [[image:image-20220526142033-41.png]] 813 813 814 814 Check if OTAA Keys match the keys in device 815 - 816 - 817 -= 8. FAQ = 818 - 819 -== 8.1 How to import devices keys to server. == 820 - 821 - 822 -**For TTS in LPS8v2** 823 - 824 -Open your application and click the button **Import end devices** 825 - 826 -[[image:image-20230423154012-1.png||height="472" width="755"]] 827 - 828 - 829 -Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv 830 - 831 -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. 832 - 833 -You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated. 834 - 835 -Start the import by clicking the **Import end devices** button. 836 - 837 -[[image:image-20230423154040-2.png||height="470" width="749"]] 838 - 839 - 840 -Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console. 841 - 842 -[[image:image-20230423154105-3.png||height="478" width="763"]] 843 - 844 - 845 -If the import was successful, your devices are added to the list of end devices in your application. 846 - 847 -[[image:image-20230423154125-4.png||height="480" width="766"]] 848 - 849 -Devices are now registered on The Things Stack. 850 - 851 - 852 -=== **JSON File Reference** === 853 - 854 - 855 -The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices. 856 - 857 -Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions. 858 - 859 -Here is an example of an OTAA device description in the file:devices.json 860 - 861 -{{{{ 862 - "ids": { 863 - "device_id": "my-device", 864 - "dev_eui": "0102030405060708", 865 - "join_eui": "0102030405060708" 866 - }, 867 - "name": "My Device", 868 - "description": "Living room temperature sensor", 869 - "lorawan_version": "MAC_V1_0_2", 870 - "lorawan_phy_version": "PHY_V1_0_2_REV_B", 871 - "frequency_plan_id": "EU_863_870_TTN", 872 - "supports_join": true, 873 - "root_keys": { 874 - "app_key": { 875 - "key": "01020304050607080102030405060708" 876 - } 877 - } 878 -} 879 -}}} 880 - 881 -Multiple end devices can also be contained in a single file like so:devices.json 882 - 883 -{{{{ 884 - /* device 1 */ 885 -} 886 -{ 887 - /* device 2 */ 888 -} 889 -}}} 890 - 891 -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 892 - 893 - 894 -=== **CSV File Reference** === 895 - 896 - 897 -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. 898 - 899 -The CSV import in The Things Stack uses the following settings: 900 - 901 -* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient; 902 - 903 -* Header row is required 904 - 905 -* On each row, the same number of fields as on the header line 906 - 907 -* Use quotes to use in a field value; 908 - 909 -* Use double quotes to escape quotes 910 - 911 -* Unknown header columns are permitted and ignored 912 - 913 -* Name and id cannot have capital letters and special characters 914 - 915 -* Example column lorawan_phy_version is not needed 916 - 917 -(% style="display:none" %) 918 - 919 - 920 - 921 -=== **Example** === 922 - 923 - 924 -Minimal example: 925 - 926 -{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key 927 -1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111 928 -2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222 929 -3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333 930 -}}} 931 - 932 -All columns for a LoRaWAN 1.0.4 device: 933 - 934 -{{{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 935 -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 936 -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 937 -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 938 -}}} 939 - 940 - 941 - 942 -=== **Excel Template** === 943 - 944 - 945 -[[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). 946 - 947 - 948 -= 9. Trouble Shooting. = 949 - 950 -== 9.1 How to solve the problem of MIC Mismatch? == 951 - 952 - 953 -Please refer to the link below: 954 - 955 -[[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]] 956 - 957 - 958 - 959 -
- image-20230221164647-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.6 KB - Content
- image-20230221164809-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.9 KB - Content
- 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
- image-20230728144218-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoye - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.7 KB - Content