Chapter 8.1 – Automation (Actions) in the DOMIQ System Configurator

Automation is a fundamental feature and the heart of a smart building. Its role is to make the automation system more autonomous – the system will automatically remember to carry out repetitive tasks, or decide how to behave based on the rules programmed into it.
This chapter is divided into four subsections.

1. Actions – An interface element used to define a list of tasks to be carried out by the Base module. This element is used in both events and timers, which is why it’s described before the actual descriptions of those two tabs.
   
2. Events – Logical rules that are triggered when a specific action is called within the system, or in response to a change in the state of a device/variable (identifier). Logical rules can be configured so that they’re only executed under certain conditions. They give you complete freedom to configure the actions that will be carried out in response to an event occurring.
   
3. Timers – Let you trigger rules that run automatically at a specified time (schedules). They make it very easy to automate repetitive tasks, e.g. at a specific hour, on a chosen day of the week or month.
   
4. Logic – The most advanced form of automation. It requires knowledge of the Lua scripting language. It gives the programmer complete freedom to create their own automation scripts, taking into account events occurring in the system, the state of identifiers, and time-based dependencies. However, the use of Lua scripts is a very advanced feature, and the vast majority of functionality in the DOMIQ system can be configured without using scripts. Scripts can also be used for integration with external software.
   

1. Actions #

The Actions window is a universal configuration interface element used to define the actions to be carried out by the Base module. You’ll find Actions in the Events, Timers, and Remote tabs (in the Page and Button controls).
The window has a table layout, which lets you change the order of rows. The order in the table matters – actions are carried out in order, from top to bottom.

1. Active – uncheck to deactivate the selected action. An inactive action has a struck-through label.
2. Test – A button that lets you test whether the configuration is correct. If the system doesn’t encounter a problem, the action will be executed. Actions that involve binding identifiers are not executed.
   To edit an action, click its label in the table.
   To delete an action, select it, then click Delete.
   Three types of actions are available:
3. + LCN
4. + VAR
5. + Command

+ LCN
This window is used to define a command that will be sent onto the LCN bus. The left part of the window contains the command’s recipient settings:

• Description (optional) – If this field is filled in, its content will be displayed as the command’s label in the Actions table.
• Segment – The number of the segment the command is directed to.
• The Module/Group selection field determines the type of the command’s recipient. If Module is selected, the command will be sent to a specific LCN module; its ID should be entered in the Module field. If Group is selected instead, the command is sent to the group of LCN modules specified in the Group field.
• Select from list – Clicking this displays a list of LCN modules available in the installation, letting you select the module that is to receive the command.
• Confirmation – If this option is checked, the Base module will receive confirmation from the LCN bus that the recipient has received the command. This field is checked by default.
  The right part of the window is used to select the command type and its parameters.

1.1. Output #

A command for controlling a dimmable output.

1. Output – Select the number of the output you want to control.
2. Value – The percentage value the output is to be set to.
3. Ramp – That is, the ramp-up time with which the output will be driven.

1.2. Relays #

A command for controlling relays. It contains an interface for selecting the value to be sent to the individual relays.

1.3. Motors #

Controlling blind motors using relays. Lets you control from 1 to 4 blinds, either with positioning (an option with current monitoring – requires the LCN-BS4 module) or without positioning. The checkboxes numbered 1 to 4 represent pairs of relays. 1 corresponds to relays No. 1 and 2, 2 to relays 3 and 4, and so on. Options 1+2 and 3+4 are used to control pairs of motors. The 1-4 option, meanwhile, controls all 8 relays.

1.4. Send Keys #

Sends a command simulating a press of any key(s) from the selected table(s), with any action.

1.5. Lock Keys #

A command that lets you lock selected keys from a given table.

1.6. Scene #

A command that lets you trigger or save a scene.

1. Operation:
   • Load: Loads the selected scene.
   • Save: Saves the scene. The settings and the numbers of the outputs active at the moment the command is sent will be saved to the scene’s settings.
2. Scene number: The number of the scene to load/save. Range: 1 to 10.
3. Active outputs: The number of the output(s) to be loaded/saved in the scene. Available options: Output 1, Output 2, Output 3, Output 4.
4. Use time from scene definition: If this option is checked, the outputs will be driven using the ramp programmed in the scene’s definition. Otherwise, you can set your own ramp in the Time field.
   

1.7. Register #

A command for switching the scene register. Range of change: 0 to 9.

+ VAR

A command for setting a value in a VAR-type virtual variable. VAR variables are stored in the Base module’s memory until it is restarted.

1. Description (optional) – If this field is filled in, its content will be displayed as the command’s label in the Actions table.
2. Name – Enter the variable’s name here. It will be available in the Base module’s state under the identifier VAR.<nazwa>. For example, if the name is test, it will appear in the state as VAR.test.
3. Value – The value to be assigned to the variable.
4. Remember – Converts the VAR-type variable into a MEM-type variable. The value of MEM variables is retained even after the Base module loses power. In that case, the variable is available in the state under the identifier MEM.<nazwa>.

+ Command

Lets you send a value to any identifier in the DOMIQ system (including VAR variables and LCN modules). This is a very powerful feature in the DOMIQ system, since it lets you execute any command or trigger any event.

1. Description (optional) – If this field is filled in, its content will be displayed as the command’s label in the Actions table.
2. Name – Enter the name of the identifier you want to send the value to here.
   IMPORTANT! Note that using a prefix is required!
   If you use the C. prefix, the action represents executing a command. For example, turning on a relay.
   If you use the E. prefix, the action will broadcast an event within the system, which the Base module can react to according to the events that have been programmed.
3. Binary – Check this field if you’re sending raw binary data.
   

Study the examples below:

1. Toggling relay No. 3 in the LCN module with ID 10.
   Name: C.LCN.relay.0.10.3
   Value: toggle
2. Moving blind No. 2 up, controlled via the DOMIQ/Expander module and Satel INT-IORS at address 1.
   Name: C.EXP.shutter.1.2
   Value: up
3. Broadcasting an event to switch the visualization screen in the Remote app.
   For the purposes of this example, let’s assume the screen is named test. When this action is executed, every Remote app currently displaying the visualization will show the screen named test.
   Name: E.DISPLAY.screen
   Value: test