Devices

The inventory of all devices in a workspace, and the detail view of a single device.

Devices is the inventory of a workspace. It lists every device with its current state, and it is where you create, import, search for, and open devices.

Device

The device list

The device inventory

Each row shows the state of one device:

Column	What it shows
Name	The device name. Opens the detail view.
CS	Connection state. Shows whether the device has sent data within its offline timeout.
Device ID	The identifier the device sends data with, such as its DevEUI.
Tags	The tags assigned to it, in their colors.
SQI	Signal quality of the last uplink, if the connectivity reports it.
Data Flow	The data flow that processes its uplinks. Opens the data flow.
Last Message Time	When the last uplink arrived. This is the quickest way to check whether a device still sends data.

Custom fields can be added as additional columns.

Above the list are the search field, the filter, and the controls for selecting columns and refreshing the list. Most columns can be sorted.

Adding devices

Create a device

Add one device, assign its data flow, and fill in its connectivity parameters.

Bulk import

Create many devices from a CSV file, and edit, register, or delete devices in bulk.

Device Simulator

Generate uplinks without hardware to build and test a data flow.

Device Setup Assistant

Configure devices on site by scanning a QR code.

The device detail view

The detail view shows everything akenza has recorded about a device: its identifiers, its data flow, its tags and custom fields, the data it has sent, and the uplink metrics of its last message.

The device detail view

Connectivity details

What is shown under Connectivity Details depends on the connectivity, and for LoRaWAN on the carrier. All carriers show the standard LoRaWAN details. Devices on Swisscom Actility and generic Actility networks also show:

Detail	What it is
Motion Indicator	The movement expected of the sensor. In most cases this is Near static.
Connectivity Plan	The plan the device is billed under on the carrier.
Data Route	How an uplink is forwarded and who can send a downlink. It is set automatically if the device is created with a data flow.
Boot Profile	Information about the device model.

Downlinks

Downlinks can be sent manually from the detail view, or triggered by a rule action.

LoRaWAN downlinks require a port and a payload. The port has to be zero or positive, and most carriers require it to be positive. The payload is a hex string. The confirmed toggle requests a confirmation that the downlink was sent.

If the data flow of the device uses a device type with a downlink script, the hex payload is replaced by a JSON object. The script translates it into a hex string during processing, and it can also override the port and the confirmed flag.

MQTT downlinks require a JSON object as the payload and can have an optional topic. The topic has to start with / and is appended to the default downlink topic. The payload can be any valid JSON. A downlink script in the device type can override the topic.