The Things Network

This page describes the use of The Things Network as connectivity provider in akenza

On akenza, two options are available to make use of The Things Network:

1. Connectivity-as-a-Service

The Things Network can be chosen on akenza as Connectivity-as-a-Service (CaaS). Therefore, TTN CaaS needs to be selected on a Data Flow as device connector.

2. Connecting own account

The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless.

2.1 Authentication

The authentication of a TTN account is offered in multiple ways in the tab of Integrations:

2.1.1 Organization ID and API key

2.1.2 Application ID and API key

2.1.3 User ID and API key

TTN Integration login

2.1.1 Organization ID and API key

The appropriate organization ID and API key need to be provided in order to connect the akenza integration to a specific TTN organization. The API key has to have all current and further access rights. The authentication requires an organization API key or personal API key which can be deleted once the integration setup on akenza has been completed. This method will create a new application, a webhook, and an API key. The newly created API key will be stored encrypted in akenza for further communication.

2.1.2 Application ID and API key

The appropriate organization ID and API key with the necessary permissions need to be provided in order to connect the akenza integration to a specific TTN organization. Please note that either a personal API key or an application API key to authorize using this method can be used. This method will create a new webhook only. The API key will be stored encrypted in akenza for further communication.

2.1.3 User ID and API key

To create a new application for the akenza integration, a TTN user ID is necessary to authorize selectively. The API key has to have all current and further access rights.

A personal API key is needed for authentication, which can be deleted once the integration is completely set up on akenza. The permissions for the personal API key can be seen below. This method will create a new application, a webhook, and an API key. The newly created API key will be stored encrypted in akenza for further communication.

API key on TTN account

2.2 Integration login on akenza

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

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

An Integration in the application or organization will be created (depending on the chosen authentication method) on the TTN servers which are used to forward the IoT device data to 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.

Last updated

Was this helpful?