Product Updates
Greetings,
This issue's product updates, at a glance:
Samsung Color E-Paper support — battery-powered panels in the same Box as the rest of your fleet
Edge Cache runner for BrightSign — new content crosses the internet once per location
More accurate Content Guard matching — three image fingerprints instead of one, nothing to change
Scripts as tiles, plus Apply again — repeat a run without filling everything in
Coming soon: alert windows in local time — one rule for devices in every timezone
Samsung Color E-Paper support
You can now run signageOS on Samsung Color E-Paper displays (EMDX series, Tizen 8.0, tested on the 32" EM32DX). You set them up in the Samsung E-Paper app and then manage them in Box alongside the rest of your fleet.
What's new:
Applets — run with timings
Monitoring — remote screenshots, battery level and charging status
Screen refresh — on demand from an applet, or at a set daily time
There's no video playback, and brightness, volume, display power, on/off timers, remote reboot, scheduled power actions, orientation change and auto recovery aren't available.
Why it matters: If you add battery-powered E-Paper panels, you manage them from the same Box, with the same applets, as the rest of your fleet.
Set up your Samsung E-Paper display →
Edge Cache runner in the Solution Hub
We've added Edge Cache to the Solution Hub as a runner for BrightSign. One player caches the files your content downloads and serves them to the other players and clients on the same local network.
What's new:
Private content — requests with authorization are forwarded as they are, and private responses aren't stored
Disk budget — stays within a set amount of disk space
Reboots — survives a reboot without downloading everything again
Remote clear — you can clear the cache remotely
Why it matters: If a location has many screens and a slow or metered connection, new content now downloads once instead of once per player.
Set up Edge Cache for your BrightSign players →
More accurate Content Guard matching
Content Guard now compares screenshots with your reference images using three image fingerprints instead of one. It recognizes the expected content more reliably, including on complex, content-rich screens, and there's nothing to change.
Why it matters: If you use Content Guard alerts, they now give you a clearer signal of what's actually on your screens.
Availability: Works on devices with Tizen Core App 2.13.0, webOS Core App 2.12.0, Linux Core App 2.8.0, Windows Core App 3.2.1 or BrightSign Core App 2.6.0 and newer.
See how Content Guard checks your screens →
Scripts as tiles, plus Apply again
On the device detail, the Scripts tab now shows scripts as tiles, laid out like the Settings tab.
What's new:
Run history — a script's editor keeps the version and parameters of every run
Pre-filled runs — the editor fills in the last run, so you change only what you need
Apply again — in Settings → Time, sends the timezone and NTP server shown in Box to the device again
Why it matters: If you run custom scripts or manage device time settings, repeating a run or re-sending the time settings no longer means filling everything in again.
Run a custom script from the device detail →
Coming soon: alert time windows follow each device's local time
In the coming days or weeks, active time windows in alert rules will follow each device's local time instead of UTC. One rule set to Mon–Fri 09:00–17:00 will then cover devices in Prague and New York during their own business hours.
What to know:
Existing rules — converted automatically
Rules without time windows — work as before
Devices without a known timezone — keep using UTC
"% of devices" threshold — counts only devices inside their time window
Why it matters: If your fleet spans several timezones, one rule covers all of it, without converting times to UTC by hand.
