Differences

This shows you the differences between two versions of the page.

--- wiki:bulkupload [2023/08/01 19:14] – mbrauer
+++ wiki:bulkupload [2023/08/01 19:50] (current) – mbrauer
@@ Line 16: / Line 16: @@
   * udtName: The UDT name associated with the device. This initializes the correct UDT instance in the selected tag provider and associates an existing decoder with the device. The LoRaWan/Regional Parameters versions are also specified by the UDT. Options for UDT Names can be found in your existing UDT Definitions, or you may specify one type of UDT for the entire upload by selecting the //Single Device Type// option on the bulk upload menu.
-         * There are several supported udtNames that come with the module: Dragino, TWTG-Pressure-V3, TWTG-Temperature-Transmitter-V4, TWTG-Vibration-V3, TE, Vutility-HotDrop, TEConnectivityPressure-US8900, TEConnectivityVibration-8391N, Abeeway, Adeunis, Aloxy, RadioBridgeVoltage, RadioBridgeMoisture, RadioBridgeTemperature, RadioBridge4-20ma, RadioBridgeAccelerometer
-RadioBridgeContactSensor, RadioBridgeVibration, RadioBridgeHumidity, RadioBridgeLevel, RiotWirelessLevel, SushiVibration, SushiTemperature, SushiPressure, TektelicTracker, TektelicTundra, VegaAir, VoBoGP-1, Ellenex-PDS2-L
-and Tekelek888
-         * You can also upload a custom UDT in the Data Manager, and use the names of a custom UDT to bulk upload.
   * description: A brief description of the device. This field can contain additional information or notes about the device. The value can be a string of characters.
@@ Line 31: / Line 25: @@
 **Alternate Formats**
-  * Alternate formats are partially supported, such as the device export format from the TTN, where the column names available are dev_eui, join_eui, name, app_key, and description instead of the ones mentioned above. However, a single device type would need to be specified or an extra column (denoted udtName) added to the csv with the correct UDT definition names for tags to be created for each device.
+  * Alternate formats are supported, such as the device export format from the TTN, where the column names available are dev_eui, join_eui, name, app_key, and description instead of the ones mentioned above. However, a single device type would need to be specified or an extra column (denoted udtName) added to the csv with the correct UDT definition names for tags to be created for each device.
 **Formatting Guidelines**
@@ Line 50: / Line 44: @@
   * There should be no additional columns or data beyond the required columns specified above. Any extra columns will be ignored during the upload process.
+         * There are several UDTs that are currently supported by the SiteSync module: Dragino, TWTG-Pressure-V3, TWTG-Temperature-Transmitter-V4, TWTG-Vibration-V3, TE, Vutility-HotDrop, TEConnectivityPressure-US8900, TEConnectivityVibration-8391N, Abeeway, Adeunis, Aloxy, RadioBridgeVoltage, RadioBridgeMoisture, RadioBridgeTemperature, RadioBridge4-20ma, RadioBridgeAccelerometer, RadioBridgeContactSensor, RadioBridgeVibration, RadioBridgeHumidity, RadioBridgeLevel, RiotWirelessLevel, SushiVibration, SushiTemperature, SushiPressure, TektelicTracker, TektelicTundra, VegaAir, VoBoGP-1, Ellenex-PDS2-L, and Tekelek888. You may use these as options for the udtName column if a single device type is not specified.
+         * You can also upload a custom UDT in the Data Manager, and use the name of a this UDT in the udtName column of the CSV file for bulk uploading.
 **Conclusion**
 By adhering to the specified format and guidelines outlined in this documentation, you will be able to successfully perform bulk device uploads using a CSV file. Ensure that your CSV file contains all the required columns and that the values are correctly formatted.