Skip to Content
Devices & connectivityDevices and I/O

Devices and I/O

Device identity

Each device has a name, a serial number and a device profile. The serial number identifies the device and must be unique; the profile describes its type. Open a device from the device list to view its details.

Inputs and outputs

Inputs represent readings coming from a device. Outputs represent channels for commands or control.

An input name should match the field sent by the device. A display label makes that name easier to recognise in dashboards and widgets.

The overview’s circular I/O panel shows all configured channels — blue for readings, orange for actions. Hover or focus a channel to inspect it; click it or press Enter to keep its details visible.

Selecting a channel in the I/O panel does not send a command. To send one, use the Downlinks tab.

Connection status

The overview shows whether the device is connected, inactive or disconnected. The I/O panel presents these as Online, Degraded or Offline.

Status depends on the connection and on the freshness of received data, not on configuration being saved correctly. A device that reports infrequently needs an appropriate data interval — otherwise it will be judged stale and shown as offline between its normal reports.

Set the data interval to match how often the device actually reports. Leaving it at a short default for a device that reports every few minutes is the most common cause of a device that flickers between online and offline.

Using the details tabs

TabWhat it is for
OverviewIdentity, connection settings and the I/O map
MessagesInspect the raw messages received from the device
DownlinksConfigure and run commands
ConfigurationUpdate connection settings
Device InfoInspect reported device information
OTAInspect reported firmware information

Available actions depend on your permissions.

The Messages tab is the first place to look when something is wrong. It answers one question cleanly: did the platform receive anything at all? That splits every connectivity problem into a device-side half and a platform-side half.