How ReadyView decides a device is offline
What Online and Offline mean, how long ReadyView waits before it marks each kind of device Offline, why it sometimes holds off, and how to read the reason it gives.
ReadyView marks a device Offline when it stops hearing from it. How soon that happens depends on how the device reports, from about two minutes to an hour.
#What the statuses mean
| Status | Meaning |
|---|---|
| Online | ReadyView is hearing from the device. |
| Offline | ReadyView has stopped hearing from the device. |
| Dormant | Offline for 7 days or more, or since an unknown time. |
| Adopted | An offline device someone acknowledged. See Device lists. |
#How ReadyView hears from a device
A device reports in one or both of these ways.
- Live connection. The device keeps a connection open to ReadyView and sends a report every 15 seconds. This is the device's MQTT setting. ReadyView is told when that connection drops, so it notices within about two minutes.
- Check-ins. ReadyView asks the device for its status every few minutes, or the device calls in on a schedule. ReadyView notices a drop only after several check-ins in a row go unanswered.
Which devices use which:
| Device | Live connection | Check-ins |
|---|---|---|
| Switches | Yes, when MQTT is on | Yes |
| ReadyLink clients | Yes, when MQTT is on | Through their switch, which reports the clients connected to it |
| ReadyWall firewalls | Yes | No |
| Access points | No | Yes |
| Smart plugs | No | Yes |
#How long before a device shows Offline
| Device, as ReadyView is hearing it | Shows Offline |
|---|---|
| Switch on a live connection | About 2 minutes after its last report |
| ReadyLink client on a live connection | About 2 minutes after its last report |
| ReadyWall firewall | After 4 minutes of silence |
| Switch that only checks in | After 45 minutes without a check-in |
| ReadyLink client that only its switch reports | After 60 minutes without a report |
| Access point | After 5 minutes |
| Smart plug | After 2 minutes |
A switch or client on a live connection is judged in two ways, and whichever comes first counts.
- Its connection drops. ReadyView waits 90 seconds for the device to reconnect or to be heard some other way, then marks it Offline. Counted from the device's last report, that is about 2 minutes.
- Its connection stays open but the reports stop. ReadyView marks a switch Offline after 4 minutes of silence and a client after 2.
The times for check-in devices are long on purpose. A single missed check-in is common and means nothing, so ReadyView waits until the silence can't be explained by one.
#Why ReadyView waits before marking a device Offline
A device that has gone quiet isn't always down. Before ReadyView marks a device Offline it checks three things.
- Did it come back? After a live connection drops, ReadyView waits 90 seconds and asks a switch for its status once more. A device that reconnects or answers in that time never shows Offline. A device that passes its silence time gets one more minute in the same way.
- Is ReadyView itself behind? If ReadyView still has reports waiting to be read, it reads those first, so a device isn't marked Offline while its report is in the queue.
- Did many devices go quiet together? When a large share of one kind of device goes quiet in the same few minutes, the likely cause is the connection between them and ReadyView, not the devices. ReadyView holds those devices back until reports start again, and marks Offline only the ones that stay silent. The same goes for live connections: when a large share of them drop at the same moment, ReadyView doesn't mark any device Offline for that reason alone.
These checks keep you from being alerted about a device that is fine.
#When a device comes back
A device shows Online again as soon as ReadyView hears from it: within about 15 seconds of reconnecting on a live connection, or at its next check-in otherwise.
A device that restarts is out of contact for about two minutes. A restart is often over before ReadyView marks the device Offline. A slower one shows Offline for a minute or two and then Online again. If you restarted the device from ReadyView, its panel shows Rebooting during that time and the event says so.
#Read why a device went Offline
Each time a device goes Offline, ReadyView records the most specific cause it has evidence for, how serious it is, and what to do next. You see them on the event in View Logs and in the alert.
| Cause | What ReadyView saw | Severity | What to do |
|---|---|---|---|
| Restarted from ReadyView | Someone restarted the device from ReadyView. A configuration restore and a factory reset show their own name. | Info | Nothing. The event says when the device should be back. If it isn't, check its power and uplink. |
| Restarting for a firmware upgrade | A firmware upgrade started in the last 30 minutes. | Info | Nothing. Upgrades usually finish within 10 minutes. |
| Did not come back after a restart | A restart or firmware upgrade that ReadyView started ran past the time the device was due back: 5 minutes after the expected time, or 20 minutes after an upgrade began. ReadyView adds a second event and sends the alert again. | Critical for a switch or firewall, Major for a client or access point, Warning for a smart plug | Check its power, then its uplink. |
| Its switch is offline | The device is a ReadyLink client and its switch is Offline. | Warning | Restore the switch first. The client should come back with it. |
| Its switch no longer sees it | The device is a ReadyLink client that stopped reporting while its switch is Online. | Major | Check the client's power and the coax or phone line between it and the switch. |
| Stopped responding | The device's live connection timed out: the device went silent without closing it. | Critical for a switch, Major for a client | Check its power, then its uplink. |
| Connection cut | The device's live connection ended suddenly, for a reason other than a timeout. | Critical for a switch, Major for a client | If it isn't back in a few minutes, check its uplink. |
| Closed its own connection | The device closed its live connection itself. Devices do this when they restart or shut down. | Major for a switch, Warning for a client | If it isn't back in a few minutes, check it on site. |
| No report for 45 minutes | Nothing was heard from the device for the time shown, which is the device's waiting time from the table above. | Critical for a switch or firewall, Major for a client or access point, Warning for a smart plug | Check its power, cabling, and the site's connection to ReadyView. |
What the severities mean:
- Critical: a switch or firewall is down without warning, and so is everything behind it.
- Major: one client or access point is down without warning.
- Warning: the cause is somewhere else (the device's switch is down), or the device is a smart plug.
- Info: ReadyView started it, so it's expected. If the device doesn't come back in time, the event is replaced by Did not come back after a restart at the severity an unexpected outage would have.
When ReadyView has no evidence, it says only that the device is Offline and to check its power and uplink. A device that went Offline before this was added shows the time only.
When the device comes back, the Online event says how long it was Offline.
The time on the event is when ReadyView marked the device Offline. The device stopped reporting before that: about two minutes on a live connection, and the full waiting time for a device that only checks in. The event's details say when the device was last heard.
To find out what happened around that time, see A device shows Offline or Dormant.
#Offline alerts
ReadyView sends an alert when a device goes Offline and another when it comes back. The Offline alert includes the cause, what to do, and the severity from the table above; the Online alert says how long the device was Offline. Alerts need two switches turned on: Device Offline on the Notifications page, and Email alerts in the site's settings. See Alert notifications.
#Related guides
Last updated November 20, 2026