Knowledge Base

The Scene task is used to set a group of values at the same time.

Scenes are commonly used when several devices or values need to be changed together with one command. A typical example is a lighting scene, where multiple lights are set to predefined states, brightness levels, or colors for a specific occasion.

Common scene examples include:

• Party scene — sets selected lights to a specific mood or color

• All ON — turns on multiple lights or devices

• All OFF — turns off selected lights or the entire area

• Movie scene — dims lights and closes blinds

• Away scene — turns off lights, lowers heating, and activates security-related functions

• Morning scene — opens blinds, adjusts lights, and sets room temperature

Each scene can contain multiple values from the configuration, such as lights, blinds, HVAC setpoints, variables, modes, or other controllable devices.

Scenes can be triggered from the bOS Client visualization, schedules, buttons, automation logic, or other tasks. This makes them useful for creating simple one-touch control for different room modes, user preferences, or building states.

Table of contents

Scene Settings

Scene name defines the name of the scene displayed on the UI control. It can be changed in the user interface by setting the Allow Rename setting. Allow Rename setting is set by selecting the scene in the theme and use the additional settings display on the right side.

Delay setting can be used to execute the scene with a delay between each device. It can be used as a filter for scenes which are turning ON a lot of inductive loads, which can cause an overload on the bus.

The scenes can also automatically be triggered by the use of Trigger function. Any node in the configuration can be used to trigger the scene and control the devices.

Settings List contains the devices controlled by the scene. Each device has the enabled check box for temporary excluding the device in the scene. Users can also change the value of multiple devices by clicking and dragging over the devices that are the same type. We can simply drag and drop the devices from our configurator to the scene and control them.

Scene can be executed from other tasks by calling the Run function. Learn function can also be called to learn the scene (i.e. store the states of devices on the list).

Visualization Settings

The clients can easily run a scene by simply running it in the bOS Client app. The client can also at any time change how the scene works and which devices are controlled and not.

Scenes can also be edited directly from the bOS Client app, depending on the project configuration.

To open the scene settings, users can either click the wheel icon on the scene control or press and hold the scene button.

Once the scene is opened, users can adjust the scene behavior without using bOS Configurator. They can:

• Select or deselect devices included in the scene

• Define whether selected devices should turn ON or OFF

• Learn the current status of the connected devices

• Rename the scene

• Add or change the scene image

• Adjust the scene according to their preferred room or building behavior

This allows end users to personalize scenes directly from the visualization. For example, they can update a lighting scene based on the current room setup, add or remove devices, or change how the scene behaves for different occasions.

Detailed explanation of all scenessettings is also available in the video below: