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
  • Integrate your LoRaWAN Network Server (LNS) Account
  • Synchronizing an Integration
  • Data Routes
  • Device Connectors

Was this helpful?

  1. Device Management

Integrations

PreviousCustom ComponentsNextReference

Last updated 5 months ago

Was this helpful?

Integrate your LoRaWAN Network Server (LNS) Account

Akenza seamlessly integrates with various connectivity providers. These integrations can be used to connect, synchronize and manage Assets of a connectivity provider account.

The below list consists of all supported connectivity providers and their feature sets.

Integration provider

Type

Coverage

Asset Sync

Data Routes

Swisscom LoRaWAN

LoRaWAN

Switzerland

Yes

Yes

EWZ LoRaWAN

LoRaWAN

Zurich

Yes

Yes

Loriot

LoRaWAN

global

Yes

Yes

Actility's ThingPark Wireless

LoRaWAN

global

Yes

Yes

The Things Network

LoRaWAN

global

Yes

No

Integrations allow the management of Devices and Sim Cards of connectivity providers. This enables the integration of already existing assets into akenza and manages all Assets from a single point.

Depending on the connectivity provider, multiple options for authorizing the process are available. These are described in the individual documentation.

Synchronizing an Integration

By clicking on the synchronize action on the Integration list, the synchronization process starts. On the first setup, the Integration synchronizes automatically. All changes will be applied from the connectivity provider to the Inventory list of akenza. New devices will be created, updates will be reflected and deleted devices will also be deleted on akenza.

If a device gets created or updated in akenza, and is linked to integration, these changes will also be reflected on the platform of the connectivity provider. Deleting devices will be reflected as well. Therefore no double-handling on the integration account is required.

By adding an Integration, an appropriate device connector will be created simultaneously. This new Device Connector can be used in Data Flows to receive and process data from IoT devices in akenza.

Data Routes

Data Routes reflect the data output of the connectivity provider platform. This can either be akenza or any other third-party provider. Depending on the connectivity provider, Data routes can be created and managed through akenza.

In order to create a new Data Route, the button in the top right corner needs to be clicked. The Integration to create the data route has to be selected, as well as all properties for the data route specified.

Existing data routes can be deleted by selecting the + (plus) icon on the Integration list and clicking the delete action in the appropriate data route entry.

It is not possible to create Data Routes or synchronize Devices or Sim Cards using out-of-the-box connectivities. Their Device Connectors however can be used in Data Flows which allows creating Devices and receiving and processing their data in akenza.

Deleting an Organization which contains Assets managed through CaaS will also be irreversibly deleted on the connectivity provider platform.

Device Connectors

When creating an integration, a device connector will be created. It can be used to receive and process data from your IoT assets in akenza.

Integrations