Bulk import CSV templates
This page provides CSV templates and additional descriptions for Bulk imports
On this page, bulk import CSV templates are ready to be downloaded for:
Connectivity Management only & LoRa Data flows
For OTAA- activation mode
For ABP- activation mode
HTTP, MQTT & CoAP Data Flow
OTAA- activation mode (Over-the-Air Activation)
General field descriptions:
Field
mandatory or optional
Description
name
mandatory
Name example of device eg. Humidity Sensor 1
onlineTimeout
optional
Interval in seconds, how long a device appears (green) online in akenza after last sample eg. 86400 (= 24 hours)
applicationKey
mandatory
Provided from the device. 16 byte eg. 1213456789012345612134567890123456
applicationEui
mandatory
Provided from the device. 8 byte eg. 12134567890123456
deviceClass
mandatory
Provided from the device. eg. A, B or C
loraVersion
mandatory
Provided from the device. eg. 1.0.3
deviceEui
mandatory
Provided from the device. 8 byte eg. 12134567890123456
description
optional
Free text field. eg. Humidity Sensor 1 on floor A
frequencyPlan
optional
provided from the device and integration e.g. EU_863_870
Bulk import template - OTAA:
General field descriptions LoRa 1.1:
name
mandatory
Name example of device eg. Humidity Sensor 1
onlineTimeout
optional
Interval in seconds, how long a device appears (green) online in akenza after last sample eg. 86400 (= 24 hours)
deviceClass
mandatory
Provided from the device. eg. A, B or C
loraVersion
mandatory
1.1.0
deviceEui
mandatory
Provided from the device. 8 byte eg. 12134567890123456
joinEui
mandatory
Provided from the device. 8 byte eg. 12134567890123456
networkKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
applicationKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
description
optional
Free text field. eg. Humidity Sensor 1 on floor A
frequencyPlan
optional
provided from the device and integration e.g. EU_863_870
Bulk import template - OTAA actility:
Applies only for Swisscom and Actility connectivity carrier:
Field
mandatory or optional
Description
motionIndicator
mandatory
Valid values: NEAR_STATIC, WALKING_SPEED, VEHICLE_SPEED, BIKE_SPEED, RANDOM
activationMode
mandatory
Activating a device with Over-the-Air Activation (OTAA)
deviceProfileId
mandatory
LoRa/GenericA.1.0.3a_ETSI
connectivityPlanId
optional
eg. swisscom-cs/swisscom-cp-nb-trial
Bulk import template - OTAA actility:
Applies only for everynet connectivity carrier:
Field
mandatory or optional
Description
countersSize
mandatory
size of the device uplink and downlink counter, valid values are: 2, 4
Bulk import template - OTAA everynet:
ABP- activation mode (Activation by Personalization)
General field descriptions:
Field
mandatory or optional
Description
name
mandatory
Name example of device eg. Temperature Sensor 2
onlineTimeout
optional
Interval in seconds, how long a device appears (green) online in akenza after last sample eg. 86400 (= 24 hours)
applicationSessionKey
mandatory
Provided from the device. 16 byte eg. 1213456789012345612134567890123456
deviceClass
mandatory
Provided from the device. A, B or C
loraVersion
mandatory
Provided from the device. eg. 1.0.3
deviceEui
mandatory
Provided from the device. 8 byte eg. 12134567890123456
deviceAddress
mandatory
Provided from the device. 4 byte device address (8 characters)
networkSessionKey
mandatory
16 byte eg. 1213456789012345612134567890123456
description
optional
Free text field. eg. Temperature Sensor 2 on floor B
Bulk import template - ABP:
General field descriptions 1.1:
name
mandatory
Name example of device eg. Temperature Sensor 2
onlineTimeout
optional
Interval in seconds, how long a device appears (green) online in akenza after last sample eg. 86400 (= 24 hours)
deviceEui
mandatory
Provided from the device. 4 byte device address (8 characters)
loraVersion
mandatory
1.1.0
deviceClass
mandatory
Provided from the device. A, B or C
deviceAddress
mandatory
Provided from the device. 4 byte eg. 121345678
applicationSessionKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
forwardingNetworkSessionIntegrityKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
networkSessionEncryptionKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
servingNetworkSessionIntegrityKey
mandatory
Provided from the device. 16 byte eg. 12345678901234561234567890123456
frequencyPlan
optional
provided from the device and integration e.g. EU_863_870
description
optional
Free text field. eg. Temperature Sensor 2 on floor B
Bulk import template - ABP 1.1:
Applies only for Swisscom and Actility connectivity carrier:
Field
mandatory or optional
Description
motionIndicator
mandatory
Valid values: NEAR_STATIC, WALKING_SPEED, VEHICLE_SPEED, BIKE_SPEED, RANDOM
activationMode
mandatory
Activating a device with Activation by Personalization (ABP)
deviceProfileId
mandatory
LoRa/GenericA.1.0.3a_ETSI
connectivityPlanId
optional
eg. swisscom-cs/swisscom-cp-nb-trial
Bulk import template - ABP actility:
Applies only for everynet connectivity carrier:
Field
mandatory or optional
Description
countersSize
mandatory
size of the device uplink and downlink counter, valid values are: 2, 4
Bulk import template - ABP everynet:
HTTP, MQTT & CoAP Data Flow
General field descriptions:
Field
mandatory or optional
Description
name
mandatory
Name example of device eg. Brightness Sensor 3
onlineTimeout
optional
Interval in seconds, how long a device appears (green) online in akenza after last sample eg. 86400 (= 24 hours)
deviceId
mandatory
Provided from the device. 16 character hex string eg. 1234567890123456
description
optional
Free text field. eg. Brightness Sensor 3 on floor C
Bulk import template - HTTP, MQTT & CoAP:
Additional values Custom Fields and Tags
General field descriptions:
Field
mandatory or optional
Description
Tags
optional
Tag name or id formatted as list separated with spaces
{{CustomFieldName}}
optional
The custom field name or id is used as column name. The value has to be set based on custom field type. JSON example: {"someKey":"someValue"} GPS example: {"latitude":90, "longitude":20}
Bulk import template - custom fields and tags:
Note that custom fields to be added using the bulk import need to exist in your workspace. There is a bulk import feature to create custom fields.
Once the CSV file is uploaded, the file validation can be started. If the validation is successful, the import can start. All imported assets will be displayed now on the Asset Inventory Overview.
If you need further assistance, please contact us at [email protected]
Last updated
Was this helpful?