From 481ddd8ec6b9ed7163943f83165653d6790cc4dd Mon Sep 17 00:00:00 2001 From: Michael Ingraham <34340210+meingraham@users.noreply.github.com> Date: Mon, 8 Jul 2019 16:48:25 -0400 Subject: [PATCH] Http#Initialized & System#Save --- Rules.md | 36 +++++++++++++++++++----------------- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/Rules.md b/Rules.md index b635a76c..22741329 100644 --- a/Rules.md +++ b/Rules.md @@ -76,30 +76,32 @@ Some of available triggers: Trigger | When it occurs | ------------------|-------------| -System#Boot | occurs once after MQTT is initialized. Due to the command execution order it cannot occur earlier than that. +Analog#A0div10 | when the `A0` input changes by more than 1% it provides a value between 0 and 100 +Button2#State | when a button changes state:
`0` = OFF
`1` = ON
`2` = TOGGLE
`3` = HOLD +Clock#Timer=3 | when global `Timer3` is activated +Dimmer#Boot | occurs after Tasmota starts +Dimmer#State | when the value for Dimmer is changed +Event#User | when command `Event User` is executed. You can define your own event values and trigger them with the `Event`](commands#event) command. +Mem#State | when the value for Mem\ is changed +Http#Initialized Mqtt#Connected | when MQTT is connected Mqtt#Disconnected | when MQTT is disconnected -Wifi#Connected | when Wi-Fi is connected -Wifi#Disconnected | when Wi-Fi is disconnected +Power1#Boot | after Tasmota starts +Power1#State | when a power output is changed
use `Power1#state=0` and `Power1#state=1` for comparison, not =off or =on
Power2 for Relay2, etc. +Rules#Timer=1 | when countdown `RuleTimer1` expires +Switch1#Boot | occurs after Tasmota starts +Switch1#State | when a switch changes state:
`0` = OFF
`1` = ON
`2` = TOGGLE
`3` = HOLD
(`SwitchTopic 0` must be set for this to trigger) +System#Boot | occurs once after MQTT is initialized. Due to the command execution order it cannot occur earlier than that. +System#Save | executed just before a planned restart Time#Initialized | once when NTP is initialized and time is in sync Time#Initialized>120 | once, 120 seconds after NTP is initialized and time is in sync -Time#Set | every hour when NTP makes time in sync Time#Minute | every minute -Time#Minute==241 | every day once at 04:01 (241 minutes after midnight) Time#Minute\|5 | every five minutes -Clock#Timer=3 | when global `Timer3` is activated -Rules#Timer=1 | when countdown `RuleTimer1` expires -Event#User | when command `Event User` is executed. You can define your own event values and trigger them with the `Event`](commands#event) command. -Power1#State | when a power output is changed
use `Power1#state=0` and `Power1#state=1` for comparison, not =off or =on
Power2 for Relay2, etc. -Power1#Boot | after Tasmota starts -Button2#State | when a button changes state:
`0` = OFF
`1` = ON
`2` = TOGGLE
`3` = HOLD -Switch1#State | when a switch changes state:
`0` = OFF
`1` = ON
`2` = TOGGLE
`3` = HOLD
(`SwitchTopic 0` must be set for this to trigger) -Switch1#Boot | occurs after Tasmota starts -Dimmer#State | when the value for Dimmer is changed -Dimmer#Boot | occurs after Tasmota starts -Analog#A0div10 | when the `A0` input changes by more than 1% it provides a value between 0 and 100 +Time#Minute==241 | every day once at 04:01 (241 minutes after midnight) +Time#Set | every hour when NTP makes time in sync Var#State | when the value for Var\ is changed -Mem#State | when the value for Mem\ is changed +Wifi#Connected | when Wi-Fi is connected +Wifi#Disconnected | when Wi-Fi is disconnected Connected sensors can be a trigger in the form as they are represented in the `TelePeriod` or `Status 8` JSON message.