Changes for page Notes for TTN

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

From 198.1 to 199.1 From 205.1 to 206.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 205.1

edited by Bei Jinggeng
on 2023/03/21 16:12

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

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

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 ==
@@ -190,7 +190,6 @@
  (((
  A gateway that can access the internet normally
--
  )))
  )))
@@ -223,7 +223,6 @@
  Add Gateway
--
  == 3.3  Step 2: Create the API key ==
@@ -244,7 +244,6 @@
  (% style="color:red" %)**Note: Please copy the API key.**
--
  == 3.4  Step 3: Update the gateway setting ==
@@ -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 =
@@ -838,3 +838,112 @@
  [[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:https://www.thethingsindustries.com/docs/getting-started/migrating/import-end-devices.png||alt="import devices" height="517" width="828"]]
++
++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:https://www.thethingsindustries.com/docs/getting-started/migrating/upload-file.png||alt="upload devices.json file" height="536" width="858"]]
++
++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:https://www.thethingsindustries.com/docs/getting-started/migrating/operation-finished.png||alt="import finished" height="551" width="882"]]
++
++If the import was successful, your devices are added to the list of end devices in your application.
++
++[[image:https://www.thethingsindustries.com/docs/getting-started/migrating/successful-import.png||alt="successful-import" height="556" width="889"]]
++
++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
++
++=== 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).

Changes for page Notes for TTN

Summary

Details

Applications

Navigation