Loriot
This page describes the use of Loriot as connectivity provider in akenza
Last updated
Was this helpful?
This page describes the use of Loriot as connectivity provider in akenza
Last updated
Was this helpful?
Loriot provides a global Low Power Network (LPN) over LoRaWAN. The use of the community server is offered for free. For a private LoRa network, the own server can be purchased.
On akenza, two options are available to make use of the Loriot LoRaWAN network:
The Loriot LoRaWAN network can be chosen on akenza as Connectivity-as-a-Service (CaaS). Therefore, Loriot CaaS needs to be selected on a Data Flow as device connector.
CaaS allows one to quickly get started with an IoT project without the need of setting up an individual account for a network provider. The LoRaWAN account gets managed through akenza. Device connectivity prices will be invoiced automatically through akenza. No connectivity costs will occur by using the Loriot Network.
The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless.
Two authentication methods to set up the integration are provided:
Username and password
API key (to be created in Account - API keys of Loriot)
When authenticating with a username and password, akenza creates an API key on the Loriot server which is used for further communication. When authenticating with an API key, the key is stored encrypted in akenza and used for further communication with the Loriot system.
The username and password are not stored in akenza.
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.
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 are given. Whether or not to process the data in akenza and/or send it 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.
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:
Other custom headers can't be added.
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.
