From abda2b0e7388a2ef92c7720b87062a578addc769 Mon Sep 17 00:00:00 2001 From: Michael Ingraham <34340210+meingraham@users.noreply.github.com> Date: Wed, 25 Sep 2019 10:35:47 -0400 Subject: [PATCH] Anchors --- Rules.md | 65 ++++++++++++++++++++++++++++---------------------------- 1 file changed, 33 insertions(+), 32 deletions(-) diff --git a/Rules.md b/Rules.md index e2408160..9b9818bd 100644 --- a/Rules.md +++ b/Rules.md @@ -65,34 +65,35 @@ Comparison operators: Some of available triggers: -Trigger | When it occurs | -------------------|----------------| -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#eventName | when command `Event eventName` 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 -Power1#Boot | `Relay1` state before Wi-Fi and MQTT are connected and before Time sync but after `PowerOnState` is executed. Power#Boot triggers before System#Boot.
This trigger's value will be the last state of `Relay1` if [`PowerOnState`](Commands#poweronstate) is set to its default value (`3`). -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#Minute | every minute -Time#Minute\|5 | every five minutes -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 -Wifi#Connected | when Wi-Fi is connected -Wifi#Disconnected | when Wi-Fi is disconnected +Trigger|When it occurs +:-|:- +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#eventName|when command `Event eventName` 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 +Power1#Boot|`Relay1` state before Wi-Fi and MQTT are connected and before Time sync but after `PowerOnState` is executed. Power#Boot triggers before System#Boot.
This trigger's value will be the last state of `Relay1` if [`PowerOnState`](Commands#poweronstate) is set to its default value (`3`). +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#Minute|every minute +Time#Minute\|5|every five minutes +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 +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` and `Status 8` JSON payloads. @@ -114,12 +115,12 @@ Hardware and software serial interface, RF, or IR are also supported based on th Trigger | When it occurs | ------------------|----------------| -|SerialReceived#Data=\| whenever \ is received via hardware serial| +|SerialReceived#Data=\| whenever \ is received via hardware serial| |SSerialReceived#Data=\| whenever \ is received via software serial| -|IrReceived#Data=801| whenever an IR signal for a RC5 remote control button 1 is received| +|IrReceived#Data=801| whenever an IR signal for a RC5 remote control button 1 is received| |IrReceived#Data=0x00FF9867|whenever an IR signal with hex code 0x00FF9867 is received| -|RfReceived#RfKey=4| whenever the [RF Bridge](Sonoff-RF-Bridge-433) receives a recognized RfKey 4 signal -|RfReceived#Data=0xE8329E|whenever an RF signal with hex code 0xE8329E is received| +|RfReceived#RfKey=4| whenever the [RF Bridge](Sonoff-RF-Bridge-433) receives a recognized RfKey 4 signal +|RfReceived#Data=0xE8329E|whenever an RF signal with hex code 0xE8329E is received| [Back To Top](#top)