Actility’s ThingPark Wireless

This page describes the use of Actility’s ThingPark Wireless as connectivity provider 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, Client ID, and Client secret are required.

Creating a service account

First you will need to create a service account. Log into your Actility instance for this and go onto the administration panel where you will be able to add a new service account. The only rights needed for it are "Devices, multicast groups and connections manager" & "Viewer".

List of Profile IDs This is mostly dependant on your host. Following is a list with all standard ones.

ThingPark Enterprise SaaS EU -> tpe-eu-api US -> tpe-us-api AU -> tpe-au1-api ThingPark Community SaaS community-api Dedicated Enterprise Tenant yourHostsName-api

Actility integration setup

After verification of provided credentials, the integration name can be specified.

If Create Integration gets selected, everything will be set up on the Actility servers by akenza automatically.

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).

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.

After the setup, the integration gets created and the initial synchronization will start. Depending on how many devices are registered, the process can take a few minutes.

Once the synchronization succeeds, all devices will be displayed in the overview of the tab Assets. The devices can now be managed on akenza.