Device statuses (Beta)
Understand the device status values shown in the Devices table.
The Status field reflects a device's overall health by combining three signals: the device's own self-reported state, the health of any Xyte-monitored connection that brings its data into the platform (such as a Connector, Edge collector, or parent device), and any active incidents on the device.
A device reports one of six statuses. When more than one condition applies, the higher-priority status is shown.
| Priority | Status | Meaning |
|---|---|---|
| 1 | Never seen | The device has been created in Xyte but has never sent telemetry, so its state cannot yet be determined. This is typical for devices that have been claimed but not powered on or onboarded. |
| 2 | Disconnected | An Xyte-monitored connection upstream of the device is broken — for example, the Connector, Edge collector, or parent device is offline or in error. The device's own state cannot be observed until the connection is restored. |
| 3 | Error | The device is reachable but is unable to perform its primary function, is at risk of imminent failure, or is actively reporting itself as non-functional. This status is triggered by a critical, high, or moderate incident on the device, or by the device (or its parent) reporting active failure. |
| 4 | Warning | The device is functional but requires attention. Leaving it in this state will negatively affect operational KPIs such as firmware compliance, monitoring coverage, or early RMA detection. This status is triggered by a low or planning incident. |
| 5 | Device offline | The device cannot be reached by Xyte, even though the Connector, Edge collector, or parent device upstream of it is functioning normally. The issue is local to the device. |
| 6 | OK | The device is fully connected to Xyte and operating normally, with no active incidents. |
Disconnected and Device offline both indicate that telemetry is not currently flowing, but they point to different root causes. Disconnected means the path between Xyte and the device is broken upstream — investigate the Connector, Edge collector, or parent device first. Device offline means the path is healthy but the device itself is unreachable — investigate power, network, or the device hardware.
How a device goes offline and comes back online
How Xyte learns that a device went offline, or came back, depends on how the device is connected. What happens after that is the same for every device.
By connection type
| Connection | How Xyte marks it offline | How Xyte marks it back online |
|---|---|---|
| Edge | For most models, the Edge checks the device every 60 seconds. When the device stops answering for longer than its model's offline detection time, Xyte marks it offline. | On the Edge's next successful check. For most models that's within about a minute of the device being reachable again. |
| Direct (the device reports to Xyte itself) | When the device stops reporting for longer than its model's offline detection time. | As soon as the device sends its next report. How often it reports is set by the device. |
| Cloud Connector | The device's status comes from the manufacturer's cloud. Xyte picks it up on the Connector's next sync, and how often a Connector syncs depends on the Connector. A few Connectors also receive status changes from the manufacturer as they happen. | The same way, when the manufacturer's cloud reports the device online again. |
For how a specific Cloud Connector maps the manufacturer's status and how often it syncs, see that Connector's page under Cloud Connectors.
For Edge and Direct devices, offline detection time is set per device model, so a short gap in reporting doesn't open an incident.
If a device is removed from the manufacturer's cloud, Xyte doesn't mark it offline. It's removed from Xyte after a while instead.
If the Edge or Cloud Connector itself stops working, its devices show as Disconnected instead of Device offline, and no offline incident is opened for them. See the statuses above.
For every device
- There's no waiting period on the way back. As soon as Xyte learns the device is online again, its incident closes and the "resolved" notification is sent. The device's status in the Devices table can take up to another minute to refresh.
- The space's notification delay applies only to the "opened" notification. It's set per space and covers every device in it. See Space settings.
- The "resolved" notification is never delayed. If the device comes back online before the delay ends, the incident closes and no notifications are sent.
Related
- A device that keeps dropping and recovering is grouped into one incident. See Incident flapping consolidation.
- When several devices in a room go offline together, Xyte opens one room incident. See Room incident consolidation.
Device statuses also drive the status of the Room containing them. See Room Statuses for details on how Room status is calculated.
Updated 19 days ago