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. Device Management
  2. Data Flows
  3. Device Connectors
  4. LoRaWAN

Loriot

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

PreviousThe Things NetworkNextActility’s ThingPark Wireless

Last updated 5 months ago

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:

1. Connectivity-as-a-Service

The Loriot LoRaWAN network can be chosen on akenza as (CaaS). Therefore, Loriot 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. No connectivity costs will occur by using the Loriot Network.

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.

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:

curl -H "Authorization: <the field value>" https://<the-url>

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.

Connectivity-as-a-Service
Data Flow
Connectivity-as-a-Service
Connecting own account
device connector
Loriot integration setup
Account details of integration setup