Mestra Player
Updates and reliability
Mestra Player is built so a fault is repaired without a blank screen, and so anything it can’t repair is said in plain words to the right person.
Updates
Mestra signs every release of the player. A screen installs only what Mestra signed and checks it before installing. The server chooses which signed release a screen is offered and when. It can’t make a screen run anything Mestra didn’t sign.
Mestra rolls a release out in stages: first the screens that have Early updates on, then more screens, then everyone. A rollout moves on only while screens stay healthy, and pauses itself if too many fail their trial.
Early updates
An owner can put a screen on the early track. Open the screen’s page, Updates, and switch on Early updates. The screen then takes a new version before the others.
When a screen updates
A screen applies an update outside booked play.
- A stopped screen updates at once.
- Otherwise it updates when the screen is off, if it has hours.
- Otherwise it updates in the time an owner chose. Under Updates, enter Update time, from and to, then Save time.
- With no hours, or hours that never leave a stretch off, and no chosen time, it updates at 3 am the screen’s own time (between 3:00 and 4:00). The zone is the site’s, found from the site’s location if the site has none set, else the screen’s, else your organisation’s. The screen goes dark for a minute or two while it updates.
- An owner can select Apply now on a waiting update.
A screen that updates at 3 am shows Updates at 3:00 am Sydney time (its own zone) under Updates. To use another time, select Choose another time, enter Update time, from and to, then Save time. An update that has arrived and is waiting for its time shows Update ready, with an Apply now button. A security update shows Security update ready.
Pause updates
Under Settings > Updates, an owner can switch on Pause updates. Screens keep their current version, and security updates wait too. A screen with a security update waiting shows Security update waiting with “Updates are paused”, and Mestra sends a screen.update_waiting webhook. Switch it off to let screens update.
If an update fails
Each PC must prove itself healthy after an update, within a trial. If it can’t, it goes back to its last working version by itself. The screen shows Rolled back or Update failed, with the reason, and the rollout pauses. A screen that runs on the Evergreen web runtime and not the one in the release shows Runtime not pinned.
Self-healing
The player watches itself: its page, the display, its content, the clock, the disk and its own health. It also notices early signs of trouble, such as low disk space or heat, and raises them before they become outages.
When something goes wrong it repairs it by itself, starting with the gentlest fix, and it avoids a blank screen where it can. A fault you can see is fixed at once. A fault you can’t see waits for a quiet time. If it can’t fix a fault, it stops and tells a person.
A screen’s What it did section lists the repairs it made and whether they worked.
The backup player
A separate backup player covers the screen while the main player is down or restarting. It keeps showing the booked stills and video from the same checked files, so the screen doesn’t go blank. HTML5 items are skipped while it covers. Plays it shows are recorded as shown by the backup player, and count as up time.
The screen’s page tells you if the backup player isn’t ready.
Who is told
Every fault has a plain-words cause, a plain-words fix and a who:
- It fixes itself.
- You, the owner.
- Your installer.
- Mestra.
A fault the player couldn’t fix, or that needs a person, shows on the screen’s page and on the Screens list as Needs a look or Needs a visit. A fault it fixed shows as Online, fixed itself. Mestra also sends these webhook events, if you have an endpoint: screen.issue (with a severity of info, warn or down) and screen.recovered, plus screen.online, screen.offline and screen.update_waiting. See Webhooks.
When an install key needs attention, Mestra sends an install_key.alert webhook, and emails owners if the key was made with Email owners if this key is tried after it ends ticked. The key’s row also shows Joining too fast or Reported exposed.
See the Privacy Policy for what Mestra holds about your screens.
Uptime
Each screen’s page and the Sites page show uptime over 30 days. See Proof of play for what counts.