Conditions View

Conditions allow you to make controls (buttons, sliders, rotaries etc.), scheduler routing entries, and routing entries conditional on one or many factors. For example, you may use conditions to ensure that a scene is enabled only on weekdays, or only on weekends; or to prevent a redirect Instructions within a scene that, when the scene is executed, cause another scene to be executed after or instead of the scene, or cause a range of scenes to be enabled/disabled. from happening while the room affected by it is locked (if you have an appropriate input unit connected). You can also interlink Instructions within a scene that, when the scene is executed, cause another scene to be executed after or instead of the scene, or cause a range of scenes to be enabled/disabled, but only after a defined delay. conditions to meet the requirements of multipurpose environments (such as a conference hall), or to meet security requirements.

A condition comprises one or more terms, and may contain up to 32 terms. A term A component of a Condition, a Term is an expression that may be TRUE or FALSE. A Condition may contain several Terms which, when assessed using Boolean Operators, determine whether the Condition is TRUE or FALSE. is a single statement that, at any given time, may be TRUE or FALSE. For example, a term may specify a day of the week, such as Monday. On Monday, this term is TRUE, but on all other days it is FALSE.

You can view, create, edit and delete conditions via the Conditions view.

Related Topics

• Boolean Logic and Conditions

• Create a Condition or Term

• View or Edit a Condition or Term

• Delete a Condition or Term

• Scenes

• Scheduler

• Routing Entries

• Subdevice Configuration