Skip to content
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

Lights not adapting until Reload is selected #1056

Open
Fonzi03 opened this issue Oct 8, 2024 · 19 comments
Open

Lights not adapting until Reload is selected #1056

Fonzi03 opened this issue Oct 8, 2024 · 19 comments

Comments

@Fonzi03
Copy link

Fonzi03 commented Oct 8, 2024

home-assistant_adaptive_lighting_2024-10-08T22-32-08.613Z.log

  1. Your Adaptive Lighting configuration:

I used the UI config not YAML, I see this note but not sure where it should go in the config or what it should include
"Note: If you plan to strictly use the UI, the adaptive_lighting: entry must still be added to the YAML."

Without that line adaptive lighting does function and reloading the integration kickstarts it again. Do I just need to add a node like this:

#Adaptive Lighting Config, no entries needed if using UI
adaptive_lighting:
  1. Im using ZHA
    • Brand and model number of problematic light(s)
      Philips Hue White Ambiance (LTD010 and LTD009)

Switches are Inovelli Blue series
Switches are bound to the group of lights
The group is set to the adaptive lighting integration

  1. Describe the bug and how to reproduce it:
    Turn lights off via switch, wait some time (in my case usually after work so a few hours but doesnt need to be that long)
    Turn on lights via switch
    Lights return to previous value and do not continue to adapt even though AL settings are all enabled.

  2. Steps to reproduce the behavior:
    To correct the behavior go to Adaptive lighting integration, and select reload for each affected area.
    Lights now continue to adapt while on.

*EDIT: Min and max brightness are 12/100% respectively, those seem to be the only parameters not displayed in the snips.

image
image

image
image
image
image

@kyc1338
Copy link

kyc1338 commented Oct 9, 2024

same issue.

@Fonzi03
Copy link
Author

Fonzi03 commented Oct 9, 2024

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your adapt delay is set to some reasonable number to give it a chance. I have mine at 0.5s.

@kyc1338
Copy link

kyc1338 commented Oct 11, 2024

Y

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your initial transition to some reasonable number to give it a chance. I have mine at 5s.

This works great, thanks.

@Lawris
Copy link

Lawris commented Oct 12, 2024

Hello, same issue here

@MrTinyStark
Copy link

Hello. Same issue here as well.

@Fonzi03
Copy link
Author

Fonzi03 commented Oct 28, 2024

@basnijholt looks like this is fairly widespread, any chance you could investigate? I am willing to test and provide results if you need it.

@warrap1989
Copy link

Same issue here

@bergethan
Copy link

Same issue here.

@PetFra
Copy link

PetFra commented Oct 29, 2024

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your adapt delay is set to some reasonable number to give it a chance. I have mine at 0.5s.

Same issue. Can you elaborate a bit more on your workaround? I didn't get how to set it. Thanks!

@Fonzi03
Copy link
Author

Fonzi03 commented Oct 29, 2024

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your adapt delay is set to some reasonable number to give it a chance. I have mine at 0.5s.

Same issue. Can you elaborate a bit more on your workaround? I didn't get how to set it. Thanks!

Set an automation where when you turn the lights off it. Also disables the adaptive lighting for that particular zone /group. When you turn the lights on enable adaptive lighting. This force is adaptive lighting to load every time the lights are turned on which ultimately keeps them in sync.

1 similar comment
@Fonzi03
Copy link
Author

Fonzi03 commented Oct 29, 2024

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your adapt delay is set to some reasonable number to give it a chance. I have mine at 0.5s.

Same issue. Can you elaborate a bit more on your workaround? I didn't get how to set it. Thanks!

Set an automation where when you turn the lights off it. Also disables the adaptive lighting for that particular zone /group. When you turn the lights on enable adaptive lighting. This force is adaptive lighting to load every time the lights are turned on which ultimately keeps them in sync.

@PetFra
Copy link

PetFra commented Oct 29, 2024

same issue.

Just a tip, a workaround is to disable AL when the light turns off and enable when turned on. Just be sure to set your adapt delay is set to some reasonable number to give it a chance. I have mine at 0.5s.

Same issue. Can you elaborate a bit more on your workaround? I didn't get how to set it. Thanks!

Set an automation where when you turn the lights off it. Also disables the adaptive lighting for that particular zone /group. When you turn the lights on enable adaptive lighting. This force is adaptive lighting to load every time the lights are turned on which ultimately keeps them in sync.

Gotcha, I need to find a way to make it "general" and not for each light - so far they are seven where I use AL. Hope the developer can look into it

@ZeddicPrime
Copy link

To make it easier for the workaround, I created a "Run in sequence" step that turns off adaptive lighting (the main switch, not the integration itself), waits 500 ms, then turns it on. And I copy/paste that section into each automation that includes a "Light: Turn on" step and update the target entity. It could probably be made into a script that accepts a device input, or it could be its own automation that cycles the associated adaptive lighting for any switch. But all of that seems like unreasonable effort - hoping this bug gets fixed soon.

Side note: I don't know if this is an HA problem (2024.10.4) or an Adaptive Lighting problem, but more than once when updating my automations with this workaround, the actual name of the automation changed (I definitely didn't change the name intentionally or even unintentionally) and suddenly I couldn't save it and was getting an error that said "only automations in automations.yaml are editable". To fix I had to abandon my changes, go back to my list of automations, and force a refresh to find the renamed automation.

@PetFra
Copy link

PetFra commented Oct 29, 2024

To make it easier for the workaround, I created a "Run in sequence" step that turns off adaptive lighting (the main switch, not the integration itself), waits 500 ms, then turns it on. And I copy/paste that section into each automation that includes a "Light: Turn on" step and update the target entity. It could probably be made into a script that accepts a device input, or it could be its own automation that cycles the associated adaptive lighting for any switch. But all of that seems like unreasonable effort - hoping this bug gets fixed soon.

Side note: I don't know if this is an HA problem (2024.10.4) or an Adaptive Lighting problem, but more than once when updating my automations with this workaround, the actual name of the automation changed (I definitely didn't change the name intentionally or even unintentionally) and suddenly I couldn't save it and was getting an error that said "only automations in automations.yaml are editable". To fix I had to abandon my changes, go back to my list of automations, and force a refresh to find the renamed automation.

Hi thanks for sharing. I added the step to add the light/lights into Adaptive Light in the scenes so it seems to work. What I didn't get yet is if AL keeps adapting the temperature.
EDIT: no, it doesn't keep updating the temperature of a light, it just set the temperature when the scene is called.

Hope the bug get fixed

@Fonzi03
Copy link
Author

Fonzi03 commented Oct 29, 2024

To make it easier for the workaround, I created a "Run in sequence" step that turns off adaptive lighting (the main switch, not the integration itself), waits 500 ms, then turns it on. And I copy/paste that section into each automation that includes a "Light: Turn on" step and update the target entity. It could probably be made into a script that accepts a device input, or it could be its own automation that cycles the associated adaptive lighting for any switch. But all of that seems like unreasonable effort - hoping this bug gets fixed soon.

Side note: I don't know if this is an HA problem (2024.10.4) or an Adaptive Lighting problem, but more than once when updating my automations with this workaround, the actual name of the automation changed (I definitely didn't change the name intentionally or even unintentionally) and suddenly I couldn't save it and was getting an error that said "only automations in automations.yaml are editable". To fix I had to abandon my changes, go back to my list of automations, and force a refresh to find the renamed automation.

Hi thanks for sharing. I added the step to add the light/lights into Adaptive Light in the scenes so it seems to work. What I didn't get yet is if AL keeps adapting the temperature.
EDIT: no, it doesn't keep updating the temperature of a light, it just set the temperature when the scene is called.

Hope the bug get fixed

If you do it the way I mentioned it will continue to adapt. The integration works well once it's "reloaded". This effectively causes that

@ZeddicPrime
Copy link

I'm probably just terribly inept, but how do you automate the reload of the integration itself? I can't find a generic "Integration: Reload" action or anything similar to put into an automation or script.

Or are you saying you do this by hand using the GUI? If that's the case, do you just have to reload the integration once per HA boot, or once every time the lights go from off to on?

@Fonzi03
Copy link
Author

Fonzi03 commented Oct 30, 2024

I'm probably just terribly inept, but how do you automate the reload of the integration itself? I can't find a generic "Integration: Reload" action or anything similar to put into an automation or script.

Or are you saying you do this by hand using the GUI? If that's the case, do you just have to reload the integration once per HA boot, or once every time the lights go from off to on?

Just create a scene with the adaptive lighting settings in it and save it with it On and save another with it off.

Then create an automation that when the lights group is turned off the off scene is triggered. When lights group on trigger the on scene.

@danpeps
Copy link

danpeps commented Nov 12, 2024

I had the same issue but I discovered that in my automation that was turning the light on, I had specified the device I wanted to turn on. Once I changed that automation to specify the entity instead, AL started working as expected.

Hope that helps someone.

@Fonzi03
Copy link
Author

Fonzi03 commented Nov 12, 2024

I had the same issue but I discovered that in my automation that was turning the light on, I had specified the device I wanted to turn on. Once I changed that automation to specify the entity instead, AL started working as expected.

Hope that helps someone.

I'm not sure what you mean.

I took all My lights that are in the room and turn them into a zigbee group. From there I bound the switch to the light group. Went into adaptive lighting and I added the light group entity in the switch.switch entity.

Doing it this way does not work. In the incense I describe above there are no automations or scenes. The only way I found to make it work is to create an automation which enables and disables adaptive lighting. Unless I'm just totally missing something here. But I believe adaptive lighting only lets you assign the light entities anyways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants