Are two rules really needed to turn a light on and off?
One for the "on" trigger, and one for the "off" trigger?
It seems that way, but I could be missing something.
I'm used to SA, and this would be one rule.
Starting off slow, I just wanted to try turning a light on and off by turning a switch on and off. It seems like the only way to do this is to have a RM rule to turn used the switched on as a trigger to turn it on, and another rule to use switched off as a trigger to turn it off.
I tried several things, and this was the only way I could do I it.
I figure there's gotta be a better way, but it's early.
I've got a ways to go, but here's my first effort.
I have to brush up on my Else, ElseIf, End, etc, etc, etc. Plus that other method. Plus everything else. But hey, it works.
It'd be a good practice to end each IF block with an END-IF. Doesn't matter so much in this case, but this is much more important as you start creating rules with nested IF blocks.
if you're trying to do something as basic as that, i would recommend simple automations. it offers less overhead than rule machine and can achieve what you want within a single simple automation
You did say RM, so this isn't really answering our question, but you can also use the built-in "Mirror" app if you're just trying to control a second switch when a first switch is changed.
Or if the switch has Central Scene capability, use the "Select Button Device" option and then set different actions for Button 1 and Button 2.