The Fleet section lists every screen your organization has claimed: what it is assigned, when it last checked in, and whether it has caught up with what it was last told.
Reading a screen’s status
Each screen checks in about every 20 seconds. Its status answers two different questions:
- Is it reachable? When a screen misses check-ins for long enough it is marked offline. Screens ride out short network blips without you noticing — they keep playing from their local copy — so an offline mark means the dongle has genuinely lost power or network.
- Is it current? “Up to date” means the screen reports it is actually displaying the content you last assigned — not that the server sent it. A screen that is downloading a new playlist shows as catching up until the swap happens.
Screenshots
From a screen’s page, request a screenshot. The dongle captures what it is rendering and sends it back — the console shows you the wall as it really is. This is the tool for “did the new menu make it up?” and for settling whether a screen problem is content or hardware.
Commands
A screen answers a small set of commands from its detail page:
- Screenshot — capture what the panel is showing now.
- Re-fetch content — make the screen re-download what it should be showing. A repair tool for the rare case a device holds wrong bytes; it is not needed for ordinary publishing, which reaches screens on their own check-in.
- Reboot — restart the dongle. Admin only.
Commands are delivered on the screen’s next check-in and their outcome is reported back, so you can see whether a screen actually acted on one. A command an offline screen never picks up expires rather than lying in wait.
When a screen goes dark
Check power and network first — the dongle recovers from both on its own the moment they return, and the screen catches up on everything it missed in one check-in. If the TV is on and the network is fine but the screen stays offline, contact support.