Devices
Devices are the operational targets for telemetry, state tracking, configuration, commands, application updates, and Infuse-Marketplace installs. A device record binds a physical or logical device to an organisation, board, MCU identifier, Infuse deviceId, and metadata.
Device IDs are also used in Infuse-Marketplace checkout and purchase APIs when a customer buys products for specific devices. Backend services should treat Infuse-IoT Cloud as the source of truth for the deviceId values passed into Infuse-Marketplace and downstream data workflows.
Devices In The Console
Open Infuse IoT > Devices to list and search devices in the linked Infuse IoT organisation.
The device list supports:
| Search mode | Use |
|---|---|
| List | Browse the organisation device list. |
| Infuse ID | Search by the internal device record ID. |
| Device ID | Search by the 16-character Infuse device ID. |
| SoC and MCU ID | Find a physical device by SoC and MCU identifier. |
| Board metadata | Find devices on a selected board by a board metadata field and value. |
Open a device to inspect identity, board, state, metadata, application state, KV entries, logger state, and recent RPCs.
Device Identity
Infuse-IoT Cloud supports several lookup paths because different systems know different identifiers:
| Identifier | Typical use |
|---|---|
id | Internal UUID-style record identifier used by backend systems. |
deviceId | Device-facing Infuse identifier, represented as a 16-character hex string in RPC workflows. |
mcuId | Hardware MCU identifier reported by the device. |
| SoC and MCU ID | Hardware lookup when discovering or reconciling a physical device. |
boardId | Links the device to a board profile. |
organisationId | Scopes the device to the owning organisation. |
metadata | Product-specific fields such as serial number, customer assignment, deployment site, or hardware variant. |
Device Details
Device details are organised into tabs:
| Tab | Use |
|---|---|
| Applications | View the reported application state, release metadata, queued updates, and update history. Schedule or cancel application updates when permitted. |
| KV Store | Inspect decoded or raw KV entries, queue updates, view update history, and cancel pending updates. |
| Logger Sync | Review logger download state such as reported/downloaded blocks and timestamps. |
| Metadata | Edit device metadata using board-defined fields where available. |
| RPCs | Dispatch a command to the device and review recent RPCs. |
Marketplace purchase, entitlement, compatibility, and install flows remain in the Marketplace area.
Metadata
Metadata is the editable product context attached to a device. Use it for fields such as serial number, asset ID, customer assignment, deployment site, hardware variant, or commissioning batch.
If the device board defines metadata fields, the console shows those fields while editing metadata. Required fields must be present. Unique fields indicate values that should identify a device within that board family.
For board metadata rules, see Boards.
Device State
Device state is the latest operational view Infuse-IoT Cloud has for a device. It can include:
- last seen time,
- reported status,
- application ID,
- application version,
- algorithm versions.
Use state for support, operations, command decisions, and joining device output to a known registry record.
API Registry Flow
For automated onboarding, the common registry flow is:
- Resolve or create the owning organisation.
- Resolve or create the board profile for the device family.
- Resolve or create a network if your deployment model needs one.
- Create the device with
mcuId,boardId,organisationId, and optional metadata. - Store the returned identifiers in your backend system so downstream workflows use the same device identity.
Last-route lookups are important for downlink workflows. If an RPC is sent immediately, Infuse-IoT Cloud can use the device's last known route. If you choose a wait timeout, Infuse-IoT Cloud can wait for the device to send a packet before sending the RPC.
Useful Endpoints
| Task | Endpoint |
|---|---|
| List or create devices | GET /device, POST /device |
| Read or update by record ID | GET /device/id/{id}, PUT /device/id/{id} |
| Read by device ID | GET /device/deviceId/{deviceId} |
| Read by SoC and MCU ID | GET /device/soc/{soc}/mcuId/{mcuId} |
| Read state by record ID | GET /device/id/{id}/state |
| Read state by device ID | GET /device/deviceId/{deviceId}/state |
| Read last route | GET /device/deviceId/{deviceId}/lastRoute |
| Read routes for many devices | POST /device/lastRoute |
| List devices and state together | GET /device-and-state |
For request schemas and response shapes, see the Infuse-IoT Cloud API reference.