Fleet device management

Availability and inventory

Fleet management requires an administrator to deploy migration 037 and explicitly enable the server, UI and worker. Existing individual-device workflows remain available before activation. The inventory uses 50 devices per server page; search by name, device UUID, Secure V2 wire ID, external identifier or serial number. Activity describes observed reporting, not a continuous UDP connection.

Filter by groups, all selected tags, status or a published schema copied from an authorized device. Active means a packet was observed within three expected reporting intervals, with a five-minute minimum. Historical first-packet evidence survives telemetry retention.

Bulk registration

Choose Add devices, then quantity/numbering, a pasted name list or CSV. Optionally copy an authorized device’s immutable published schema slot, choose groups and tags, and review the preview. Confirming schedules a durable background job; closing your browser does not stop it.

Names may repeat; device UUIDs, wire identities and random credentials remain distinct. External IDs and serial numbers are exact, case-sensitive organization-scoped identities. Free and paid capacity checks use the existing billing system. The preview shows an upper-bound month-end true-up, not a new charge or subscription change.

Groups and tags

Groups are flat and allow multiple memberships. Create or rename groups in Devices; select devices and assign/remove groups in bulk. Deleting a group never deletes its devices. Tags are normalized lowercase labels, separate from historical key/value device tags; at most 20 labels of 48 characters per device.

For Phase 7 routing, use field group_ids with contains and a quoted group UUID, or field labels with contains and a quoted tag. Membership changes affect future committed events only. Existing queued delivery snapshots are preserved. A deleted group stops matching; it does not broaden a routing rule.

Bulk actions and jobs

Select a page or all matching devices (maximum 10,000 per operation). The server freezes the exact IDs and administrative versions at preview; later-created devices are not included. Concurrent changes produce a visible version conflict instead of overwriting newer data.

Update description/metadata, groups/tags, disable, enable, revoke, archive or request manual reprovisioning. Metadata replaces the selected JSON object; this does not remotely configure firmware. Existing schema slots are never overwritten. Bulk reassignment of existing firmware schemas is intentionally unavailable.

Cancel stops uncommitted items; completed changes remain. Download a formula-safe CSV report. Failed eligible items can be reviewed in a new retry preview, which requires confirmation. Preview records expire after 30 minutes; terminal job inputs/results are retained for up to 30 days and at most the latest 50 terminal jobs per workspace, whichever limit is reached first. Audit records remain for up to one year. Download reports before cleanup.

Disable, revoke and archive

Disable temporarily rejects new ingestion and bootstrap; Enable restores only eligible disabled devices. Revoke permanently blocks this device record and invalidates all its Secure V2 credentials. Revoked records cannot be re-enabled or rotated.

Archive is soft deletion: it blocks ingestion and preserves identity, telemetry and delivery history. It does not cascade-delete downstream jobs. Archived records still count under existing billing rules; contact the existing account support path for permanent data deletion questions.