ScreenlyOS 26.5.1 | Screenly

ScreenlyOS 26.5.1: Edge Apps can read their encrypted settings from injected JavaScript

Fri, 29 May 2026 00:00:00 +0000

An Edge App that points at a remote page and injects JavaScript into it can now read its own encrypted settings from that script, as screenly_settings.<key>. The player decrypts the values when the page loads and passes them to your script.

Use it wherever a script on a remote page needs a secret to do its job: an internal dashboard that needs an API key, an order screen calling a kitchen system, or a logistics board pulling from an API that authenticates every request. Store the key as an encrypted setting of the Edge App and read it from screenly_settings instead of writing it into the script.

ScreenlyOS 26.5.1: Players can show web pages that require a client certificate

Fri, 29 May 2026 00:00:00 +0000

Some internal systems never go near the open web: a plant’s process dashboard, an internal operations board, anything an organization has put behind mutual TLS. Until now, a player couldn’t load those pages.

Now you can show them directly. Turn on “Allow sending client certificate” in a web page’s settings, and the player presents its own device certificate when it loads the page. The server can then decide whether to talk to that player, the same way it decides for any other client it trusts.

On Screenly Player Max and other x86 players, the certificate is held in the device’s secure hardware.

ScreenlyOS 26.5.1: Players report which hardware they run on

Fri, 29 May 2026 00:00:00 +0000

Players report the model and revision of the hardware they run on, so the dashboard can show which player a screen is.
Dependencies and system libraries updated.