Skip to content

Devices view

Devices appear in two places: a summary card on the project page, and a full Devices page reached from that card or from the breadcrumb trail. Each device has its own detail page.

The devices page

The full list shows every device, 50 to a page, and can be filtered by:

  • device id (search)
  • active or inactive
  • release channel
  • device group
  • how long since it was last seen (1, 7 or 30 days)

The card on the project page

The card shows the five most recently seen devices, with the active count in its heading and a Showing 5 of 213 ยท View all footer. It lists per device:

  • the device_id it reports, linking to its detail page
  • its current_build_number
  • whether it is active or inactive

To act on a device, open it. There are no bulk actions: changing many devices at once is an API job.

Add device pre-provisions one manually and issues its per-device token, which is what a factory flashing rig wants. Most fleets never use it, because a device registers itself the first time it calls /check/.

Device detail

Opening a device shows the compatibility profile it reports (framework, chip family, board id, hardware revision, partition profile, NVS schema version, security mode), what it is running, and when it was last seen.

The controls are:

Control Effect
Save membership Move the device to a release channel, and set its device groups.
Deactivate Stop offering it updates. It stops counting against your plan's device cap.
Revoke Revoke its per-device token.

Deactivating does not delete the device or its history, and it can be reactivated later. Reactivating takes a plan slot, so it is refused when you are already at your device cap. Both actions are recorded in the project's audit log.

Querying a fleet programmatically

GET /api/v1/projects/{id}/devices/ returns every device with its full compatibility profile and takes an active query parameter. That is the fastest way to work out why a device is not being offered a build: compare its profile against the artifact's manifest, which you can read on the artifact's page.