From 76ab3d511a60adcb2113ba82c59eb28a0e815c2a Mon Sep 17 00:00:00 2001
From: Michael Ingraham <34340210+meingraham@users.noreply.github.com>
Date: Wed, 25 Sep 2019 10:25:40 -0400
Subject: [PATCH] Revert
 81dc48584dbab52a64607dc4419a3cd139b1f3eb...d2097c7f135929159e55a274485f6f0ff92127a6
 on Rules

---
 Rules.md | 56 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 28 insertions(+), 28 deletions(-)

diff --git a/Rules.md b/Rules.md
index ab16e715..e2408160 100644
--- a/Rules.md
+++ b/Rules.md
@@ -65,34 +65,34 @@ Comparison operators:
 
 Some of available triggers:  
 
-Trigger|When it occurs 
-------------------|----------------
-Analog#A0div10<a id=“Analog#”></a>|when the `A0` input changes by more than 1% it provides a value between 0 and 100
-Button2#State<a id=“Button#State”></a>|when a button changes state:<br>`0` = OFF<BR>`1` = ON<BR>`2` = TOGGLE<BR>`3` = HOLD
-Clock#Timer=3<a id=“Clock#Timer”></a>|when global `Timer3` is activated
-Dimmer#Boot<a id=“Dimmer#Boot”></a>|occurs after Tasmota starts<a id="ADC0"></a> 
-Dimmer#State<a id=“Dimmer#State”></a>|when the value for Dimmer is changed
-Event#eventName<a id=“Event#eventName”></a>|when command `Event eventName` is executed. You can define your own event values and trigger them with the [`Event`](commands#event) command.
-Mem\<x>#State<a id=“Mem#State”></a>|when the value for Mem\<x> is changed
-Http#Initialized<a id=“Http#Initialized”></a>|
-Mqtt#Connected<a id=“Mqtt#Connected”></a>|when MQTT is connected
-Mqtt#Disconnected<a id=“Mqtt#Disconnected”></a>|when MQTT is disconnected
-Power1#Boot<a id=“Power#Boot”></a>|`Relay1` state before Wi-Fi and MQTT are connected and before Time sync but after `PowerOnState` is executed. Power#Boot triggers before System#Boot.<BR>This trigger's value will be the last state of `Relay1` if [`PowerOnState`](Commands#poweronstate) is set to its default value (`3`).
-Power1#State<a id=“Power#State”></a>|when a power output is changed<br>use `Power1#state=0` and `Power1#state=1` for comparison, not =off or =on<br>Power2 for Relay2, etc.
-Rules#Timer=1<a id=“Rules#Timer”></a>|when countdown `RuleTimer1` expires
-Switch1#Boot<a id=“Switch#Boot”></a>|occurs after Tasmota starts
-Switch1#State<a id=“Switch#State”></a>|when a switch changes state:<br>`0` = OFF<BR>`1` = ON<BR>`2` = TOGGLE<BR>`3` = HOLD<BR>(`SwitchTopic 0` must be set for this to trigger)
-System#Boot<a id=“System#Boot”></a>|occurs once after MQTT is initialized. Due to the command execution order it cannot occur earlier than that.
-System#Save<a id=“System#Save”></a>|executed just before a planned restart
-Time#Initialized<a id=“Time#Initialized”></a>|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<a id=“Time#Minute”></a>|every minute
-Time#Minute\|5|every five minutes
-Time#Minute==241|every day once at 04:01 (241 minutes after midnight)
-Time#Set<a id=“Time#Set”></a>|every hour when NTP makes time in sync
-Var\<x>#State<a id=“Var#State”></a>|when the value for Var\<x> is changed
-Wifi#Connected<a id=“Wifi#Connected”></a>|when Wi-Fi is connected
-Wifi#Disconnected<a id=“Wifi#Disconnected”></a>|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:<br>`0` = OFF<BR>`1` = ON<BR>`2` = TOGGLE<BR>`3` = HOLD
+Clock#Timer=3     | when global `Timer3` is activated
+Dimmer#Boot       | occurs after Tasmota starts<a id="ADC0"></a> 
+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<x>#State      | when the value for Mem\<x> 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.<BR>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<br>use `Power1#state=0` and `Power1#state=1` for comparison, not =off or =on<br>Power2 for Relay2, etc.
+Rules#Timer=1     | when countdown `RuleTimer1` expires
+Switch1#Boot      | occurs after Tasmota starts
+Switch1#State     | when a switch changes state:<br>`0` = OFF<BR>`1` = ON<BR>`2` = TOGGLE<BR>`3` = HOLD<BR>(`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\<x>#State     | when the value for Var\<x> 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.