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
  • Device Inventory
  • Device Detail View
  • Connectivity Details
  • Downlink

Was this helpful?

  1. Device Management

Devices

This page describes the Asset Inventory

PreviousUsers (Workspace)NextDevice

Last updated 5 months ago

Was this helpful?

Device Inventory

The Inventory is a collective list of all Devices:

Device Detail View

The Device Detail View displays all information from a selected device.

Connectivity Details

Depending on the LoRa carrier, different connectivity details are displayed within Connectivity Details. All carriers provide LoRa connectivity details per default.

In addition to the default LoRa connectivity details, Swisscom Actility, and generic Actility devices provide additional information such as:

  • Motion Indicator

    • Provides information about the expected movement speed of the sensor. In most cases "Near static" has to be selected.

  • Connectivity Plan

    • Provides information about billing on the Actility carrier.

  • Data Route

    • If the Device was created with the help of a Data Flow, then Data Route is set automatically. The Data Route defines how an uplink is forwarded and who can send a downlink.

  • Boot Profile

    • Contains information about the device model.

Downlink

LoRa downlink

LoRa downlinks require a port and a payload formatted as a hex string. The port has to be zero or positive although most carriers require it to be positive. The payload has to be a hex string. The confirmed toggle allows requesting a confirmation that the downlink was sent. If the device is assigned to a Data Flow with a Device Type that has a downlink script, the payload hex gets replaced with a JSON object. During downlink processing, the JSON object will be translated into the hex string using the downlink script. The downlink script can also override the port and confirmed inputs.

MQTT downlink

MQTT downlinks require a JSON object payload and can add an optional topic. The topic has to start with a / and will be appended to the default downlink topic. The payload can contain any valid JSON and has no further restrictions. If the device is assigned to a Data Flow with a Device Type that has a downlink script, the topic can be overridden by the downlink script.

This functionality can be used to send downlinks manually. Downlinks can also be triggered based on a .

Rule action
Asset Inventory Overview
Asset detail view