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
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:
Bulk import template - OTAA activation mode.csv
248B
Text
General field descriptions LoRa 1.1:
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) |
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:
Bulk import template - OTAA 1.1 activation mode.csv
283B
Text
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:
Bulk import template - OTAA activation mode - actility.csv
343B
Text
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:
Bulk import template - ABP activation mode.csv
301B
Text
General field descriptions 1.1:
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) |
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:
Bulk import template - ABP 1.1 activation mode.csv
441B
Text
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:
Bulk import template - ABP activation mode - actility.csv
398B
Text
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:
Bulk import template - HTTP, MQTT & CoAP data flow.csv
87B
Text
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.
Last modified 2mo ago