-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Feature request: Adaptive Lighting should be inactive when the light is activated via brightness #581
Comments
See the V2 Roadmap for the main thread. This has been requested many many times already. tldr, if you want to turn a light manually from off->on with AL, either call light.turn_on twice: once to turn the light on and second to set the target brightness/color, or call |
I have this same issue. @th3w1zard1, you mention that this should work with scenes. Do you have any advice on that? When I apply a scene, even if I turn off the main adapt brightness toggle in the scene, the lights that are turned on by the scene that were previously off get adapted, breaking the scene. |
I am implementing an option Enabling this will make sure AL doesn't take over when setting a scene. |
This is now in the latest beta release. Looking forward to your feedback. |
@basnijholt |
Thanks a lot for getting back to me! Glad you like it 😄 |
Hello dear community,
I am observing an undesirable behaviour. If I set a switched-off light in Homeassistant directly to a certain brightness in the context menu of the frontend, this is overwritten by Adaptive Lighting.
I would therefore like to see the following behaviour, if possible:
The text was updated successfully, but these errors were encountered: