Rules - Revision history

Tbezstarosta: /* COOLDOWN functionality */

2026-07-13T13:28:31Z

‎COOLDOWN functionality

2026-07-13T13:28:05Z

‎COOLDOWN functionality

2026-07-13T13:27:07Z

2026-07-13T13:26:44Z

‎COOLDOWN functionality

2026-07-13T13:26:09Z

‎COOLDOWN functionality

2026-07-13T13:25:43Z

‎COOLDOWN functionality

2026-07-13T13:24:20Z

‎COOLDOWN functionality

2026-07-13T13:22:38Z

‎COOLDOWN functionality

2026-07-13T13:22:02Z

‎COOLDOWN functionality

2026-07-13T13:20:02Z

‎COOLDOWN functionality

← Older revision		Revision as of 13:28, 13 July 2026
Line 48:		Line 48:

	*<code>"cooldown"</code> This is the basic cooldown condition which comes into effect whenever the rule activates (the conditions turn from `false` to `true`) and the actions block gets evaluated. This then pauses the evaluation of the rule for the specified time.		*<code>"cooldown"</code> This is the basic cooldown condition which comes into effect whenever the rule activates (the conditions turn from `false` to `true`) and the actions block gets evaluated. This then pauses the evaluation of the rule for the specified time.
−

	"conditions":{		"conditions":{

@@ Line 62: / Line 62: @@
-*<code>"falseCooldown"</code> - This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from `true` to `false`.
+*<code>"falseCooldown"</code> - This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from "true" to "false".
-* <code>"allCooldown"</code> - This combines the functionality of the other cooldown conditions. It also pauses the evaluation of the rule, but triggers whenever the rule state changes from either `true` to `false` or the other way around from 'false' to 'true'
+* <code>"allCooldown"</code> - This combines the functionality of the other cooldown conditions. It also pauses the evaluation of the rule, but triggers whenever the rule state changes from either `true` to `false` or the other way around from "false" to "true"
 == ACTION ==

@@ Line 42: / Line 42: @@
 * <code>"SCHEDULE/TestSchedule/ACTIVE": true</code> = <code>TestSchedule</code> is active
 * <code>"OUTPUTS/1/STATE":"on"</code> = Output 1 is ON
 == COOLDOWN functionality ==

← Older revision		Revision as of 13:26, 13 July 2026
Line 59:		Line 59:

	In this example rule whenever the output 1 turns on both outputs 2 and 3 get their state toggled. Then for 30 seconds no amount of changes in the states of output 1 the states of outputs 2 and 3 remains unchanged. After the 30 seconds elapse the rule still needs the triggering condition to happen again, therefore there needs to be an event where output 1 goes from being turned off to being in the "on" state.		In this example rule whenever the output 1 turns on both outputs 2 and 3 get their state toggled. Then for 30 seconds no amount of changes in the states of output 1 the states of outputs 2 and 3 remains unchanged. After the 30 seconds elapse the rule still needs the triggering condition to happen again, therefore there needs to be an event where output 1 goes from being turned off to being in the "on" state.
		+

	*<code>"falseCooldown"</code> - This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from `true` to `false`.		*<code>"falseCooldown"</code> - This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from `true` to `false`.

@@ Line 48: / Line 48: @@
 *<code>"cooldown"</code> This is the basic cooldown condition which comes into effect whenever the rule activates (the conditions turn from `false` to `true`) and the actions block gets evaluated. This then pauses the evaluation of the rule for the specified time.
-<code>
    "conditions":{
      "OUTPUTS/1/STATE":"on",
@@ Line 58: / Line 57: @@
      "OUTPUTS/3/ACTION":4
+   }
-#In this example rule whenever the output 1 turns on both outputs 2 and 3 get their state toggled. Then for 30 seconds no amount of changes in the states of output 1 the states of outputs 2 and 3 remains unchanged. After the 30 seconds elapse the rule still needs the triggering condition to happen again, therefore there needs to be an event where output 1 goes from being turned off to being in the "on" state.
+In this example rule whenever the output 1 turns on both outputs 2 and 3 get their state toggled. Then for 30 seconds no amount of changes in the states of output 1 the states of outputs 2 and 3 remains unchanged. After the 30 seconds elapse the rule still needs the triggering condition to happen again, therefore there needs to be an event where output 1 goes from being turned off to being in the "on" state.
 *<code>"falseCooldown"</code> - This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from `true` to `false`.

@@ Line 49: / Line 49: @@
 The cooldown period doesn't activate while the rule is already in a cooldown period, there needs to be a new cooldown triggering event happening after the cooldown period is over.
-# "cooldown"
+*<code>"cooldown"<code>
 This is the basic cooldown condition which comes into effect whenever the rule activates (the conditions turn from `false` to `true`) and the actions block gets evaluated. This then pauses the evaluation of the rule for the specified time.
@@ Line 66: / Line 66: @@
 In this example rule whenever the output 1 turns on both outputs 2 and 3 get their state toggled. Then for 30 seconds no amount of changes in the states of output 1 the states of outputs 2 and 3 remains unchanged. After the 30 seconds elapse the rule still needs the triggering condition to happen again, therefore there needs to be an event where output 1 goes from being turned off to being in the "on" state.
-# "falseCooldown"
+*<code>"falseCooldown"<code>
 This cooldown condition works in the same way as the base `cooldown` condition, but the cooldown period triggers when the rule state goes from `true` to `false`.
-# "allCooldown"
+* <code>"allCooldown"<code>
 This combines the functionality of the other cooldown conditions. It also pauses the evaluation of the rule, but triggers whenever the rule state changes from either `true` to `false` or the other way around from 'false' to 'true'