CSV-Import

Content

CSV-Import for virtual devices

Up to 500 virtual devices can be imported via CSV file. To do this, click on the bulk import button () and select the account into which the devices are to be imported, whether a device template should be applied, and the connector through which the devices to be created are to receive data.

The following steps are required:

  • Define import variables: An overview of the available variables and their meaning can be found in the following table: Import variables. It is also possible to create and download a template for the import file. Use the dropdown to select the optional columns that should be present in the file. The mandatory fields defined for the selected connector are already preselected.

  • Upload the CSV file: Upload the prepared CSV file. If the CSV file contains errors, the error messages including the corresponding line in the file are displayed here. This makes it easy to identify the issue.

  • Review and confirm: After a title has been entered, a background job can be created by clicking the “Create” button. After that, one device is created automatically per second. The individual jobs are executed system-wide one after another. The job starts as soon as the previous jobs have been completed. The status of the import can be viewed in the background jobs. Errors are also listed there if devices cannot be imported. Once the import has finished, you can leave the page.

CSV format notes:

  • Separator:
    In the CSV file it is possible to use commas as separators as well as semicolons.
  • UTF-8 encoding: The CSV file should be saved using UTF-8 encoding.

Import variables

The following variables are available for CSV import.

General variables

Variable Description
coordinates Location coordinates in the format latitude,longitude.
custom_KEYNAME Custom properties. Use the key with the custom_ prefix in the header and provide the matching value in the row.
description Description text of the virtual device in niotix.
device_id ID of the device to be imported. For Firefly devices, this corresponds to the Device EUI.
deviceType ID of the niotix device type used to parse the payload.
deviceDriver ID of the device driver. This field can only be used when no device template is applied.
groups Device groups in niotix.
faIcon Icon shown in the UI. See Font Awesome V5 Icon Overview.
isDeviceImport If this parameter is not set, niotix will try to create the device in the external system, e.g. Firefly. If the devices already exist in the external system, they only need to be imported. In that case, set this parameter to true.
location Postal address where the device is located. Please use the format Street, City, Country or at least City, Country so that the coordinate lookup works correctly. Example: Bei den Mühren 70, 20457 Hamburg, Deutschland.
operationalStatus Operational status of the virtual device in niotix.
performAddressLookup Automatically looks up the address when coordinates are imported. Use it together with coordinates.
performCoordinateLookup Automatically looks up coordinates when a postal address is imported. Use it together with location.
tags Tags of the virtual device in niotix.
targetReferenceId_KEYNAME Reference ID for Dynamical Data Routing. Replace KEYNAME with the reference key of the target digital twin, e.g. targetReferenceId_Melo. The CSV row then contains the corresponding reference value, e.g. MesslokationsnummerWert.
title Display name of the virtual device in niotix.

Firefly-specific variables

Variable Description
activation LoRaWAN join procedure of the device. Choose OTAA for joining via application key or ABP for manually assigned session keys and device address. Import devices with different join procedures in separate imports.
adr_limit LoRaWAN adaptive data rate.
application_key LoRaWAN application key. Only relevant for OTAA.
application_session_key LoRaWAN application session key. Only relevant for ABP.
class_c Defines whether the device is a Class C device.
deduplicate Defines how duplicate messages should be handled.
address LoRaWAN device address for ABP devices. Not relevant for OTAA.
network_session_key LoRaWAN network session key. Only relevant for ABP.
region LoRaWAN regional parameter. Default: EU868.
rx2_data_rate Data rate including spreading factor and bandwidth.
skip_fcnt_check Defines whether the LoRaWAN frame counter should be ignored.