Since I upgraded from 2.0.6 to 2.0.7 I have been having issues with motion lighting.
What still works fine is the turning on of the lights when motion is detected and the turning off of the lights when motion no longer is detected. However, it’s the in-between behaviour that has changed and I don’t know if it’s a bug or a feature.
For starters, even though I have motion lighting rules that have the switch set so that they will not change when a mode is changed (while the lights are on that is), they now change to the settings for the current mode as soon as motion is detected.
Example: My living room lights are configured to 67% brightness during evening mode and 5% during night mode. The “adjust levels when mode changes?” switch is also disabled. Even though the lights are on and I’m moving around the living room, the lights dim to 5% as soon as night mode is triggered and motion is detected. This did not happen in 2.0.6.
Secondly, and maybe caused by the same bug/feature as is causing the above issue, I have an issue with motion lighting overriding a light setting that has been set manually. It appears to do this as soon as motion is detected (this is while the lights are already on, and they were turned on by motion lighting to begin with). It’s like motion lighting sends a command to the lights to set the lights to the configured settings every time motion is detected rather than just resetting the “delay to turn off” timer which appears to have been happening in 2.0.6.
Example: Motion lighting will always set the lights to 67% when it turns them on during evening mode. If we wanted them dimmer than that, we would just override that by asking Alexa to set them to a different level. In 2.0.6 that was not a problem. The new level would remain until motion lighting determined that there has now not been any movement for the set period of time and turns the lights off. In 2.0.7 it seems like motion lighting will reset the lights to the configured setting every time the motion sensor reports that there is motion in the room. So once we have changed the light level to something else, that will only remain for half a minute or so until motion is detected in the room again and motion lighting then resets the light levels again.
Can someone please advise whether this is a bug or the new normal?
1 Like
I've noticed the same, but I thought it started in 2.0.6. I just thought I had changed something incorrectly, but kept forgetting to test/ fix it each time I saw it.
@mattias Do you have override with level change set (which I have)? If you turn in logging what do you get?
@bravenel I'll also get some logs tomorrow on it, but has there been any changes?
There was actually a fix put in 2.0.7 to deal with this issue. So I'm not sure what is happening with your setup. Motion Lighting is designed to not touch the lights on new motion-active events once it has turned them on. With the Adjust on mode change feature turned off, it should not do anything upon the mode changing.
Please turn on the logging in Motion Lighting. This will show you what it's "thinking" for events such as you are describing.
Update: I did just catch it changing the level upon mode change when it should not. Will investigate. --> Found a typo, one letter not capitalized that should have been. That fix will go in for upcoming release.
That one typo would explain what you're seeing. Thanks for bringing my attention to it.
5 Likes
@bravenel I presume you're talking about the level change that a mode change causes?
My other issue with motion lighting setting the levels every time motion is detected has gone away now. The issue was there this morning but has disappeared while I was away over the day. The log file below shows you how motion lighting kept setting the level every time motion was detected, but this afternoon, it's not doing it anymore. This affected several different motion lighting rules and they are all fine now.
@BorrisTheCat I am pretty sure I was already on 2.0.6 before I upgraded to 2.0.7 a couple of days ago. But I can be wrong as well.
All of this behavior is from that one bug. Fix is in, coming out in next release.
I'm one of the ones doing the Iris V1 beta testing, I noticed that my motion sensors dont have any delay time. My alarm was armed this morning and when I walked downstairs to key in the code on the Iris v2 keypad, the alarm started sounding. This also happened this afternoon as well. I have the delay set for 15 seconds. When I click on the box for sensors for the delay, I dont see any motions there. Everything was working like it should prior to the newest software.
There's currently known issues with HSM and the keypads, we're finishing up these changes now.
1 Like
My keypads work fine, it's the motion sensors that are giving me the problems. I cant find where to adjust the intrusion delays for them.
Thanks Bruce. I'm always impressed by the prompt replies I get from Hubitat support on any issues. And over a weekend as well! Hats off to you guys!
1 Like
BTW, this was fixed in 2.0.8. Please see if your problems are resolved.
Yep, I tried it out last night and I can confirm it fixed the problem. Thanks!
1 Like
