Devices and activity

Identity and credentials

The dashboard UUID identifies the device record; the Secure V2 wire ID is the numeric identity in packets. The root secret authenticates and encrypts packets; the one-time bootstrap token initializes sequence reservation through HTTPS. Neither a UUID nor wire ID is a secret. Never share the root secret, token or private starter ZIP.

Rotate secrets from Schema when a credential is exposed or counter state is lost. Rotation issues a new wire ID and offers an explicit old-credential grace period. Immediate revocation stops that prior credential; this is not a universal device-disable switch. Deleting a device is destructive and requires confirmation.

Activity is not connectivity

Active describes recent observed device activity, not a live connection. Current Secure V2 last-seen updates follow committed telemetry; historical last-seen values may also reflect authenticated connections and are not sufficient proof to complete onboarding. Inactive means a device with prior activity has exceeded three configured reporting intervals, with a minimum five-minute window. Without an expected interval the threshold is five minutes. Never connected means no durable last-seen or committed-reading evidence is available. If only historical committed-reading evidence remains without a last-seen timestamp, the status is conservatively Inactive.

Set the expected reporting interval in the device setup guide. This is a status-display expectation, not a command that changes firmware. A batch sample interval describes spacing between readings, not how frequently a device transmits. Retention deletes telemetry history but does not erase last_seen or the first-reading milestone.

More devices

Use the search to match names, identifiers, tags or activity status. Open device is the main card action; setup appears for a new sender, and secondary actions are under More actions. The fleet-management guide covers Secure V2 bulk registration, groups, tags and manufacturing manifests when fleet management is enabled. Historical fleet-profile tooling remains compatibility-only.