(10 intermediate revisions by the same user not shown)

Line 43:

* <code>"OUTPUTS/1/STATE":"on"</code> = Output 1 is ON

* <code>"OUTPUTS/1/STATE":"on"</code> = Output 1 is ON

+

== COOLDOWN functionality ==

+

The "cooldown" family of conditions serve as a way to prevent unwanted repeat triggering of rules which have their conditions met and often changing. This is achieved by pausing rule execution for a specified time after the condition state changes based on the specific cooldown condition used. Only one cooldown condition can be present in a `conditions` block at any time. 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.

+

*<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":{

+

    "OUTPUTS/1/STATE":"on",

+

    "cooldown":30

+

},

+

  "actions":{

+

    "OUTPUTS/2/ACTION":4,

+

    "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.

+

*<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"

== ACTION ==

== ACTION ==

wiki.netio-products.com - Recent changes [en]

Rules

← Older revision		Revision as of 13:28, 13 July 2026
(10 intermediate revisions by the same user not shown)
Line 43:		Line 43:
	* <code>"OUTPUTS/1/STATE":"on"</code> = Output 1 is ON		* <code>"OUTPUTS/1/STATE":"on"</code> = Output 1 is ON

		+
		+	== COOLDOWN functionality ==
		+	The "cooldown" family of conditions serve as a way to prevent unwanted repeat triggering of rules which have their conditions met and often changing. This is achieved by pausing rule execution for a specified time after the condition state changes based on the specific cooldown condition used. Only one cooldown condition can be present in a `conditions` block at any time. 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.
		+
		+	*<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":{
		+	"OUTPUTS/1/STATE":"on",
		+	"cooldown":30
		+	},
		+	"actions":{
		+	"OUTPUTS/2/ACTION":4,
		+	"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.
		+
		+
		+	*<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"

	== ACTION ==		== ACTION ==