Add command to stop rules

[mkh595]

Currently there is no support for IF..ELSE in the rules.

There is posibility to handle two states:
on tele-DS18B20#temperature do event temp=%value% endon on event#temp<81 do backlog power1 1; power2 1; power3 1 endon on event#temp>85 do backlog power1 0; power2 0; power3 0 endon

Can be added command e.g. STOP to stop rest of rules? This will allows to simulate IF..ELSEIF..ELSE..ENDIF and control each relay separatelly.
Example:

IF temp > 85 then
  POWER1 OFF; POWER2 OFF; POWER3 OFF;
ELSEIF temp > 83 then
  POWER1 ON; POWER2 OFF; POWER3 OFF;
ELSEIF temp > 81 then
  POWER1 ON; POWER2 ON; POWER3 OFF;
ELSE
  POWER1 ON; POWER2 ON; POWER3 ON;
ENDIF

Rule:
on tele-DS18B20#temperature do event temp=%value% endon on event#temp>85 do backlog power1 0; power2 0; power3 0; STOP endon on event#temp>83 do backlog power1 1; power2 0; power3 0; STOP endon on event#temp>81 do backlog power1 1; power2 1; power3 0; STOP endon on event#temp<81 do backlog power1 1; power2 1; power3 1 endon

Thank you

[ascillato]

Hi,

You have 3 independent set of rules
Rule1, rule2 and rule3

You can turn on or off any set by command rule2 1 for on and rule2 0 for off

[ascillato]

Besides that, the rule triggers are being evaluated in the same order that you wrote them, so the following rule should be working as you want, because only the first match will be executed:

on tele-DS18B20#temperature do event temp=%value% endon on event#temp>85 do backlog power1 0; power2 0; power3 0 endon on event#temp>83 do backlog power1 1; power2 0; power3 0 endon on event#temp>81 do backlog power1 1; power2 1; power3 0 endon on event#temp=81 do backlog power1 1; power2 1; power3 1 endon on event#temp<81 do backlog power1 1; power2 1; power3 1 endon

[andrethomas2]

Closing this issue as it has been answered.

Support Information

See Wiki for more information.
See Chat for more user experience.

[mkh595]

You can turn on or off any set by command rule2 1 for on and rule2 0 for off

Two rules are already occupied because temperature levels are calculated by ADD or SUB in rule from temperature set by HA. Therefore I can turn On/Off only one rule. In example were temperatures hardcoded.

Besides that, the rule triggers are being evaluated in the same order that you wrote them, so the following rule should be working as you want, because only the first match will be executed:

This unfortunately doesn't work. If all conditions are fulfilled then all are executed. That's why I asked for STOP to trigger only first which match

on event#temp>30 do backlog power1 0; power2 0; power3 0; STOP endon on event#temp>27 do backlog power1 1; power2 0; power3 0 endon on event#temp>24 do backlog power1 1; power2 1; power3 0 endon on event#temp<20 do backlog power1 1; power2 1; power3 1 endon

22:44:11 MQT: tele/home207/SENSOR = {"Time":"2018-11-28T22:44:11","DS18B20":{"Temperature":30.5},"TempUnit":"C"}
22:44:11 RUL: TELE-DS18B20#TEMPERATURE performs "backlog backlog var1 30.5; event check=1"
22:44:12 MQT: stat/home207/RESULT = {"Var1":"30.5"}
22:44:12 MQT: stat/home207/RESULT = {"Event":"Done"}
22:44:12 RUL: EVENT#CHECK=1 performs "backlog event temp=30.5"
22:44:12 MQT: stat/home207/RESULT = {"Event":"Done"}
22:44:12 RUL: EVENT#TEMP>30 performs "backlog power1 0; power2 0; power3 0; STOP"
22:44:12 RUL: EVENT#TEMP>27 performs "backlog power1 1; power2 0; power3 0; STOP"
22:44:12 RUL: EVENT#TEMP>24 performs "backlog power1 1; power2 1; power3 0; STOP"
22:44:13 MQT: stat/home207/RESULT = {"POWER1":"OFF"}
22:44:13 MQT: stat/home207/POWER1 = OFF
22:44:13 MQT: stat/home207/RESULT = {"POWER2":"OFF"}
22:44:13 MQT: stat/home207/POWER2 = OFF
22:44:13 MQT: stat/home207/RESULT = {"POWER3":"OFF"}
22:44:13 MQT: stat/home207/POWER3 = OFF
22:44:14 MQT: stat/home207/RESULT = {"POWER1":"ON"}
22:44:14 MQT: stat/home207/POWER1 = ON
22:44:14 MQT: stat/home207/RESULT = {"POWER2":"OFF"}
22:44:14 MQT: stat/home207/POWER2 = OFF
22:44:14 MQT: stat/home207/RESULT = {"POWER3":"OFF"}
22:44:15 MQT: stat/home207/POWER3 = OFF
22:44:15 MQT: stat/home207/RESULT = {"POWER1":"ON"}
22:44:15 MQT: stat/home207/POWER1 = ON
22:44:16 MQT: stat/home207/RESULT = {"POWER2":"ON"}
22:44:16 MQT: stat/home207/POWER2 = ON
22:44:16 MQT: stat/home207/RESULT = {"POWER3":"OFF"}
22:44:16 MQT: stat/home207/POWER3 = OFF

[ascillato]

Hi,

I'm sorry. I had the concept wrong from some other tests I was doing.

You are right, testing this type of cases will perform as you said. Testing with a simplified rule:

rule1
on event#temp>85 do VAR1 more85 endon
on event#temp>83 do VAR1 more83 endon
on event#temp>81 do VAR1 more81 endon
on event#temp=81 do VAR1 equal81 endon
on event#temp<81 do VAR1 less81 endon

I have this output in the console :

19:43:18 CMD: rule
19:43:18 MQT: stat/living/RESULT = {"Rule1":"ON","Once":"ON","StopOnError":"OFF","Free":322,"Rules":"on event#temp>85 do VAR1 more85 endon on event#temp>83 do VAR1 more83 endon on event#temp>81 do VAR1 more81 endon on event#temp=81 do VAR1 equal81 endon on event#temp<81 do VAR1 less81 endon"}

19:43:24 CMD: event temp=10
19:43:24 MQT: stat/living/RESULT = {"Event":"Done"}
19:43:24 RUL: EVENT#TEMP<81 performs "VAR1 less81"
19:43:24 MQT: stat/living/RESULT = {"Var1":"less81"}

19:43:36 CMD: event temp=100
19:43:36 MQT: stat/living/RESULT = {"Event":"Done"}
19:43:36 RUL: EVENT#TEMP>85 performs "VAR1 more85"
19:43:36 MQT: stat/living/RESULT = {"Var1":"more85"}
19:43:36 RUL: EVENT#TEMP>83 performs "VAR1 more83"
19:43:36 MQT: stat/living/RESULT = {"Var1":"more83"}
19:43:36 RUL: EVENT#TEMP>81 performs "VAR1 more81"
19:43:36 MQT: stat/living/RESULT = {"Var1":"more81"}

So, your idea of a kind of STOP command is appropiate for these type of cases. Thanks for share your ideas.

Working on that...

[ascillato]

Another idea,

To use the command STOP, you will need all the time to use also the BACKLOG command

So, the actual rule syntax is

ON [TRIGGER]=[CONDITION] DO [COMMANDS] ENDON

IDEA 1 - Using the proposed STOP, an alternative rule syntax could be:

ON [TRIGGER]=[CONDITION] DO BACKLOG [COMMAND1]; [COMMAND2]; STOP ENDON

IDEA 2 - So, another alternative rule syntax also could be:

ON [TRIGGER]=[CONDITION] DO [COMMANDS] BREAK

So, when there is a set of rules, the first trigger that matches will execute the commands and then stop the execution of the rest of the rules that continues in the set.

This should allows to simulate IF..ELSEIF..ELSE..ENDIF
Example:

IF temp > 85 then
  VAR1 more85
ELSEIF temp > 83 then
  VAR1 more83
ELSEIF temp > 81 then
  VAR1 more81
ELSEIF temp = 81 then
  VAR1 equal81
ELSE
  VAR1 less81
ENDIF

IDEA 1 - Rules with STOP command:

on event#temp>85 do backlog VAR1 more85; stop endon
on event#temp>83 do backlog VAR1 more83; stop endon
on event#temp>81 do VAR1 more81 endon
on event#temp=81 do VAR1 equal81 endon
on event#temp<81 do VAR1 less81 endon

IDEA 2 - Rules with break ending:

on event#temp>85 do VAR1 more85 break
on event#temp>83 do VAR1 more83 break
on event#temp>81 do VAR1 more81 endon
on event#temp=81 do VAR1 equal81 endon
on event#temp<81 do VAR1 less81 endon

So, what do you think?

[mkh595]

Doesn't matter if STOP or BREAK.
Doesn't matter if with BACKLOG or without.
As I am working with more relays I have to use BACKLOG anyway do backlog power1 1; power2 0; power3 0 endon
But if BREAK will be recognize as internal rules command like ON or ENDON then BACKLOG for one command will be not necessary and can save few characters in rule.

Implement what will be easiest DO .... STOP ENDON or DO....BREAK

Thank you