Screenly 26.10.3: Improvements to managing a screen's labels

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

Managing a screen’s labels is easier now. They have a Labels tab of their own on the screen page, instead of a section on its Settings tab.

The tab shows the screen’s labels in a table, with how many screens and playlists use each one, so you can see how far a label reaches before you change it. Search and sorting make a long list easy to get around, and you add and remove labels right from the table, all in 1 place.

Screenly 26.10.3: Screen reports on the API include hardware and software health

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

Screen reports on API v4.1 (GET /v4.1/screens/reports) now return much more of what a player reports about itself. From your own tools, you can watch a fleet for an SD card or a disk that’s starting to fail, keep an eye on temperatures, or check which model and software a player runs, without opening each screen in the dashboard.

Storage:

sd_card_health: errors on a Raspberry Pi’s SD card, and whether the card has turned read-only.
smart_disk_data: a S.M.A.R.T. summary of the SSD or NVMe drive on an x86 player, including its temperature, power-on hours, and how much of its life is used.
storage_info: the identity of a Raspberry Pi’s SD card: name, manufacturer, and date.
disk_usage: total, used, and free space on the player’s data storage, in bytes.
disk_stats: read and write counters for each disk since the player started.

Hardware:

sensors: temperature and other sensor readings, such as a Raspberry Pi’s chip temperature.
x86_stats: hardware temperatures on Screenly Player and Screenly Player Max.
mem_info: total, free, and available memory, in kB.
raspi_rev and raspi_serial: a Raspberry Pi’s board revision and serial number.

Software and security:

installed_snaps: every software package on the player, with its version.
device_model and validation_sets: the ScreenlyOS image a player runs, and the exact package versions it’s held to.
secure_boot, full_disk_encryption, and mtls_enabled: whether the player uses secure boot, an encrypted data partition, and a client certificate for its connection to Screenly.
is_wayland: whether the player draws through the newer display stack.

Display, network, and running state:

display_data: each connected display’s make, model, size, and supported resolutions.
screen_resolution: the resolution content is shown at.
bluetooth: on, off, or unknown. off also covers a player with no Bluetooth at all.
probe_diagnostics: the results of the player’s own network checks, refreshed about once a day.
player_uptime: seconds since the player’s content started, which restarts once a day.
local_time: the player’s clock when it sent the report.

Fields fill in from each player’s next report, and some apply only to certain hardware: a field a player doesn’t report is empty. These are additions, so existing responses keep every field they had.

Screenly 26.10.3: Power BI reports stay on screen through connection renewals, and other fixes

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

Screens showing a Power BI report no longer show an error in its place when the workspace’s connection to Power BI is due for renewal.
Changing a screen’s name or location now reaches the apps playing on it right away. An app that shows either one used to keep the old value until something else changed for that screen, such as an edit to one of its playlists.

Screenly 26.10.3 | Screenly

Screenly 26.10.3: Improvements to managing a screen's labels

Screenly 26.10.3: Screen reports on the API include hardware and software health

Screenly 26.10.3: Power BI reports stay on screen through connection renewals, and other fixes