Added the ability to use another condition in night lights called âEntity Stateâ . Night lights have 3 conditions now.
Entity State
Time
Sun Elevation
The entity must have an ON state to activate nigh lights. So now you can use âDo Not Disturbâ on your phone, a helper toggle, a switch near your bed, a bed sensor etc to activate night lights. More information can be found in our FAQ or Click Here for more information.
Bugs Fixes
Fixed an error when transition was disabled like shown below. This was probably when you are using zigbee2mqtt.
Transition value 0 is not valid.
If you like this blueprint? Consider hitting the button in the top post
If you like my blueprints, and would like to show your support or just say thank you? Click Here
Thanks for that awesome work and constantly improving this blueprint!
Just a minor thing i want to point out there is a typo in the change log date of V4.3.
Thats great to hear, i faced issues with the combination of yeelight and nightlight functionality previously. Let me check tonight if this is gone now. If not iâll come back and post my logs.
Fixed an bug in crossover transition from ânight light to normal lightsâ and from ânormal light to night lightsâ using wrong transition selection.
If you like this blueprint? Consider hitting the button in the top post
If you like my blueprints, and would like to show your support or just say thank you? Click Here
Well seeing as youâve released several new versions while weâve been talking I decided to update to the latest, delete the automation and start it from scratch and it works! Shame we will never get to the bottom of the problem, but Iâm happy that is working perfectly now. Thanks so much for all the time you put into your automaton blueprints
Thanks for your reply and explanation, @Blacky. So in my case I have a variety of âkill switchesâ for each automation. Stuff like âdisable downstairs light automationsâ, âguest modeâ, etc. It looks like with the current blueprint you can have just a single by-pass? Based on your description of by-pass, seems like that would be sufficient when it comes to achieving my kill switch functionality, but I am constrained by the limitation of allowing only a single entry.
I recently upgraded the blueprint and am seeing an odd error. I did just try to delete the respective automations, delete then re-add the blueprint, and add back one automation.
error:
Error rendering variables: UndefinedError: âdict objectâ has no attribute âentity_idâ
(Source: components/automation/init.py:608)
Thanks for your suggestion âMore Than One By-passâ. I will add it to the list.
For now you could and âentitiesâ card to your dashboard with a top toggle and name. This will turn ON and OFF any entities in the card. You could have one for downstairs, guest, upstairs, all light automations, all automations. It will be easy to manage then.
You could also use areas but name them how you like example area name âLight Automations Downstairs - By-passâ Then put all your by-passes in that area and you can turn on and off areas in automations.
Thanks, everything is working again. I am not sure what version I upgraded from, but I changed all the previously working ones from âdeviceâ to âentityâ and everything is working as expected again.
This is my go-to blueprint by far!
My next attempt will be trying to use a humidity sensor (set as a binary sensor helper) to leverage as my âbypassâ device. (Am not asking for assistance, as I prefer to tinker and figure it out on my own first). But too often my wife yells at me when sheâs in the shower and the lights go off on her.
Thanks again! And another ask to add to your list⊠Would be great to be able to use a template value for brighness + color. This would make this blueprint work better with âAdaptive Lightingâ integration on HACS.
If you are not sure what version you came from if it is not to much trouble I would recommend a clean install of your automations. This way it will clean up any existing YAML configerations that may cause problems.
In the FAQ under " UPDATES OF BLUEPRINT" it will list all the things that were needed to be done. But again if it has been a wile sometimes it is easer to just redo the automations
Yes this can be done, but I respect you would like to tinker and try and work it out. In any case if you run into troubles just post a message and I will be happy to help. There is one thing I will say, if you havenât checked out my Bathroom Humidity Exhaust Fan then it is realy worth a look. There are 2 blueprints I realy like, this one and the Bathroom Humidity Exhaust Fan blueprint. I think they are a must have, and spoiler alert I am working on the Bathroom Humidity Exhaust Fan blueprint now.
I donât use Adaptive Lighting, but I know a lot of companyâs are including it, like Apple, Philips, etc. I think they do all the hard work and all you need to do is to turn the light ON and it will adjust as required. Maybe I should look into it further to get a better understanding.
. Youâre correct about how adaptive lighting works. The reason being able to use a template in your blueprint for brightness/color etc, is that currently, the light will turn on with defaults and then adaptive lighting will adjust it. That adjustment is noticeable. If I can use the adaptive lighting desired brightness, color etc, then your blueprint can turn it with the desired parameters and avoid the immediate adjustment by Adaptive Lighting.
This looks like it may be an âadaptive lightingâ or the lights your using bug, issue or setting. When you donât choose any lighting control options in this blueprint, the light will just simply turn ON with no lighting data input .
Not sure of the lights your using or if there is a setting in âadaptive lightingâ but maybe there is a setting that is âRestore previous light setting when turned OFFâ that you can untick. A lot of lighting controls sometimes have an option like this. This way the light will get new data every time the light tuns ON . Maybe have a look around for this.
Hey Blacky. The behavior youâre describing is exactly the current behavior. However, itâs not the desired behavior When the blueprint turns on the lights it has two options (no lighting data input or static lighting data input). (Excluding the night mode). However, the desired result is to turn lights on with dynamic lighting data provided by another entity. For example, at 5pm, the temp may be 3000K, at 6pm it may be 2900K and at 7pm it may be 2800K. So the desired result is for the blueprint to be able to pass in a variable value for lighting data. Does that make sense?
I use Blackyâs blueprint and the same HACS adaptive lighting. It works just fine for me, except that the adaptive lighting settings kick in about 1 second after the lights turn on. So if itâs late at night, for example, lights will come on full brightness then a second later adaptive lighting kicks in and changes the color and brightness. Not completely seamless, but it hasnât bothered me.
. Night lights have 3 conditions now.
button in the top post 
. Maybe have a look around for this.
When the blueprint turns on the lights it has two options (no lighting data input or static lighting data input). (Excluding the night mode). However, the desired result is to turn lights on with dynamic lighting data provided by another entity. For example, at 5pm, the temp may be 3000K, at 6pm it may be 2900K and at 7pm it may be 2800K. So the desired result is for the blueprint to be able to pass in a variable value for lighting data. Does that make sense?