akenza.io
Search…
Everynet
This page describes the use of Everynet as connectivity provider in akenza
Everynet operates Low-Power Wide-Area (LPWA) networks in major geographies around the globe. Everynet maintains the highest service levels through 24x365 Network Operations Centre (NOC) and associated operational policies and procedures.
On akenza, two options are available to make use of Everynet:

1. Connectivity-as-a-Service

Everynet can be chosen on akenza as Connectivity-as-a-Service (CaaS). Therefore, Everynet 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. Additional connectivity costs will occur by using Everynet LoRaWAN.

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. In order to integrate the Everynet account in akenza, the following steps are required.

2.1 API key creation on Everynet account

As a first step, an API key needs to be created on the account of Everynet. This can be created in Keys - Create API keys of the Everynet account. ALL permissions need to be provided for:
  • Devices
  • Filters
  • Connections
Create API key on Everynet account
Important: The API key (Access Token) needs to be copied instantly once the key gets saved.

2.2 Verify Everynet account on akenza

As a second step, Everynet needs to be selected on akenza in the tab of Integrations. Following authentication methods can be chosen from:
  • Everynet LoRaWAN Host EU or US and API key
  • Everynet LoRaWAN Host Custom and API key
When authenticating with the API key, the key is stored encrypted in akenza and used for further communication with the Everynet system.
Integration login
As a third step, an HTTP connection for each up- and downlink message needs to be created on the Everynet account in Connections - HTTP.
Connections
The following parameters are required for each connector:
HTTP Uplink parameter
  • Filter
  • Application URL
HTTP Downlink parameter
  • Auth header
  • Filter
  • Application URL
All required parameters are displayed during the Integration- or Data Flow setup.
Integration setup with HTTP parameters
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 modified 4mo ago
Copy link
On this page
1. Connectivity-as-a-Service
2. Connecting own account