Hello,
Tagging @bobbyD, @gopher.ny and @bravenel
I'm having an issue with a rule on Motion Lighting which looks like a bug.
From what I can see, the "Do turn on if already on" setting is being ignored.
I did a simple test of activating the motion sensor, which turned on the light, then walking away. Then I set the CT to something else, and triggered the motion sensor again.
Instead of setting the CT to the correct one again, it logged "not turning on, already on", which I wasn't expecting.
I also tested doing it differently, instead of using CT changes I tried just with using the "switch to turn on", and I manually turned the light off on the Hue app to see if Motion Lighting would send the On command again even though it thought the light was on, and again, same thing - "not turning on, already on".
Please find attached screenshots of the rule and of the logs.
Thank you!
Your logs don't show a malfunction. It was turned on at 17:36:07, and not turned off before the following motion active event at 17:36:30. So, at that point, the lights are on as far as ML is concerned. What am I missing?
'Do turn on if already on' has to do with multiple lights where one is on and others not.
I expected it to send the on command even tough it considered them already on.
What is not shown on the log is that before that happened, I changed the colour temperature of the light to 5000K, to see if the rule would change it back, but it didn't.
I guess I misinterpreted what do turn on when on means, and it doesn't mean to send the on command even if the light is already on from the rule
I think I was looking for something like disable command optimization, but I dont think there's an option like that on ML
Let me take a look at the app. I'll get back to you. Actually, the idea of turning off command optimization makes sense. I'm pretty sure it's not looking at the subtlety of changed color temps.
Thank you.
I imagined it wouldn't account for CT, but I was expecting it to send the on command anyway because I have some Hue Switches connected directly to the Hue Bridge, and since it depends on polling, the lights off state can take a while to reach the Hubitat hub.
Having motion Lighting send the on command anyway would bypass the problem.
I know it's a pretty specific use case, but I thought it didn't hurt to ask. I have it working on RM, but always better to keep things simple.
I'm wondering whether I am having a similar issue where I want to essentially override motion lightling when I initiate some kind of manual control of the lights, but then when I try to return to using motion lighting I get the impression the motion lighting "rule" seems to have a state of still being "on", i.e. the rule not necessarily the lights. I then get the "Not turning on, already on" message in the logs. It feels like there needs to be an option for say a switch that can be used to turn off the rule without turning off the lights the rule acts on.
Was there any resolution to the issue raised in the earlier posts?
