Connect a Device

Create a data flow, add your first device, and confirm that its data arrives in akenza.

Connecting a device to akenza requires a data flow, which describes how data is authenticated, decoded, and stored, and a device, which represents the hardware itself and points at that data flow.

You create the data flow first. It is reusable, so every further device of the same model can point at the same data flow without you configuring anything twice.

If you do not have a physical device at hand, you can use the Device Simulator and complete this guide exactly as written.

1

Create a data flow

Select Create Data Flow on the Data Flow menu tab. A data flow is assembled from three parts, which you configure in order.

2

Choose a device connector

The device connector holds the information on how a device communicates with akenza, and defines the secret used to authenticate its data.

Direct connectivity

• LoRaWAN

• HTTP

• MQTT

• CoAP

• NB-IoT

• mioty

Cloud-to-cloud connectors, for devices that already live in a vendor platform:

• Disruptive Technologies

• VergeSense

• Spaceti

• Haltian

Selecting a device connector

If you already run a LoRaWAN network through a provider such as Swisscom, Loriot, Actility, or The Things Network, set up a connectivity integration instead. The device connector is then created for you, and the provider platform is configured to forward data to akenza.

3

Choose a device type

The device type extracts, transforms, and normalizes the data sent by the device. akenza provides an extensive device type library with more than 300 ready-to-use device types from manufacturers around the globe, maintained openly on GitHub.

If no suitable device type exists, create a custom device type and write your own decoder. Select Passthrough if no parsing is required at all, in which case the payload is forwarded unchanged.

Selecting a device type

4

Choose one or more output connectors

Output connectors define where the decoded data goes. You can add several to one data flow.

Databases

• akenza DB

• InfluxDB

• SQL databases

• Snowflake

Streaming

• Webhook

• Azure IoT Hub

• AWS Kinesis

• Google Cloud Pub/Sub

• Apache Kafka

Notifications

• E-Mail

• SMS

• Microsoft Teams

• Slack

Selecting output connectors

Add the akenza DB output connector unless you have a reason not to. It is what stores the data passing through this data flow, and therefore what makes it available to dashboards, rules, the API, and Genio. A data flow that only forwards data elsewhere keeps no history in akenza.

5

Create a device

Select Create Device in the Asset Inventory.

The Asset Inventory

Add a device name and, optionally, a description, a tag, or a custom field. Naming and tagging consistently from the start pays off once the fleet grows, because tags drive filtering, dashboard data sources, and rule inputs. Select Next.

Basic device information

Choose the data flow you just created and set an offline timeout, which is how long akenza waits without an uplink before flagging the device as offline. Pick a value that suits the device's sending interval. Select Next.

Assigning the data flow

6

Fill in the connectivity parameters

What is required here depends on the device connector you chose:

• LoRaWAN: the device identifiers and keys from your network provider. See LoRaWAN.

• HTTP and MQTT: an alphanumeric secret between 8 and 64 characters.

Connectivity parameters

Finish with Create device.

7

Confirm that data arrives

Select your device from the Asset Inventory and open the device detail page. Once the device sends its first uplink you see the last message time, the decoded values, and, depending on the connectivity, signal quality and battery level.

The device detail page

Congratulations, you have connected your first device.

If no data arrives

Work down the pipeline in the same order the data travels:

1. Is the device sending? Check the device itself, and for LoRaWAN check that the uplink is visible on the network provider's platform.

2. Is akenza receiving it? The Data Processing Logs show what reached the platform and what happened to it, including authentication failures and decoder errors.

3. Is the payload decoded? A mismatch between the device type and the actual device is the most common cause of an uplink that arrives but produces no readable values. Verify the device type, or test your decoder in Scripting.

4. Is it stored? Without the akenza DB output connector, data passes through without being kept.

Still stuck? Reach out through the In-App Chat Support or the Service Desk.

What to do next

Add the rest of your fleet

Import devices from a CSV file instead of creating them one by one.

Deploy on site

Use the Device Setup Assistant to configure devices by scanning a QR code.

React to your data

Set up rules to trigger notifications, downlinks, or aggregations.

Visualize it

Build a dashboard from the data your device is now sending.