Condition Block ​

Condition block gives you an ability to perform different actions based on the result of a condition check.

In case the condition evaluates to True the automation continues with the path from the Green checkmark. In case the condition evaluates to False the the automation continues with the path from the Red X mark.

Table of contents

Checking multiple conditions ​

You can specify multiple conditions in the Condition block. A combination of AND and OR conditions is possible.

For example you can check that the time is between certain hours OR that the device state is set to a certain vale and proceed to the Green checkmark path if either of them is true. Or you can specify that both of them must be true for the automation to continue to the Green checkmark path.

This makes it simple to perform more complex conditions within the same Condition block.

Available condition types ​

List of available condition types:

• Time - check if the time is as desired (before, after, between, specific day).
• Astronomical - condition based on sunrise and sunset, as well as day/night.
• Device state - check if the state of the device is as desired.
• Value of a previous block - check if value of a previous block is as expected. In example below the trigger was a brightness sensor and we check if the value of Lux is greater than 100.
• Advanced - create custom complex conditions, use math, formulas, ....

Using data from the system ​

In the Condition block you can reference data available in your system or from the previous steps in this automation.

Possible data:

• System time - you can select hour, minute, day, month, year, weekday and more
• Any state of your devices - for example you can check whether a brightness of a light sensor (in Lux) is greater than a certain number
• Results from previous steps in automation - for example a value of the trigger or a result of a certain action

Handling errors ​

In some cases during the Condition an error can occur.

This can happen if the device you are using in condition to verify it's state is offline or if you have entered an invalid calculation.

You can decide what to do in case the error occurs. Here are the possible options:

For example if something goes wrong you can abort the whole automation (you will see a failed status in the Run History) or Handle the condition in a separate branch as shown below (this will be useful to send a notification for certain critical automations).

You can select to handle any issues in a separate branch. See orange alert branch above.

Advanced conditions ​

Within each condition's left or right side you can use advanced data transformation, maths and more.

Check the Transform data guide guide to learn more.