Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58

From 198.1 to 199.1 From 217.1 to 218.1

From version 199.1

edited by Xiaoye
on 2023/03/09 13:44

Change comment: There is no comment for this version

To version 217.1

edited by Xiaoye
on 2023/07/28 14:52

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 8 added, 0 removed)

Details

Page properties

Content

@@ -6,10 +6,8 @@
  = 1. The Things Network-V3 =
--
  == 1.1  Introduction ==
--
  === 1.1.1  What is The Things Network ===
@@ -20,7 +20,6 @@
  (((
  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.
--
  )))
@@ -34,7 +34,6 @@
  (((
  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
--
  )))
@@ -44,12 +44,12 @@
  LoRaWAN Gateway model: Existing Gateway
--
  = 2.  Gateway Registration for Semtech UDP =
  (% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
++
  == 2.1  Primary LoRaWAN Server ==
@@ -95,10 +95,8 @@
  Show Status
--
  == 2.2  Secondary LoRaWAN Server ==
--
  === 2.2.1  Introduction ===
@@ -105,7 +105,6 @@
  The Dragino gateway has supports the Secondary server settings.
--
  === 2.2.2  Below list the support products and Requirements: ===
@@ -118,7 +118,6 @@
  )))
--
  === 2.2.3  Example ===
@@ -125,7 +125,6 @@
  The following takes Helium as a Secondary LoRaWAN server as an example
--
  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
@@ -137,7 +137,6 @@
  Download and Install gateway-rs
--
  === 2.2.5  Step 2: Back to Semtech UDP page ===
@@ -149,10 +149,8 @@
  Configuration of helium
--
  = 3.  Gateway Registration for Basics Station =
--
  == 3.1  Introduction ==
@@ -183,7 +183,7 @@
  )))
  (((
--(% style="color:blue" %)**What do you need to prepare**
++(% style="color:blue" %)**What do you need to prepare?**
  )))
  (((
@@ -190,64 +190,69 @@
  (((
  A gateway that can access the internet normally
--
  )))
  )))
--== 3.2  Step 1: Add Gateway ==
++== 3.2  Step 1: Register Gateway ==
  (((
  (((
--(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
++(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
  )))
  )))
  (((
  (((
--User can add your gateway into The Things Network V3 according to the previous step
++Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page.
++
++[[image:image-20230728144218-7.png||height="128" width="836"]]
  )))
  )))
--(((
--(((
--Following picture is the successful added.
++[[image:image-20230728143449-2.png]]
--
--)))
--)))
++Register Gateway
--[[image:image-20220526135316-8.png]]
--Add Gateway
++== 3.3  Step 2: Create the API key ==
++**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
--== 3.3  Step 2: Create the API key ==
--user need to create the CUPS API key and LNS API key.
++**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png]]
--[[image:image-20220526135349-9.png]]
--Create CUPS API key
++=== **1.) Generated by TTH** ===
++===   ===
++===   ===
--[[image:image-20220526135428-10.png]]
++=== **2.) Manually create API KEY: ** ===
--Create LNS API key
++==== CUPS API KEY ====
--(% style="color:red" %)**Note: Please copy the API key.**
++[[image:image-20220526135349-9.png]]
--== 3.4  Step 3: Update the gateway setting ==
++==== LNS API KEY ====
++[[image:image-20220526135428-10.png]]
++
++(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.**
++
++
++==== Update the gateway setting ====
++
++
  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
@@ -256,7 +256,6 @@
  paste the API key
--
  == 3.5  Step 4: Access the gateway GUI ==
@@ -268,7 +268,6 @@
  Access the gateway GUI
--
  == 3.6  Step 5: Configure Station ==
@@ -290,7 +290,6 @@
  Congfigure Station
--
  == 3.7  Start Station ==
@@ -297,7 +297,6 @@
  (((
  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
--
  )))
@@ -312,7 +312,6 @@
  Station live date
--
  == 3.9  Trouble Shooting ==
@@ -332,7 +332,6 @@
  Recore Log
--
  = 4.  Configure node connection to TTNv3 =
@@ -352,7 +352,6 @@
  (((
  (% style="color:#037691" %)**We take LES01 as an example.**
--
  )))
  )))
@@ -393,7 +393,6 @@
  [[image:image-20220526140044-18.png]]
--
  == 4.2  Step 2 ==
@@ -406,8 +406,6 @@
  )))
--
--
  == 4.3  Step 3 ==
@@ -417,7 +417,6 @@
  [[image:image-20230221140131-4.png||height="569" width="674"]]
--
  == 4.4  Step 4 ==
@@ -427,10 +427,8 @@
  [[image:image-20230221140448-6.png||height="535" width="647"]]
--
  = 5.  TTN V3 integrated into MQTT server =
--
  == 5.1  Introduction ==
@@ -438,7 +438,6 @@
  (((
  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.
--
  )))
  )))
@@ -550,7 +550,6 @@
  [[image:image-20220526140936-27.png]]
--
  == 5.3  Send Downlink message ==
@@ -628,7 +628,6 @@
  downlink
--
  = 6.  Route TTN data to Node-Red =
@@ -635,7 +635,6 @@
  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]]"
--
  == 6.1  Edit mqtt-broker node ==
@@ -656,7 +656,6 @@
  [[image:image-20220829164358-188.png||height="570" width="1130"]]
--
  == 6.2  Debug ==
@@ -665,7 +665,6 @@
  [[image:image-20220829164652-189.png||height="572" width="1134"]]
--
  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
@@ -677,7 +677,6 @@
  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
--
  === 6.3.1  Link Node-Red to Local TTN ===
@@ -720,7 +720,6 @@
  [[image:image-20220914140918-5.png||height="602" width="1121"]]
--
  === 6.3.2 Check result. ===
@@ -729,15 +729,12 @@
  [[image:image-20220914140841-4.png||height="600" width="1119"]]
--
  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.
--
  [[image:image-20220914142021-7.png||height="517" width="1346"]]
--
  = 7.  Request Remote Support =
@@ -747,14 +747,19 @@
  )))
  * End node is connected to serial port to show the Join frequency and DR. (If possible)
++
  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
++
  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
++
  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
++
  * 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)
  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
  * If the device is sending join request to server?
++
  * What frequency the device is sending?
  [[image:image-20220526141308-33.png]]
@@ -838,3 +838,148 @@
  [[image:image-20220526142033-41.png]]
  Check if OTAA Keys match the keys in device
++
++
++= 8.  FAQ =
++
++== 8.1 How to import devices keys to server. ==
++
++
++**For TTS in LPS8v2**
++
++Open your application and click the button **Import end devices**
++
++[[image:image-20230423154012-1.png||height="472" width="755"]]
++
++
++Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv
++
++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.
++
++You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated.
++
++Start the import by clicking the **Import end devices** button.
++
++[[image:image-20230423154040-2.png||height="470" width="749"]]
++
++
++Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console.
++
++[[image:image-20230423154105-3.png||height="478" width="763"]]
++
++
++If the import was successful, your devices are added to the list of end devices in your application.
++
++[[image:image-20230423154125-4.png||height="480" width="766"]]
++
++Devices are now registered on The Things Stack.
++
++
++=== **JSON File Reference** ===
++
++
++The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices.
++
++Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions.
++
++Here is an example of an OTAA device description in the file:devices.json
++
++{{{{
++  "ids": {
++    "device_id": "my-device",
++    "dev_eui": "0102030405060708",
++    "join_eui": "0102030405060708"
++  },
++  "name": "My Device",
++  "description": "Living room temperature sensor",
++  "lorawan_version": "MAC_V1_0_2",
++  "lorawan_phy_version": "PHY_V1_0_2_REV_B",
++  "frequency_plan_id": "EU_863_870_TTN",
++  "supports_join": true,
++  "root_keys": {
++    "app_key": {
++      "key": "01020304050607080102030405060708"
++    }
++  }
++}
++}}}
++
++Multiple end devices can also be contained in a single file like so:devices.json
++
++{{{{
++  /* device 1 */
++}
++{
++  /* device 2 */
++}
++}}}
++
++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
++
++
++=== **CSV File Reference** ===
++
++
++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.
++
++The CSV import in The Things Stack uses the following settings:
++
++* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient;
++
++* Header row is required
++
++* On each row, the same number of fields as on the header line
++
++* Use quotes to use in a field value;
++
++* Use double quotes to escape quotes
++
++* Unknown header columns are permitted and ignored
++
++* Name and id cannot have capital letters and special characters
++
++* Example column lorawan_phy_version is not needed
++
++(% style="display:none" %)
++
++
++
++=== **Example** ===
++
++
++Minimal example:
++
++{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key
++1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111
++2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222
++3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333
++}}}
++
++All columns for a LoRaWAN 1.0.4 device:
++
++{{{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
++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
++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
++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
++}}}
++
++
++
++=== **Excel Template** ===
++
++
++[[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).
++
++
++= 9. Trouble Shooting. =
++
++== 9.1 How to solve the problem of MIC Mismatch？ ==
++
++
++Please refer to the link below:
++
++[[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]]
++
++
++
++

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

image-20230728143505-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoye

Size

...	...	@@ -1,0 +1,1 @@
	1	+16.7 KB

Content

image-20230728144218-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoye

Size

...	...	@@ -1,0 +1,1 @@
	1	+12.7 KB

Content

Changes for page Notes for TTN

Summary

Details

Applications

Navigation