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

Rules

Tbezstarosta — Tue, 11 Aug 2026 07:37:44 GMT

‎A representative deployment:

Tbezstarosta — Tue, 11 Aug 2026 07:36:03 GMT

New page

Tbezstarosta — Tue, 11 Aug 2026 07:34:48 GMT

Tbezstarosta — Tue, 11 Aug 2026 07:34:20 GMT

‎A representative deployment:

Tbezstarosta — Tue, 11 Aug 2026 07:12:36 GMT

New page

Tbezstarosta — Tue, 11 Aug 2026 07:02:21 GMT

‎A representative deployment:

← Older revision		Revision as of 07:37, 11 August 2026
(2 intermediate revisions by the same user not shown)
Line 50:		Line 50:
	Controlled device (e.g. an AV matrix switcher) drives a GPIO output that is wired through a relay into a NETIO PDU digital input (DI). Immediately after the device reboots, the GPIO can briefly assert a spurious/undefined signal before settling — this transient is picked up by the relay and closes the contact on the NETIO DI, satisfying the Rule condition.		Controlled device (e.g. an AV matrix switcher) drives a GPIO output that is wired through a relay into a NETIO PDU digital input (DI). Immediately after the device reboots, the GPIO can briefly assert a spurious/undefined signal before settling — this transient is picked up by the relay and closes the contact on the NETIO DI, satisfying the Rule condition.

−	~~Schedule name~~: ~~'''CR07_SCHEDULE'''~~	+
		+	[[File:NETIO Cooldown Diagram 50pct.png \|NETIO Cooldown Diagram ]]

@@ Line 49: / Line 49: @@
 === A representative deployment: ===
 Controlled device (e.g. an AV matrix switcher) drives a GPIO output that is wired through a relay into a NETIO PDU digital input (DI). Immediately after the device reboots, the GPIO can briefly assert a spurious/undefined signal before settling — this transient is picked up by the relay and closes the contact on the NETIO DI, satisfying the Rule condition.
 Without a cooldown condition, the Rule fires on every such transition:

@@ Line 46: / Line 46: @@
 == 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.