Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 199.2
edited by Xiaoling
on 2023/03/09 15:23
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Xiaoye
Content
... ... @@ -708,14 +708,19 @@
708 708  )))
709 709  
710 710  * End node is connected to serial port to show the Join frequency and DR. (If possible)
711 +
711 711  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
713 +
712 712  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
715 +
713 713  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
717 +
714 714  * 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)
715 715  
716 716  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
717 717  
718 718  * If the device is sending join request to server?
723 +
719 719  * What frequency the device is sending?
720 720  
721 721  [[image:image-20220526141308-33.png]]
... ... @@ -800,4 +800,147 @@
800 800  
801 801  Check if OTAA Keys match the keys in device
802 802  
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 +
803 803  
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