ScreenlyOS 26.2.0 | Screenly

ScreenlyOS 26.2.0: Players can join 802.1X enterprise networks, wired or Wi-Fi

Wed, 13 May 2026 00:00:00 +0000

On most corporate networks, every device has to identify itself before a port or an access point lets it in. Until now the network settings on a player couldn’t answer that question.

A player now authenticates with 802.1X PEAP, giving an identity and a password like any laptop on the same network.

On Wi-Fi

Press F2 to open the Wi-Fi settings and pick the network. A network that authenticates its clients asks for an identity and a password instead of a passphrase. For a network that doesn’t broadcast its name, type it in under “Other Network” and choose 802.1X PEAP as the security.

On ethernet

Press F5 for the new wired network settings, and set “Authentication” to 802.1X PEAP. The same screen takes a static IP address, with its subnet mask, gateway, and DNS server, for a site that assigns addresses by hand instead of over DHCP.

For a batch of players going to the same site, a network.yaml on a USB drive applies the same settings without anyone standing at a screen with a keyboard.

An open or passphrase network over DHCP is still the default, and it’s still what most players use. The rest is for the factory floor and the hospital, where every port and every access point authenticates before it passes traffic.

ScreenlyOS 26.2.0: Players can join your Tailscale network

Wed, 13 May 2026 00:00:00 +0000

Some of what you’d want on a screen was never going to be on the open internet: an operations dashboard on an internal server, a page on the intranet, the API for your app. A screen can show those now.

Connect Tailscale to your workspace in the dashboard and turn it on for your screens, and your players join your tailnet, stay on it, and report whether they’re connected, which you see on a screen’s Details tab. Once a player is on your tailnet, it reaches your internal web pages and APIs the way any other machine of yours does, and nothing has to be published to get them onto a wall.

Tailscale is only for web resources. Videos, images, and other files still go to screens through the Screenly dashboard, and so does managing players, the same as for every other screen.

All of it happens from the dashboard. There’s no key to type in on the screen and nothing to set up on the player, so you connect a whole fleet from where you already are.

When you replace the key, players pick up the new one and reconnect on their own.

ScreenlyOS 26.2.0: Raspberry Pi 4 players run at 1080p on a 4K display

Wed, 13 May 2026 00:00:00 +0000

Video plays smoothly on a Raspberry Pi 4 connected to a 4K display. Until now the player would try to run at 4K, which is more than that board can handle, so video stuttered and the player looked slow when the real problem was a resolution too big for it.

These players now run at the highest resolution the display offers up to 1080p, at the fastest refresh rate available at that resolution, with nothing to set on the device.

This covers the Raspberry Pi 4 Model B, the Pi 400, and the Compute Module 4, which share the same graphics chip. Raspberry Pi 5 and x86 players, such as Screenly Player Max, keep running at 4K.

If this affects you: a Raspberry Pi 4 on a 4K display drops to 1080p when it takes this release. There’s nothing to change on your side.

ScreenlyOS 26.2.0: Improvements to how players connect to Screenly

Wed, 13 May 2026 00:00:00 +0000

Improvements to how players connect to Screenly.
Dependencies and system libraries updated.