Boards
Boards describe hardware families, product profiles, or device types. A board groups devices that share hardware assumptions such as SoC, metadata fields, and release compatibility.
Use boards to:
- organise devices by hardware or product family,
- filter devices by board and metadata,
- define which metadata fields operators should capture,
- connect application releases to compatible board targets.
Boards In The Console
Open Infuse IoT > Boards to view boards in the linked Infuse IoT organisation.
The board list shows board name, SoC, metadata field count, and update time. Open a board to view its identifiers, owning organisation, and metadata fields.
Create A Board
From Infuse IoT > Boards, select Add board and provide:
| Field | Use |
|---|---|
| Name | Human-readable board or product profile name. |
| Description | Operational context for the board. |
| SoC | System on chip used by devices on this board. |
| Metadata fields | Optional field rules used when editing device metadata. |
Metadata Fields
Board metadata fields describe the product-specific device metadata your team expects to maintain.
Each field has:
| Property | Meaning |
|---|---|
| Field name | Metadata key shown when editing a device. |
| Required | The metadata field must be present when saving device metadata in the console. |
| Unique | The value should identify a device within that board family, such as a serial number or asset tag. |
Good metadata fields are stable, operationally useful, and not overloaded. Prefer fields such as serialNumber, assetId, customer, deploymentSite, hardwareVariant, or commissioningBatch.
API Workflows
Use the API when boards are created from product lifecycle systems or when environments need to be reconciled automatically.
| Task | Endpoint |
|---|---|
| List boards | GET /board |
| Create a board | POST /board |
| Read a board | GET /board/id/{id} |
| List devices for a board | GET /board/id/{id}/devices |
For request schemas and response shapes, see the Infuse-IoT Cloud API reference.