Light.turn.on brightness and brightness step pct not working

Configuration
1

I hope this is an easy answer, but one of my lights seems to not want to work in an automation. All I want it to do is dim the light over 10 minutes by 5 percent to 1 percent from whatever the light is set at. Every time the automation runs I get this error.

Stopped because an error was encountered at November 17, 2021, 1:45:16 PM (runtime: 0.01 seconds)

two or more values in the same group of exclusion ‘brightness’ @ data[]

Here is my yaml:

image

What am i doing wrong?

Thanks everyone.

2

Remove the brightness_step part.

3

Thanks @Burningstone but when i remove the step pct then the light simply dims to 1pct right away and does not do it over 600 seconds. How would set it up to slowly dim over 10 minutes?

4

Not sure, but shouldn’t it be light.turn_off

5

The error is because you have specified two options for setting the desired brightness. Choose one.

From the documentation for the Light integration;

brightness
Integer between 0 and 255 for how bright the light should be, where 0 means the light is off, 1 is the minimum brightness and 255 is the maximum brightness supported by the light.

brightness_step
Change brightness by an amount. Should be between -255…255.

That implies the light doesn’t support the transition effect.

Transition is not implemented in software but relies on the light’s native support for the effect. If the light has no native ability to perform the effect, the transition option is simply ignored by the light.

6

I see your point, but the only thing i have seen is that i can do the same thing to the same light in Alexa app. Dim the light over 10 minutes. I guess Alexa is using a different mechanism, To give you more detail the light is a Lutron Caseta smart Dimmer Switch. Hope t his helps at all.

Thanks,

7

According to the documentation for the Lutron Caséta integration, it supports the transition effect.

Available services: light.turn_on, light.turn_off and light.toggle. The light.turn_on service supports attributes brightness, brightness_pct and transition.

As an experiment, turn off the light manually then execute the service call you created but set brightness_pct to 100 and transition to 600 (representing 5 minutes). Don’t include brightness_step.

If the light turns on instantly, that’s not how the transition command should behave so you may have found a bug in the Lutron Caséta integration and should report it as an Issue in Home Assistant’s Core repository on GitHub.

8

Ok I tried the Light in Developer Tools here is what I did:

Call Service:

image
image1240×327 23 KB

image
image1250×437 32.3 KB

Here is a result from my dashboard the light turned on instantly not over the time period.
image

It looks like a bug. I will post it in t he Github group. thanks for the help.

9

The Lutron Caseta lighting control devices send a response to the bridge with the target level as soon as the transition begins. Note that it doesn’t report the instantaneous light level over time throughout the transition.

So if you stand in the space and watch the brightness change, you will see it slowly turn on or slowly dim over the transition period. On the other hand, if you watch only the light level displayed on an app or dashboard somewhere, you will see it “immediately” jump to the target level because that is the level reported by the bridge as soon as the service request is responded to.

I’ll also note that dimming curves are complicated and the way we perceive light levels through our eyes is not a simple linear scale. Lutron dimmers are calibrated to yield a dimming curve that appears to linearly scale an incandescent light bulb’s brightness from 0 to 100 smoothly, but all dimmable LEDs behave differently (especially at low light levels). So your particular light may appear to go from off to very bright very quickly, but that could just be because the apparent difference in light level from 1% to 3% brightness looks about the same as the apparent difference from 3% to 70%.

10

Could you link to the github bug? I am facing a similar issue.

11

@ensonic

It turns out it was not a bug it was my mistake. i was using the wrong Protocall. When you use this light in an automation you want to use “Call Service” then “Light Turn on”. Then when you get into t he settings for Light Turn on Pick the delay time in seconds for it to dim. You can watch it run and it will dim to the amount of seconds. If you look at a Dashboard it will instantly tell you the light is at that level although it is dimming to that level.

I hope this helps.

Drezin2112