This page describes the setup process of the Loriot account to be used in akenza
Loriot offers a worldwide LoRa network. The use of the community server is offered for free. For a private LoRa network, the own server can be purchased. With the use of the free Loriot account tier, some restrictions apply.
The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless.
The integration does not require an account with the network provider, as this is provided by akenza. When using Loriot, there is no monthly fee for devices connected using an akenza integration.

Connecting own account

Two authentication methods to set up the integration are provided: Username and password or API Key.
When authenticating with username and password, akenza creates an API Key on the Loriot server which is used for further communication. The username and password are not stored in akenza.
When authenticating with an API Key, the API Key is stored encrypted in akenza and used for further communication with the Loriot system.
The appropriate host can be selected or if applicable, the URL has to be entered from the own Loriot server. Furthermore, the preferred authentication method can be chosen.
Integration Login
After the credentials have been verified, the integration name can be introduced and the application on the Loriot server selected. A new application can be created, or in the case of an already existing IoT project, there is the option to directly connect to the existing one.
In the case of a new application, a name and the specification of the maximal device capacity of the application is given. Whether or not to process the data in akenza and/or send to a 3rd party system instead, can also be specified.
If processing the data in akenza is chosen, each device created through akenza will forward its data to akenza.
If the data shall be processed in a different way, the data routing can be set in the Loriot account.
Integration name & available applications
When creating a new data route, the destination URL and authorization header need to be set. Noting that the authorization header will be in the following format:
curl -H "Authorization: <the field value>" https://<the-url>
Other custom headers can't be added at this moment.
After everything is set up, the integration is created and the initial synchronization is started. This can take several minutes, depending on how many devices are already registered on the account.
Once the synchronization was successful, the devices appear in the Asset Inventory Overview. Now the devices can be managed through akenza.
Last modified 6mo ago
Copy link