akenza.io
Search…
Actility’s ThingPark Wireless
This page describes the setup process of a Actility’s ThingPark Wireless account to be used in akenza
Actility is powering a vast majority of public LoRaWAN® networks through its ThingPark Wireless LPWAN core network platform for Service Providers.
The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless.

Connecting own account

In order to manage an Actility’s ThingPark Wireless LoRaWAN account, only the profile ID, username and password are required. For further communication with the system in question, an API-User will be generated by akenza.
Said password is never stored in akenza!
Integration Login
If the entered credentials are correct, the integration name and how the data is processed can be specified in the next step.
If the checkbox "Process Data in Akenza" is selected, the data will be forwarded to akenza. This only affects devices created through akenza and has no impact on already registered devices. If this option is unchecked, the data will not be forwarded to akenza. Instead, devices created through akenza will have the default data route assigned, which can be configured on the Actility system. Alternatively, during the setup of the integration, a new data route can be created. If this option is checked, the newly created data route will be assigned to all devices created through akenza (in addition to the data route forwarding the data to akenza, if specified).
Integration name & Data Routes
When creating a data route, the content type and destination can be specified.
It is highly encouraged to use uplink and downlink security.
Otherwise, IoT devices and applications can be compromised.
The Application Server ID can be any string, however, it would be best if a long and random generated string is used instead.
The Application Server Key needs to be a HEX string consisting of 32 characters. The functionality to generate such a random key is provided by akenza.
Create new Data Route
After everything is set, the integration is created and the initial synchronization is started. Depending on how many devices are registered, this could take several minutes.
Once the synchronization was successful, the devices appear in the Asset Inventory Overview. Now the devices can be managed through akenza.
Last modified 3mo ago
Copy link