Extended control for Samsung
Samsung displays can offer two different things under Extended control, and a display may have one, both, or neither. They come from different places and have different requirements.
scripts👑 Pro Device Plan or higherExtended ControlextendedControl👑 Pro Device Plan or higherDeploy recommended configuration (Tizen)
This runs on the display through the Samsung B2B API and applies the settings signageOS recommends for a production screen. The card lists every setting and the value it writes before you run anything.
| Setting | Value | Why |
|---|---|---|
| Auto power on | On | After a power cut, the display comes back on by itself. |
| Energy saving mode | Off | The picture keeps its brightness instead of being dimmed to save power. |
| Maximum power saving | Off | Stops the display powering itself down. Models without the option skip this. |
| Eco sensor | Off | The picture does not change brightness with the room. Panels without a light sensor skip this. |
| Button lock | Off | The buttons on the display stay usable for on-site technicians. |
| Network standby | On | The network stays reachable while the display is off, which is what makes remote wake and monitoring work. |
| No-signal power off | Off | A momentary loss of signal no longer switches the display off. |
Select Deploy configuration, confirm, and each setting reports back on its own as Applied, Failed with the display's error message, or Skipped where the model has no support for an optional setting. The card header summarises the last run, for example 7 of 7 applied. The full log stays available under Details, and the run is recorded in the device's script history.
Deploying the configuration also turns on auto source switching with HDMI1 as the primary source. It runs as a separate script as soon as the deploy is sent, and its result shows on the Auto source switching card.
Requirements: a Samsung Tizen device that supports Custom Scripts, the scripts feature entitlement, the device online, and a user with permission to execute Custom Scripts.
Auto source switching (Tizen)
Auto source switching lets the display fall back to signageOS when an external input loses its signal. You pick the primary source, an HDMI input, and the display shows it while it carries a signal. When that signal disappears, the display switches to the secondary source: the signageOS app.
| Field | Meaning |
|---|---|
| Auto source switching state | enable turns auto source switching on, disable turns it off. |
| Primary source | HDMI1 to HDMI4. It must be an input the display actually has, so a single-HDMI panel rejects HDMI2. Only used when enabling. |
| Secondary source | Always URL Launcher / Custom App, where the signageOS app runs. It is shown for reference and cannot be changed. |
Once the display has fallen back to signageOS, it stays there. It does not switch back to the primary source when that input carries a signal again.
Select Set auto source switching and confirm. The card header shows whether the display accepted the change, and the collapsed row shows what was set, for example On · HDMI1. When the display refuses, the run is marked Failed and Last run shows the display's reason, for example that it has no such input.
The current setting cannot be read back from the display. Box shows the result of the last run made from Box, so a change made with the physical remote will not appear here.
Requirements: a Samsung Tizen 4 or newer device that supports Custom Scripts, with MDC (network control) enabled on the display; the scripts feature entitlement; the device online; and a user with permission to execute Custom Scripts.
Samsung extended management
Devices connected to the Samsung RM server are marked with the Extended Control label and gain direct control of the display hardware:
- Power — turn the display on and off, including waking it from standby.
- Input source — switch the display between the signageOS Core App and another input such as HDMI or DisplayPort.
- VNC — open a remote desktop session on the display.
Because of the Samsung RM server API, these actions typically take around 60 seconds to complete. That is normal and not a sign that the action failed.
Requirements: the extendedControl feature entitlement, and a device set up against the Samsung RM server. Setting that up is covered in How to allow Extended Control on Tizen via RM Server.