#Automated light ignores start_brightness

1 messages · Page 1 of 1 (latest)

rocky fjord
#

Hey guys, I am using a wake up light that is working fine for my Hue Iris lamp. I added my ceiling light to the wake up mode which is working as well, but the light always starts at 100 % brightness although in the automation start_brightness is set to 1. The lbulbs used for that are Tapo L530.
Could you please have a look at my code?
https://smalldev.tools/share-bin/xQdU0FEb

stiff urchin
#

move the variables block under the actions key
i.e.

actions:
  - variables:
      light_entity: light.deckenleuchte_und_hue_iris
      sensor: ...
rocky fjord
#

i dont really get this, can you explain pls? Shouldnt variables be defined at the beginning?

#

i changed it as you said. will go try it out now

#

this seems to have broken it 😦

stiff urchin
#

how so?

#

what's it doing/not doing? what does the trace say?

rocky fjord
#

maybe an issue on my wifi settings

#

when reverting the setting and double checking it did not do it in the first place either

#

give me a min

#

nope, this way it just does not do anything. Blueprint gets triggered but is not turning the lamp on

#

maybe i did a mistake, will check again

#

alright this should work now, its triggering it. I am going to have a look at the light now to see if it still sparks to 100% brightness

#

Alright so what happens is: When it gets triggered it always uses the last brightness from the last time it was turned on

#

how can I change this?

uncut cypress
#

Hi @rocky fjord
Level 1 could be out of the range of the light and it doesn't know what to do with it. Start at level 10 or something.

rocky fjord
#

will try, ty!

#

is it possible that it does not understand 1-255 maybe? Needs 1-100 %?

undone robin
#

brightness expects 0 to 255

#

In the light.turn_on action you can also use brightness_pct

rocky fjord
#

I think starting with 20 did the trick!