actually in this case it was fine in my original setup of this rule, i just needed to move it with how i now used the rule.
i agree and this is what i ended up doing i was just using the previous bit as a reference rather than writing it down , hence how i found it and let you know but if it's there for a reason then its all OK.
@bravenel would a wiki style page of RM “recipes” be helpful? I would think it would benefit everyone, I know it would me. Maybe break it into sections depending on what the rule would oversee. Easy to complicated, lighting, motion, etc. This way there would examples for users to follow to set up their own systems. The recipes could be posted with “device type motion” or “music player” etc and then be adapted to each users individual devices, or used as a guide to get a rule set up correctly. This would also serve as a “best practice” for creating rule machine rules. This might also give a user inspiration to automate something that they hadn’t thought of, or even know was possible.
when setting GV it allows you to select more than one, when you do it allows you to give them both their values but when you click done with action it only shows the last GV. Instead of both.
This is something I wish we had but so far I have been able to find a way around it by adding more conditions and them using them as the expression of IF ELSE IF ELSE IF ELSE statements in very specific orders. Sometimes I have been required to split up logic and use two rules.
if (expr) { }
else if (expr2) {}
else if (expr3) {}
else {}
Then you basically have to put your conditions in order from most restrictive to least restrictive so that by the time you get to the bottom of the chain you don't need to AND expressions hopefully. If you still need AND then that's when the second rule comes in to play and you essentially have to utilize the "Set Rule" portion of the rule for the AND or OR expressions.
You can also AND and OR if the types are the same. For example, in this image "all is off" is lamp is off AND bulb is off. So you can do that as well.
The question really is this: For how long, or how many times, or under what conditions do you want these to repeat. Answer that question first, and then we can see the right way to do that.
I reproduced something like your trigger, and the IF-THEN on a Boolean variable, followed by and ELSE-IF with a mode condition, worked as expected. So I'm not sure why yours doesn't continue to log. It should log the ELSE-IF, ELSE, etc.