I have two switches in this ML rule. If one is on and I trigger the motion, it will not turn the other on. The reason from the log is that it is already on. In reality one is on and the other is off. I have the toggle Do Turn On If Already On set.
EDIT: The Do Turn On if Already On was set after the first switch was turned on.
I suggest you get rid of both options, reduce your turn off time to zero, and get the rule working normally. Then put in the 10 minutes delay. Go from there. Be sure that your light is actually reporting on/off events, because I don't see them in your logs. If it doesn't report them, those options are not going to work.
Thanks. I'll try that.
Both switches do report events. The Garage Flood was turned on in RM, but what I call Driveway Porch isn't being triggered with ML. I do get entries in the log if it is turned on by RM or manually.
When both switches start in the off position the rule will turn both on, the 10 minute delay works and Do Not Turn Off If Already On works.
When one switch is on and the other switch is off, the ML rule thinks they are both on and will not turn the off status switch on with Do Turn On If Already On set.
Yes, one light on makes ML believe the "lights" are on (not that "both" are on). That's how it works. You may need a different way to handle your automation.
Using "Do turn on if already on" may help, but it's getting sort of convoluted.
Forget ML for a minute. Describe how you want the automation to work, with all of the variations that are important to you.
I guess I don't understand what Do Turn On If Already On does if it doesn't make sure both switches in the ML rule are on even if one of them is already on and one is off.
What I want to happen is to have both switches on when the motion is activated even if both or one of them is off.
It sounds like splitting them out into separate ML rules is the way to go. Because both lights are controlled by the same motion it made sense to me to put the switches in the same rule for convenience.
For both options, Don't Turn Off, and Do Turn On, it's only looking for any controlled light to be on or off. ML keeps track of the state of the lights (the collection of them). If any is on, it interprets the lights to be on, so it won't turn them on with motion. That's what Do Turn On overcomes.
So there are separate issues. If you want then both to turn on even if one is already on, use Do Turn On. If you don't want them to turn off if one was turned on by some means other than the app, use Don't Turn Off...
That pretty much summarizes the issue I have. Do Turn On is not turning the lights on if one of them is already on. Don't Turn Off works perfectly.
Please post the Application State portion of the ML instance App Status page (gear icon), at a point in time where it will not turn on the lights from motion becoming active, as well as the logs leading up to that.
Was either of the two lights on at that point? That is what I'm looking for, but need to see the entire context.
Yes. One of the lights was on and one was off.
Same deal with another sensor activating three lights. Two lights selected in the ML rule were already on by another rule. When the sensor was activated the third light did not turn on.
I'm still looking into this one.
Download the Hubitat app
