To edit multiple devices in batch, open the “Mass Actions” tab and simply follow almost the same steps as when adding new devices by CSV import.
If you have previously added new devices in batch by CSV import before, you can simply upload this CSV file again with the relevant updates. If not, you can also first download a sample file and then fill it with the relevant data. When you upload the adapted file via “Upload CSV”, the system checks whether the DevEUI is known to the Datahub and, if so, the relevant changes are made.
Important: The lines with DevEUI, joinEUI, appKey and rxDelay must not be adjusted here.
The file used here must be a .csv file containing the DevEUI of the devices you want to edit, along with any other information you want to change.
For the .csv file to be recognised by the datahub, the columns must be separated by semicolons (;).
If you use a different separator, the data hub will not be able to import the file and therefore will not make any changes.
The first row must be used for the headers. These must be the exact names used by the Datahub for its values; otherwise, the Datahub will not recognise the fields and will skip them entirely.
The order of the columns does not matter, as the Datahub uses the name of each individual column, but we advise keeping the DevEUI as the first column, as this is the primary key used for detecting unique devices.
If you do not want to make changes to specific fields, simply delete the relevant column from the sample file.
We recommend doing this for the necessary technical information, such as JoinEUI, AppKey, devAddr, nwkSKey, appSKey and rxDelay.
Altering these values can prevent the devices from joining the network if done incorrectly!
To get you started, you can download the sample file or create a new file.
CSV files can be created using text editors or Microsoft Excel, but make sure you use semicolons for separation.
Below is a list of the columns from the sample file and their meaning:
Field | Meaning |
devEUI | The devEUI (Device Extended Unique Identifier) of the device |
type | The device type must be always LORA_OTAA → can remain as in sample file |
joinEUI | The joinEUI of the device |
appKey | The appKey (Application Key) of the device |
devAddr | The devAddr (Device Address) of the device, automatically regenerated during each join process when activated via OTAA → can remain as in sample file |
nwkSKey | The nwkSkey (Network Session Key) of the device, automatically regenerated during each join process when activated via OTAA → can remain as in sample file |
appSKey | The appSKey (Application Session Key) of the device, automatically regenerated during each join process when activated via OTAA → can remain as in sample file |
rxDelay | RxDelay must be always 4 → can remain as in sample file |
classC | True for class C devices, otherwise false |
activated | True or false (only if it is activated it can join) |
parser | The parser is selected here, for ZENNER & UDC Devices it must be ZENNERUSA |
status | Installation Status of the device → Mounted or dismounted |
| locationId (Project ID) | Project ID of the existing project to which the device is to be assigned, if needed |
street | The current street of the device location |
houseNo | House number of the device location |
postalCode | Postal / ZIP Code of the device location |
city | City of the device location |
geoType | Always enter “Point” unless no longitude and latitude are entered |
latitude | Latitude of the device location |
longitude | Longitude of the device location |
differentAddress | A different address can be entered here |
tenant | The tenant in which the device is created |
country | The country of the device location |
buildingNumber | The building number of the device location |
unit | The unit number of the device location |
alternative_address | An alternative address can be entered here |
| installationDate | Here you can select when the device was installed |
removalDate | Here you can select when the device was removed (if possible) |
installationPosition | Current installation Position of the device → e.g. room or floor |
medium | The medium captured by the device → water, electricity, gas |
manufacturer | The manufacturer of the device |
meterType | The meter type of the device |
pulseFactor | Pulse Factor = quantity of a pulse (see technical documents for the respective meter/device) Only important for sensors that send their data with pulse output, like ZENNER UDC Devices → see also UDC Device/Pulse Counting Must be entered, otherwise the calculation of the actual readings (measured values) and consumption will be wrong |
meterSize | The size of the meter |
initialMeterRead | Initial Meter Read of the device → Must be entered, otherwise it will assume 0. If nothing is entered, the value may be incorrect |
tags | To which tags the devices should be assigned |
If performed correctly, the datahub will display any changes it will make.
Please ensure that all detected changes are correct, as this operation cannot be reversed once completed.
Once you have checked the changes, you can start the process by clicking ‘Edit Devices’.
The datahub will then update the devices and show you the progress.
Frequent questions about Mass Editing Devices by CSV Upload
- How many devices can I change at once?
Currently, the maximum number of devices that can be changed at once is 100. If you want to change more than 100 devices, just create multiple CSV files and upload them one after the other. - Do I have to create the CSV file in a text editor?
No, you can edit them in any spreadsheet editor, such as Microsoft Excel, but make sure you use a semicolon as the separator. - The datahub does not find any of my devices in my .csv file. What can I do?
Please check your file to make sure you have used a semicolon as the separator. It’s a common mistake to use a comma instead of a semicolon here.
Also, check that you have included the correct DevEUIs and headers, as the data hub needs these to recognise the fields. - The data hub doesn’t change all the values that I wanted it to.
Check the headers in your file to make sure they are exactly the same as those used by the data hub, as we look for exact matches here. - I don’t want to change each field in the sample file. How can I just change the address and nothing else?
It’s easy! Simply open the sample file and delete every column that you don’t want to change. The only field needed every time is the DevEUI, as this is the primary key used for matching devices.
In this case, we would only need the DevEUI and the columns containing the address, such as “street”, “houseNo”, “postalCode” and “city”. - I want to add my devices to a project. Can I do this with mass edit?
Yes, just include the Project ID found in your project in the “location ID” column.
Use Case for Mass Editing of Devices
If you have just added a couple of devices, for example by provisioning, they will often only contain the necessary technical information. Adding additional information one by one would be tedious and inefficient. This is where mass editing comes in.
Either take the sample file or create one from scratch, then use a spreadsheet editor to fill in the required information.
Remember to double-check any technical information that you change here, or leave it out completely.
Upload it afterwards to change your devices in bulk quickly and easily.