Devices which you’ve directly ordered from ZENNER, also for example via the ZENNERShop, usually are stored automatically in the UAA tenant after production. This means that you can usually simply add your devices to your customer tenant by provisioning instead of having to add them as new to the Datahub.
Devices can be provisioned or also deprovisioned under “Mass actions”.
In this case, provisioning means activating the sensor. Deprovisioning, on the other hand, refers to deactivating the sensor. Deprovisioning moves a sensor (back) to the UAA tenant and it can no longer send measured values. If the sensor is to be reactivated at a later time, it can be reactivated using the provisioning command. Only the DevEUI is then required for this process.
The process of provisioning differs from that of creating new devices. Rather than adding new devices to the datahub, it involves pulling them from the UAA tenant to the working tenant.
We only need the DevEUI to tell the datahub which devices to pull.
All information about the devices that the datahub already knows will also be moved.
For example, the keys such as the AppKey or JoinEUI that are necessary for the devices to join the network will be included.
For a single DevEUI, it can be entered in the text field and then executed using the Provision or Deprovision command.
If several devices are provisioned or deprovisioned, a CSV file can be imported via “Load CSV File” located directly below the provision device DevEUI field as shown in the image below.
For this process, all DevEUIs that are to be provisioned or deprovisioned must be listed in the csv file.
The file must contain nothing but the DevEUIs that should be provisioned.
An example file looks like this:
04B648F030001234
04B648F030001235
04B648F030001236
04B648F030001237
04B648F030001238
…
Frequent questions about Provisioning/Deprovisioning
- If a device is to be provisioned, does it make a difference in which tenant it is currently located?
→ Yes, because devices can only be provisioned if they are currently in the UAA tenant. - If a device is deprovisioned, will it be deleted?
→ No. Deprovisioned devices are moved to the UAA tenant along with their measured values - If I provision a device, what happens to its previously sent values?
→ When a device is provisioned, all associated packages and measured values are also transferred. - If a device doesn’t seem to join and the datahub states that it is “deactivated” what can I do?
→ Provisioning will also activate the device. This means that the network allows the device to join. - I want to move gateways from the UAA tenant as well Can I do this with provisioning?
→ No, Gateways can’t be provisioned like devices can. To move them please refer the section “Move Devices”. Note that you will need to have access to the current tenant in which the gateway is located. - I accidentally provisioned or deprovisioned a device I did not mean to. What can I do now?
→ Just do it the opposite way around. There is no limit to how often devices can be provisioned. - I have provisioned all of my devices but now I want to fill them with additional information like the address
→ You can do this easily by mass editing them with another csv file. Please refer to “Edit by CSV Upload”
Use Case for Provisioning/Deprovisioning
- If you receive your devices directly from ZENNER, provisioning is the way to go. During production, the devices will be made known to the Datahub, along with all the technical information necessary for them to function properly in our network.
- If you want to add them to your working tenant, there is no need to add them as a new device, since they are already known to the Datahub, along with everything they need to function.
This is therefore a more convenient way to add them to your working tenant.
You only need to know the DevEUIs of the devices you want to add and include them in a CSV file as explained here.
The devices will then be activated and moved to your tenant, ready to join the network and start working.
Everything that the datahub knows about the devices, including measured values, will also be moved with them. - If you want to remove devices without deleting them outright, you can deprovision them. This process deactivates the devices and moves them back to the UAA tenant.
This ensures that the devices cannot send data or join the network.
This is useful when devices reach the end of their life or when you need to temporarily deactivate them to extend their battery life.