# Health and diagnostics


> The Details tab turns a device report into a ranked list of problems, each with what caused it and what to do. What it checks and what the thresholds are.
The **Details** tab on a ScreenlyOS screen is the device's own report, read for you. Rather than a wall of numbers, it gives a verdict, then a list of problems ordered worst first, each with the measurement behind it and the thing to do about it.

## The verdict

| Headline | Meaning |
| --- | --- |
| No issues detected | Every check in the last report came back clean |
| Working, with notes | Something to know about, nothing to fix |
| Degraded | At least one warning |
| Needs attention | At least one critical problem |
| Nothing reported yet | The screen has not sent a report |

Under it is a line naming what still works, because a list of warnings should not read as a dead screen. Content already on the player keeps playing while you work through them.

## What it checks

**Power.** The Raspberry Pi firmware raises an under-voltage flag when the supply dips, and it stays latched after the event. Brownouts crash playback and are the most common cause of a corrupted card, so this is treated as serious even when it has recovered. The fix is nearly always the supply: use the official one, and take the player off extension leads and unpowered hubs.

**Cooling.** Warns above 70 °C and calls it overheating above 80 °C. The firmware drops clock speeds to protect the board, which the audience sees as stuttering video. Clear the vents and move the player out of direct sun.

**Storage.** Warns below 3 GB free and turns critical below 1 GB, which is the point where the player starts deleting cached files that are not in the current playlist to make room. On a Raspberry Pi it also watches the SD card's own error counters and its read-only flag: a card that has gone read-only does not come back and needs replacing. On a Player Max it reads the drive's SMART data and warns at 80 percent of rated endurance.

**Memory.** Warns above 90 percent in use, where the kernel starts killing processes and the viewer can restart mid-item. Heavy web content in a playlist is the usual cause.

**Connectivity.** Four checks: can it reach its gateway, our API, the hosts your content is downloaded from, and a time server. A gateway failure is reported on its own with the rest listed underneath, since one broken route explains all of them. Wi-Fi signal below 40 percent is flagged separately, because downloads stall and restart at that level and large files may never finish.

**Clock.** A failing time check means schedules run against a drifting clock, so content appears at the wrong time. See [Configure time servers](/docs/screenlyos/networking/guides/configure-time-servers/).

**Security.** Notes when a player is authenticating with its shared secret rather than a client certificate. It still works; it is the weaker of the two paths.

**Reporting.** A report older than 45 minutes is flagged, because everything else on the page comes from that report and may no longer describe the player.

## What else is on the tab

Alongside the issues are the raw cards they come from: Resources, Network, Network checks, SD card or Disk, Security, and Player. That is where you find a screen's IP and **MAC address**, its Wi-Fi signal and frequency, its hardware model and serial number, its ScreenlyOS version, its local time, and its [Tailscale](/docs/integrations/network/private-network-access/) state if it is on your private network.

## Reading it well

Symptoms are folded into whatever explains them. A failing power supply that is also causing CPU throttling reads as one power problem, not three unrelated ones, and the throttling is listed underneath as a consequence.

So work from the top. The first item is usually the cause of several of the ones below it.