Thanks for the quick reply. I am fairly certain that this sensor gives the lux:
And tried the dynamic_lighting_min_brightness: 2 anywhere from 0% to 10% without any changes. The only time I get this automation to trigger now, is by restarting HA, then it triggers on the boolean I guess. Well, well… guess I have to sit in the dark (pun intended) a little while longer
Can you try this. Disable dynamic lighting and in light control enable Use Brightness and set the brightness to 50%. What I am trying is to see if the boolean will turn the light ON at 50% without dynamic lighting and your LUX sensor. Below is your YAML with the adjustments.
Okay that is good. It tells me that your boolean, lights and brightness works.
I have added the sun elevation as your LUX sensor. Hope you have this entity in HA if not can you use a temperature sensor rather than the lux sensor. Just copy the entity ID of your temp sensor and paste it in the Dynamic Lighting - Ambient Light Sensor.
I also removed your helper and I am trying to testing your LUX sensor.
Great work on this blueprint it catches almost all of my scenarios, thanks.
For my lights OFF I now use a random delay added to my switch-off time, is something like that possible?
Hello @Blacky and thanks for your comprehensive work!
I’m trying to create my automation but it does not adjust the brightness as I expect.
Can you spot what I did wrong?
Yep. I can see you are using Trigger - Ambient. The high you selected is to turn it OFF… the low is to turn it ON and you have not selected any trigger to turn ON (run) the automation. So you will need to decide what you would like to use.
I look at your dynamic lighting and you have a setting for 900 lux so I adjusted your YAML to turn ON (run) the automation using Trigger - Ambient low and the setting of 900 lux. I then set the high to 1000 lux and this is were it will turn OFF (stop) the automation. It may not be what you would like but it is just to give you a working example so change it as needed. What will happen is when the lux drops below 900 lux your light will turn ON and dynamic lighting will work. When the lux goes above 1000 lux the light will turn OFF. You may decide to use another trigger other than Trigger - Ambient so just change it to your liking. Below is your YAML. A tip is to use the “</>” in the menu of this text editor and then paste your YAML in there… it keeps the correct format. Try the below YAML in your automation.
Blacky many thanks for your tips, very much appreciated!
The thing is that I don’t want the light to turn on automatically but just to turn off in case it is on. I would like to switch it on only manually and then it should adjust based on lux sensor value.
I was also looking the bypass section but was not sure about how to configure this way.
Sorry for the late reply. Just got around to test with Sensor Light Blueprint and I can confirm it works!
I had to remove the filters from Triggers so that media_player.tv_living would show up. It’s not a sensor but can still be used.
Thanks again!
TIP: You dont need to remove the filters, you can just copy and paste the entity ID into the input and click save. If there is an update in the future you will have no problem with it…
@Blacky
I used it for holidays and when I’m not home as daily ending at the same time is to predictable for potential burglars. I only used it for the “switch off all lights” at a certain time.
Hi @Blacky. First of all, thank you very much for sharing all these great things. Really appreciated!
After some reading and research, my question is regarding the difference between your “Smart Light …” and “Sensor Light …” blueprints: How to decide which one to use? What is the difference?
Please accept my apologies if I missed a place where this was already explained. I searched for an answer but couldn’t find one.