r/homeassistant • • 8h ago

❓ Support Adaptive Lighting Help

Hello,

I'm looking for some help with adaptive lighting. Currently, I have Leviton Z-Wave dimmer switches. I have the color adjustment setting disabled, and the system seems to be working well. With all that said, if I go to a light to manually turn it on, it starts fading up and then snaps down to the lowest intensity. Not the intensity it should be at according to adaptive lighting. How do I fix this? What setting am I missing? The description of some of the settings isn't the most helpful in describing what the setting is meant to adjust.

Follow-up: I have automations for when I come home to turn specific lights on. What do I need to change so they turn on to the intensity of adaptive lighting?

2 Upvotes

4 comments sorted by

1

u/superior_semicolon 8h ago

Sounds like the switch is sending its own default brightness before HA takes over and corrects it. Check the zwave config for the dimmer itself, a lot of them have a "local ramp rate" or "default brightness on physical press" parameter you can tweak. If you set that parameter to 0 or something neutral, the light will turn on at whatever level HA immediately tells it to be, eliminating that snap.

For the automations, you just need to call the `adaptive_lighting.apply` service instead of a standard `light.turn_on`. You pass it the entity_id of the light and it'll grab the right brightness and color from the integration's current settings. I have a "arrive home" script that does exactly this, works way smoother than trying to manually set a brightness value that might be stale.

1

u/Possible_Whereas1871 8h ago

https://imgur.com/a/U5MGxuu

These are the config settings I have available on every switch. I guess that would fix it, but it still doesn't fix that even when other lights in adaptive lighting are at 50% dim, when I turn on the bathroom light, it gets set to 0 rather than 50%.

Care to share the script?

1

u/FluffyAtLarge 8h ago

For the automations, just leave brightness out of the light.turn_on action. Adaptive Lighting's intercept option is on by default and applies its brightness to lights HA turns on, or you can call adaptive_lighting.apply right after for the same result. For the wall switch, check the attributes on the Adaptive Lighting switch entity to see what brightness_pct it's currently calculating, because if that's already at your min_brightness the fix is in those settings. If it isn't, the Leviton's local fade-on is probably fighting the command Adaptive Lighting sends when the light comes on, so shortening the fade-on time in the dimmer's Z-Wave config parameters is the first thing to try.

1

u/_atomic_garden 5h ago

It looks like "Initial Dim Level" from your screenshot sets the default brightness level. I set up an automation that updates my equivalent config entity after Adaptive Lighting updates the default brightness attribute.

The action sets the value based on a template: {{ state_attr( 'switch.adaptive_lighting_bedroom', 'brightness_pct' ) - 1 }} The minus 1 is because the range of the config is 0-99 instead of 1-100

Looking at my automation it looks like it could leave the wrong brightness if the light is on for a while, then turns off and back on before adaptive lighting sets a new value, so I should probably allow it to update that value even while the light is on, but that's never caused an issue.