Concepts

Infuse-IoT Cloud resources are scoped to an organisation and linked to the active Infuse platform organisation used in the console.

Organisation

An organisation is the ownership and access boundary. It controls members, roles, credentials, marketplace activity, and product resources. For IoT workflows, the platform organisation can be linked to an Infuse-IoT Cloud organisation. The console uses that linked organisation when it lists IoT boards, networks, devices, applications, releases, and tokens.

Board

A board is a hardware or product profile. It usually represents a board family, product family, or device type that shares a SoC and metadata model.

Boards are used to:

• group compatible devices,
• support device search and filtering,
• constrain application release compatibility,
• define metadata fields operators should capture on devices.

Board metadata fields can be marked required or unique. Required fields must be present when editing device metadata in the console. Unique fields represent identifiers that should not be reused across devices of the same board, such as serial number or asset tag.

Network

A network represents a device connectivity domain. Networks have:

• a display name,
• an optional description,
• a numeric network ID,
• a 32-byte base64 network key.

Use networks when devices, gateways, or deployments need a shared connectivity boundary. If your product does not separate devices by network, keep network setup minimal and document the internal convention your backend uses.

Device

A device is the registered physical or logical unit. A device record includes:

• internal record ID,
• Infuse deviceId,
• MCU ID,
• board ID,
• organisation ID,
• metadata,
• latest state where available.

Use the Infuse deviceId for device-specific workflows such as commands, marketplace installs, KV updates, telemetry context, and downstream data joins.

Device State

Device state is the latest operational view known by Infuse-IoT Cloud. It can include last seen time, status, application ID, application version, and algorithm versions. State is useful for support, operations, command routing decisions, and data processing context.

KV Entries

KV entries are device-side configuration or state values. They may be displayed as decoded values when KV definitions are available, or as raw base64 payloads when no definition is available. Updates are queued so the device can apply them when it is reachable.

Logger State

Logger state tracks per-logger sync progress. It shows the latest reported and downloaded blocks and whether download is enabled. Use it to understand whether logged device data is progressing through the sync workflow.

Applications And Releases

Applications represent device-side applications known to Infuse IoT. Releases represent installable versions with board compatibility and file metadata. Device application state reports what the device is running, and application updates queue a release to be delivered to a device.

Commands

Commands are sent as RPC messages. An RPC records the target device, command payload, delivery state, response payload, and any downlink message context. Use commands for device actions, diagnostics, and supported firmware operations.

Definitions

Definitions are versioned schemas for device data and commands:

• RPC definitions describe commands and payloads,
• TDF definitions describe structured telemetry,
• KV definitions describe device key-value entries.

Definitions let backends and the console decode values consistently instead of hard-coding payload interpretation.