-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AL dim to 1% #1135
Comments
I'm experiencing the same thing. I went into settings and Sleep Mode is enabled to 1%. The thing is when I disable Sleep Mode and hit submit, it autochecks sleep mode again when I go back into configuration. I set sleep mode to my typical min brightness (50%) and it stays there. I hope this helps for an interim fix. |
I do also have the same issue. The Lights turn to Sleep mode Brightness after some time and a second light turn on from my Motion Sensor Automation. |
I have my living room lights in one z2m group, so I don't have to bother with adding or deleting light in all my automations.
After some time I saw that the is some info about manual control but I didn't change any settings:
So as far as I understand the light should be adapted by 51% Brightness, but they set to 20% which is my configured sleep brightness. |
Hi @Mariuss811,
Seems like a Edit: You mentioned you had all your living room lights in a Zigbee group, which lights did you configure for AL? I had some odd effects myself when I had either HASS or Zigbee light groups, but configured AL to control the lights seperately. For example:
Or the other way around:
And then controlling only Groetjes, |
So I control them by using the And I can also confirm the wierd behavior by adding the whole group Next thing i tried is to reset the configuration of my AL Living Room with: Which didn't change my AL configuration I made via the UI as far as I can say, but at least the light won't go to sleep brightness with the second |
Hi @Mariuss811, On the Re-reading the thread it might be Also, what type of bulbs are these? All the same brand/type? And just in case they are (all) Zigbee, would be interesting to see the Zigbee dump as well, so see what's happening there. Groetjes, |
Hey @djurny They are all the same Brand (Hue) but not the same model. But as far as I can tell, they are all up to date via OTA updates. What do you exactly mean with the Zigbee dump? Like the complete log of z2m at that moment? Here is my configuration in AL:
Greetings |
Hi @Mariuss811, Edit: In case you do not care about doing changes to your lights individually, you could also disable Edit: You might consider using Thx, |
Are you running Z2m Development? I am seeing a 1% similar issue and wondering if this has to do with Z2M and the new 2.0.0 code. |
No, I am running the latest 1.42.0 version. And in my case the light turn to sleep brightness, so not exactly 1% |
So i think it have something to do with the transition settings of In this case i had a
So far as i understand every time i call a
with a transition it gets dimmed down to my configured sleep brightness of AL. Here is my z2m log of
And the logs of AL in the same moment:
|
I have a similar issue and confirmed now. If AL is enabled, then if I turn off PHYSICALLY AT THE SWITCH, the lights will go off, but HA will start to show the lights dimming, but it never marks them as off. Then HA will set the dim percentage back to the AL setting even though the lights are off in the zigbee group. The lights do not go back on because it was at the previous setting and I have marked only to send if the settings are different. If you turn off AL, then all the changes flow back and forth correctly. It is like the AL is ignoring the light turn off command and just reseting back to the original settings. |
Digging in farther, I believe the following section of code, in 'switch.py' is where the manual control gets reset. I believe that this might be getting reset before the light finishes turning off/dimming and AL then gets kicked back on. Perhaps the section needs a delay, equal to the transition time of the off command, before the reset is issued?
|
Perhaps something like this might fix it?
|
I think this could work, but something changed. I mean, I'm using AL like 2 years and never had this issue before. @thk-socal |
@Mariuss811 z2m grouping. Once I made those changes in my groups for z2m, all my issues went away. The status of my groups was not always getting set to OFF for Hass/AL, but the changes made sure it was picked up correctly. I run a separate groups.yaml file for z2m, instead of all of it in the configuration file. |
Also wondering what would happen if you dissolve the Zigbee grouping and use a HASS group for the |
I am not a fan of getting rid of Z2M groupings. The groups allow for the lights to function if HASS is down for any reason, and a requirement from my wife is that they work even if the automation is broken. Also my switches have LEDs on them to indicate on/off and current level of the lights. Running commands at the group keeps all of the levels correct. One additional issue when using HASS groups, you can get popcorning of the lights as they do not get the command at the same time. So I avoid HASS groups when ever possible. |
Hi @thk-socal,
Somehow this issue seems linked with a difference in behavior on how the HASS group works compared to a Zigbee group and having AL not being aware of all members being changed or not getting the correct/latest update on the state of the members of the Zigbee group. Agree on the popcorning thing, yeah, I must admit I also use them, but only per fixture - e.g. some ceiling lights have two or three bulbs so those I have grouped in a Zigbee group. I however will not have AL control the bulbs individually, but AL will control the Zigbee group (or HASS group containing one or more ZB groups or bulbs). Edit: Just wondering why not use the Groetjes, |
I have the same issue on my The two bulbs in |
Hi there, from today my living room hue lights always dim to 1%. I don't understand what's the issue, all my automations are correct.
Thanks. Luca.
The text was updated successfully, but these errors were encountered: