A screen that is not playing is worth nothing. It generates no impression, no revenue, no renewal. And it goes dark more often than operators expect — usually without anyone noticing, because the person who sees the venue every day is the store manager, and for them “the TV is on” is already enough.
This is the checklist we use.
The four states of a screen
Before you monitor anything, separate what “not playing” actually means. These are four different problems, with four different owners:
| State | Symptom | Typical cause |
|---|---|---|
| Dark | Black screen | Power, HDMI, outlet unplugged by cleaning staff |
| Offline | Plays old content | Venue Wi-Fi dropped or the password changed |
| Empty | Player running, nothing scheduled | Campaign ended and nobody replaced it |
| Stuck | Frozen on one frame | Player hung, disk full |
Only the first is obvious from the outside. The other three look normal to anyone walking by — and they are most of the cases.
What to monitor
Heartbeat, not ping. Knowing the device is on the network says nothing. The useful signal is the player saying “I am playing item X from playlist Y right now.” Without that, a screen frozen for two days looks perfectly healthy.
Proof of play, not a download log. Downloaded the file is not the same as displayed the file. The gap shows up exactly in the cases that matter — a codec the device cannot handle, not enough memory, a file corrupted mid-way.
Schedule end with lead time. The useful alert is “this screen runs out of content in 3 days,” not “this screen has no content.” The second one is already the loss.
Disk space. A player that cannot download the next campaign will keep playing the previous one, quietly, indefinitely.
What not to monitor
Resist alerting on everything. An alert channel that fires twenty times a day is a channel nobody reads — and the one time it mattered was buried in the other nineteen.
Things that create noise without signal:
- Short network drops. A well-built player has a local cache and rides through that without stopping. Alert on prolonged absence, not the first lost packet.
- A reboot by itself. A store screen reboots with the breaker. What matters is whether it started playing again.
- Temperature or CPU swings with no correlation to stalled playback.
The weekly routine
Fifteen minutes, once a week, fixes almost everything:
- List screens with playback in the last 7 days. Anything missing from that list is a conversation, not an alert.
- Check schedules that expire in the next 14 days.
- Look at screens by player version — older versions concentrate freezes.
- Call a random venue and ask what is on screen. It is the only test that catches placement, brightness, and angle problems — things no telemetry sees.
The most common mistake
It is not technical. It is assuming the network is fine because nobody complained.
The store manager does not complain about a dark screen — they do not always know something specific was supposed to be playing. The advertiser does not complain because they are not there. When the complaint arrives, it is usually at contract renewal, and by then it is late.