This looks like a bug.
The rule in the editor correctly evaluates the last condition as true, but in the logs it shows it is not executing the "THEN" Fan speed set to low.
I am running v2.3.3.140
This looks like a bug.
The rule in the editor correctly evaluates the last condition as true, but in the logs it shows it is not executing the "THEN" Fan speed set to low.
I am running v2.3.3.140
I donāt think thatās a bug but Iām reading on my phone so may be wrongā¦.
Take out the first of your End-Ifās⦠If it the first statement is false and the next statement is false, that first End-If stops the last statement being evaluated, so even if itās true itās skipped.
Iād also possibly edit the first bit and pop parentheses around the temperature statement.
Edit - Iām misreading it lol. Iāll look at it on the big screen and edit this.
You have edited the rule and now have two ELSE statements if the 1st IF is not true. They should be a Else IF and a Else or two ELSE IFs.
Your conditional actions are malformed. You can only have one ELSE per IF THEN. If the expression on the IF THEN or any (optional) ELSE-IFs is false and there is an ELSE, then the ELSE section will run. It catches all other cases. Only zero or one sections inside an IF THEN (the IF THEN, the ELSE-IF, or the ELSE) will be run per execution. Adding a second ELSE block results in un-reachable actions since something before it would necessarily have matched already (if nothing else, the first ELSE).
From your rule, it seems like you want to make these ELSE-IFs, rather than ELSEs with a nested IF THEN. That should work how you want, unless I'm not guessing correctly about what you want the rule to do.
Y'all are exactly right. A malformed IF THEN... There is no ELSE IF, so I need to rearrange this. That's what I get for staying up too late. Apparently at 2:30AM the IF THEN ELSE ELSE makes sense! I nested the second else back a bit. I think that will work.
oh really? Let me see...
If I recall right, it only shows up as an action when there's already an open IF-THEN action. If you already have IF-THEN-END...an ELSE IF THEN action wouldn't make sense.
Yeah, you have to be in the middle of creating a conditional action. (It can still make sense to add one if you aren't, given that actions can be cut/copied and pasted or moved, but I suppose RM is trying to save unsuspecting users from themselves by doing this.)
You're right. As I am composing the thing it's not valid almost until the very end. I don't think it makes a lot of sense to try to restrict these commands until complete. In any case, it's all fixed up now.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.