akenza.io
WebsiteAPI DocumentationWhat's newLogin
  • Overview
  • Getting Started
    • Connect a Device
  • Changelog
  • General
    • Applications
    • Organization context
    • Workspace Context
    • Users
      • User Roles
  • Device Management
    • Managing an organization
      • API keys
      • Users (Organization)
        • Add & removing users from your organization
    • Managing a workspace
      • General Settings
        • Device Lifecycle Reports
        • Workspace properties
        • Occupancy settings
        • Device Setup Assistant
      • Custom fields
      • Tags
      • Users (Workspace)
    • Devices
      • Device
      • Device Simulator
      • Bulk actions
      • Bulk import CSV templates
    • Rules
      • Input
      • Logic blocks
        • Comparison
        • Custom Logic
          • Logic Block Scripting
      • Timed Rules
      • Rule Actions
        • Downlink
    • Data Flows
      • Device Connectors
        • Device Security
          • Using Device Credentials
            • Creating Public/Private Key Pairs
            • Using JSON Web Tokens (JWTs)
              • Python
              • Java
        • HTTP
        • MQTT
        • CoAP
        • LoRaWAN
          • Connectivity Management
          • Swisscom LoRaWAN
          • The Things Network
          • Loriot
          • Actility’s ThingPark Wireless
          • EWZ
          • Cibicom
          • Helium
          • ChirpStack
        • NB-IoT
        • mioty
        • Disruptive Technologies
        • VergeSense
        • Spaceti
        • Haltian
      • Device Types
        • Custom Device Types
          • Uplink
          • Downlink
          • Scripting
        • Library
      • Output Connectors
        • Databases
          • akenza DB
          • InfluxDB
          • SQL Databases
        • Streaming
          • Webhook
          • Azure IoT Hub
          • AWS Kinesis
          • Google Cloud Pub/Sub
          • Apache Kafka
        • Notifications
          • E-Mail
          • SMS
          • Microsoft Teams
          • Slack
    • Custom Components
    • Integrations
    • Reference
      • REST API
        • Filtering
        • Querying Device Data
      • WebSocket API
      • Scripting
        • Stateful Operations
        • Utility Functions
      • Payload Templating
  • Reference
  • Dashboard Builder
    • Managing Dashboards
      • Embedding dashboards
    • Components
      • Map
      • Floorplan
  • Device Setup Assistant
    • Device Setup Assistant - Overview
  • Tutorials
    • BI Tools
      • Grafana Data Source Plugin
      • How to build a dashboard with Retool
      • How to analyze data with AWS QuickSight
    • Devices
      • How to integrate the XDK device from Legic via MQTT on akenza
      • How to connect the Disruptive Technologies-cloud on akenza
      • How to send Downlinks to the Kuando Busylight device
      • How to integrate an Arduino device via MQTT on akenza
      • Integrate a MClimate Vicki LoRaWAN Radiator Thermostat on akenza
      • How to integrate an ERS Elsys device with Loriot on akenza
      • How to integrate the IAM Decentlab device with TTN on akenza
      • How to integrate the Seeed SenseCAP T1000 tracker on akenza
      • How to integrate a Swisscom Multisense device on akenza
    • Notifications
      • How to send SMS notifications
      • How to send notifications to Slack
      • How to send notifications to Microsoft Teams
    • Enterprise solutions
      • How to send data to Azure IoT Hub
      • How to send data to the Google Cloud Pub/Sub
      • How to send data to InfluxDB
      • How to send data to AWS Kinesis
      • How to send data to Azure Event Hubs with Apache Kafka
    • IoT Starter Kits
      • How to integrate the IAQ Kit with Actility on akenza
      • How to integrate the CoWork Kit with Actility on akenza
      • How to integrate the Smart Building Kit with Actility on akenza
      • How to integrate the Pepperl+Fuchs Kit with Actility on akenza
  • Support Center
    • FAQ
    • Status Page
    • Service Desk
    • Request a feature
  • Deprecated
    • SIM-Cards
    • Everynet
    • Sigfox
    • How to connect the Yanzi Lifecycle cloud on akenza
Powered by GitBook
On this page
  • 1. Connectivity-as-a-Service
  • 2. Connecting own account

Was this helpful?

  1. Deprecated

Everynet

This page describes the use of Everynet as connectivity provider in akenza

PreviousSIM-CardsNextSigfox

Last updated 2 years ago

Was this helpful?

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 (CaaS). Therefore, Everynet CaaS needs to be selected on a as .

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

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.

2.3 Webhook setup for Up- & Downlinks

As a third step, an HTTP connection for each up- and downlink message needs to be created on the Everynet account in Connections - HTTP.

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.

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.

Everynet
Connectivity-as-a-Service
Data Flow
Connectivity-as-a-Service
Connecting own account
device connector
2.1 API key creation on Everynet account
2.2 Verify Everynet account on akenza
2.3 Webhook setup for Up- & Downlinks
Create API key on Everynet account
Integration login
Connections
Integration setup with HTTP parameters