Default turn-on brightness/color temperature for lights

Blueprints Exchange
,
41

Thanks for letting me know! I made a mistake with an indent and just fixed it.

42

Itā€™s now ok, can install the Blueprint without problems. Thanks much for your very fast fix :wink:

43

Hey there, does anyone else has same problem that the light turn on by this automation? cant use this anymoreā€¦

44

Hi there @derkorte what exactly is the issue? Can you say more about it? Iā€™m currently using the blueprint without any issue.

Maybe include info like: what version of home assistant, what type of lights, etc.

45

Hey, sureā€¦
Core 2024.12.2
Supervisor 2024.11.4
Operating System 14.0
Frontend 20241127.7

Running on pi5 as os

Problem: when I create an automation with these blueprint it takes about 1 or 2 mins that the configured light or group turn on without a trigger. The logs says turned on from automation xxā€¦ When the automation is switched of, itā€™s fixed.

Light type doesnā€™t matter, same problem in
Lights, switches groups or wled devices

46

When you toggle or change the lights with a different automation (like a switch or something) is there any delay?

47

No, thereā€™s no delay.
When I set the bulb to red and turn it off and on again, it turns on in red and instant changes to configured color from blueprint.
But the lights also turns on by itself.
The log is: light turned on

48

Hello there, and thank you for this Blueprint. Iā€™ve been using it for years now. However, recently I have begun using an add on called hass_scene_presets, which allows me to use Hue-type dynamic lighting scenes on groups of lights. Iā€™m noticing that this blueprint seems to fire upon any state change to the light? Not just a turn on state change? For example, the hass_scene_presets runs a dynamic lighting scene that has the bulbs changing colors every 30 seconds or so, with a gradual transition etcā€¦ Appears this blueprint triggers every few seconds when this is running. Is that because of how this blueprint considers state changes to trigger? Or is that because of how the other add-on sends state change commands to the groups of bulbs?

Thanks again!

49

Upon further investigation, appears this happens because this blueprint triggers on any state change to the light. While it triggers on any state change, the conditions only take action if the state changes from off. So no action is taken in my case, but it triggers hundreds of times when running a scene on lighting that changes lighting parameters.