Automation scenarios

This article is about automation in the Wattsense console.

 

Introduction

This feature allows you to create automation scenarios (define setpoints based on several factors), via an intuitive interface. Available for Tower and Bridge, it allows you to create simple instruction chains with triggers that initiate actions.

Here are two examples that can be implemented with this module:

 

If occupancy detectors indicate that an office is unoccupied, then set temperature setpoints.

Implementation of Heating systems regulated both according to time programming and also according to office presence.

In the example above, (in the THEN block), it is also possible to change a property setpoint value rather than a schedule slot. The only condition is that the property is controlled by the schedule.

 

Description of an automation scenario

The scenario is built with instructions blocks and operands :

• The conditions can be based on the value of a property and/or on current slot type defined by a schedule.
• The temporization waits for the conditions to repeat themselves. It is based on two parameters : the number of times the conditions should be met and the period during which it should happen. Example: wait for the conditions to repeat twice for 30 minutes.
• And finally, when the conditions are met, actions are triggered. An action can be an assignment of new properties setpoints, or the replacement of the current slot in the schedule.

 

How to create an automation scenario in the Console ?

Go to the Program Tab / Automations, click on the Add an automation button

 

 

IF BLOCK (Add a Condition)

You can add conditions as part of the IF block. The conditions can be:

• A value of a property:

Only one property can be selected on this page. You can specify the condition under which the property value must be satisfied using a formula using the following operators: (Is equal to; Is not equal to; Is greater than; Is greater than or equal to; Is less than; Is less than or equal to). You can also view the recent values ​​of the selected property.

You can add multiple conditions in the IF block. In this case, choose the operand between the conditions:

• All the conditions below are met ("and")
• At least one condition below is met ("or")

• A schedule slot:

If a schedule is selected in the IF BLOCK, then the same schedule can be the target of the scenario. 

Select the schedule and then the slot type.

 

DURING BLOCK (Define temporization)

 

You can add a temporization so that the scenario waits for the conditions to repeat themselves.

The temporization is based on two parameters: the number of times the conditions must be met and the duration for which they must occur. Example: wait for the conditions to repeat twice within 30 minutes.
When a condition is met, an occurrence counter starts at 1. Each time the condition is met again, the counter is incremented by 1.
If the conditions are not met, the counter is decremented by 1. It will never drop below 0.
The counter has a lifetime, defined by the user.
If the counter reaches the user-defined threshold before the end of the period, the scenario executes the action.
Otherwise, the counter returns to 0.

Example: The timer requires 3 occurrences within 30 minutes with a property value of 1 :

 

THEN BLOCK (Add an action)

You can list the actions that trigger if the conditions are met in the THEN block. The actions can target :

• Properties

Click on the send value button and then click on the properties you want to target :

The same value will be sent to all the selected properties. To write a different value per property, create multiple actions.

 

If a schedule, not selected in the IF block, already controls a property you have chosen, you cannot select this property. In fact, our product encourages the use of schedules to meet 80% of use cases. The remaining cases can be handled using scenarios.

• Schedule

If a schedule has been selected in the IF block, then the same schedule can be the target of the scenario. You can select the slot type the schedule should apply.

 

You can’t select a schedule that has not been selected in the IF block

 

IF NO LONGER MET BLOCK

You can set things to go back to normal in the IF NO LONGER MET block. It is referred to “return to normal”.
The return-to-normal scenario is the ELSE/ELSE IF counterpart scenario with its IF, THEN and DURING blocks.
However, the return-to-normal twin scenario would run only if the original scenario was executed (and its actions triggered).
The IF block of the return-to-normal scenario reuses the same conditions as the original scenario. You can't edit the conditions.

 

Automation example

In the following example, we have three rooms with heating actuators. The temperatures in the rooms are controlled by a scheduler (20°C if the room is occupied, 15°C otherwise). As a presence detector is available is the room B, we can add a scenario : if no presence detected in room B then set temperature to 14°C. This rule will override the default schedule behaviour.

If the scenario had said, “IF no presence is detected in Room B, THEN change the schedule to “unoccupied””, then Rooms A and C  would have been impacted, which is not the desired behaviour in this case.

If you need any additional information, please contact us here.