ScreenlyOS 26.9.0 | Screenly

ScreenlyOS 26.9.0: Players support a new screenshot command

Fri, 09 Oct 2026 00:00:00 +0000

Remote device management is about doing from the dashboard what used to take someone standing at the screen. A player takes commands from Screenly, like reboot and power off, and ScreenlyOS 26.9.0 adds a new one: take a screenshot.

A player that gets the command captures what it’s showing at that moment and sends it straight back. Until now, the only screenshot to look at was the one sent with the player’s regular report, about every 15 minutes, so checking whether a change reached the lobby screen could mean a quarter-hour wait.

The dashboard sends the command from the “Take screenshot” button on a screen’s Overview, which arrived in Screenly 26.10.6. It works on players running ScreenlyOS 26.9.0 or newer.

ScreenlyOS 26.9.0: An Edge App with nothing to show can skip its turn

Fri, 09 Oct 2026 00:00:00 +0000

An earthquake map on a quiet day, a flight tracker with no planes overhead, a meeting room app between bookings: some apps have nothing worth showing some of the time. Until now, they still took their slot in the playlist, and the screen showed an empty app for its whole duration.

An Edge App can now tell the player it has nothing to show. The player skips it and moves on to the next item in the playlist, so the screen keeps showing something useful. The app gets its turn again the next time the playlist comes round, and can decide again then.

An app can only skip before it appears. Once it’s on screen, it plays for its full duration.

For developers

Call screenly.signalAbort() from your Edge App while it’s loading. If the app hasn’t been shown yet, the player cancels it and starts the next item. A call after the app is on screen is ignored. A skip isn’t counted as a failed play.

ScreenlyOS 26.9.0: Screen metrics are served over HTTPS

Fri, 09 Oct 2026 00:00:00 +0000

Some customers have Prometheus metrics turned on for their players, so their own monitoring can track CPU, memory, disk, and network use across a fleet. From ScreenlyOS 26.9.0, a player serves those metrics over HTTPS on port 9100, and identifies itself with its own device certificate. Your monitoring system can check it’s talking to the player it expects.

Metrics collection is off unless it was turned on for your players, so most customers have nothing to change.

If this affects you: a monitoring system that collects metrics from players over plain HTTP stops getting data once a player updates to 26.9.0. Change the scrape target to https on the same port, verify the certificate against the Screenly certificate authority, and set the expected server name to the player’s hostname (the srly- name). Our support team can send you the Screenly CA certificate.

For developers

For a Prometheus scrape job, that means scheme: https with a tls_config whose ca_file points at the Screenly CA certificate and whose server_name is the player’s hostname. The port stays 9100, and the metrics themselves are unchanged.

ScreenlyOS 26.9.0: Players keep Bluetooth off and report its state

Fri, 09 Oct 2026 00:00:00 +0000

Nothing on a Screenly player uses Bluetooth, so from ScreenlyOS 26.9.0, players switch it off when they start. That covers a Raspberry Pi’s built-in Bluetooth and a USB Bluetooth adapter plugged in later. Wi-Fi isn’t affected.

Each player also reports whether its Bluetooth is on or off. The dashboard doesn’t show it yet.

ScreenlyOS 26.9.0: Removed screens get a new PIN to pair again, and other fixes

Fri, 09 Oct 2026 00:00:00 +0000

Fixes

A screen that had been removed from its workspace could sit on the pairing screen with no PIN. It now gets a new PIN, so you can pair it again.
An x86 player with a TPM now recovers on its own from a TPM fault that used to disrupt its connection to Screenly until it was restarted.

Improvements

A Scala player running ScreenlyOS reports itself as a Scala Player, with the serial number from its hardware.
Dependencies and system libraries updated.