Screenly players and other clients communicating with our device API could get an error depending on a minor formatting difference in how they called it. Both forms are now accepted consistently.

Playlists with a lot of items, or with several apps in them, could take a long time to build, and occasionally timed out altogether in workspaces with a lot of playlist items or app installations. Building a playlist is now faster, so changes reach your screens reliably even in large workspaces.

Fixes

• Reassigning which label a playlist “Plays On” used to trigger a duplicate sync, briefly reloading affected screens twice in a row. It now sends just one.

Improvements

• Applied security updates to third-party dependencies across several of our services.

You can now turn any workspace member, new or existing, into a temporary member with an Active until date. Their access ends automatically on that date, and disabling or re-enabling a member is purely an access switch, their screens, playlists, and content stay exactly where they are.

Downgrading a subscription’s member limit now also uses this: instead of silently leaving a workspace over its limit, it automatically disables the right number of excess seats and notifies the workspace, rather than requiring someone to sort it out manually.

Improvements

• Adding a new screen now opens as a quick pop-up over the Screens page instead of navigating to a separate page.

Some uploaded videos played back as a slideshow-like stutter, as low as 0.7 frames per second, specifically on Raspberry Pi 4 based Screenly Players. The Pi4’s hardware video decoder was rejecting these videos over missing color information and falling back to a much slower software decoder. Affected videos are now corrected automatically during processing, so newly uploaded videos play back smoothly.

Improvements

• Dashboard blog feed thumbnails no longer look stretched or distorted.
• Corrected a capitalization inconsistency (“Websocket” to “WebSocket”) in the screen details panel.

The network configuration tool used to live inside the dashboard, so setting up Wi-Fi or a static IP for a player meant being signed in. It’s now a standalone tool at screenly.io/os/network-config-generator, no account required.

This matters for anyone installing a player who isn’t the person managing the Screenly workspace: a contractor, a technician, or an installer on-site can now generate the config file themselves instead of stopping mid-installation to ask someone with a Screenly account to send one over. The tool also runs entirely in your browser: the file is assembled locally and never sent to our servers, so anything like Wi-Fi passwords never leaves your machine.

Slack and PagerDuty were previously the two integrations you connected individually, each team member linking their own account. Every other integration was already shared at the workspace level, so this was the inconsistent case, not the norm.

Both are now connected once per workspace, consistent with everything else under Workspace Settings > Integrations.

If this affects you: if your workspace had more than one person individually connected to Slack or PagerDuty, only one workspace-wide connection remains active after this change. Check Workspace Settings > Integrations and reconnect if needed.

Improvements

• The screen overview page now automatically detects your exact Screenly Player Max model (Mk1, Mk2, or Mk3) and shows the matching device image, instead of a generic one.

The screen detail page (Screens > a screen) has been redesigned with a clearer tab structure: Overview, Details, Settings, Now Playing, and Actions. The same device health, signal strength, location, HDMI settings, and playlist information is all still there, just better organized than the single long page it replaces.

Improvements

• The sign-in page no longer depends on a live network fetch to render, and we made a security improvement to the page along the way. No visible change to how it looks.
• Applied security updates to third-party dependencies across several of our services.

API change

The CA certificate download endpoint now returns the certificate as JSON ({"certificate": ...}) instead of a downloadable file, and a missing CA now returns a proper 404. If you have an integration that downloads this certificate directly, you’ll need to update it to parse the new response format.