But the blueprint doesnt allow the addition of data when using a script as Target Entity. Maybe an option could be added there.
ex:
description: ""
use_blueprint:
path: freakshock88/motion_illuminance_activated_entity.yaml
input:
target_entity: script.light_transition
target_data: {} # this option could be added to allow sending data to the script
motion_sensor: binary_sensor.motion_wc
thank you Blacky for this nice blueprint, which is full of useful features.
My question: I configured a night scene/night brightness for our kitchen light. In some occasions i want the light to be brighter, so i adjust it with a dimmer switch, or select a brighter scene with a physical switch. If the sensor gets the next occupancy it goes back to the night scene/night brightness, this is happening every 10 or 20 seconds.
Is there a way to leave the light at the brighter scene/brightness status for at least the time of the configured time delay ?
Thanks for your question. I have been thinking about this and you got me thinking again. The only thing I can see being a problem in the development of this new feature is when we use scenes as they are a different beast.
Currently without using the by-pass, no.
Not promising anything but let me look into it further.
Update: I have had a look at it and as expected scenes are a beast. I am going to push out a new release soon once all the testing has been done but scenes are yet to be resolved. I will continue to work on it so stay tuned.
Manual control of lights once they are ON. You can now manually adjust your lights once they are ON and they will no longer be reset to the automation settings on every trigger. The manual setting will remain this way until the lights are turned OFF manually or by the automation. Once OFF, the next trigger will reset the lights back to the automation setting. This will hopefully deliver a better user experience.
The new feature will work with lights and switches. We included switches just in case you have lights on switches that can be manually controlled once they are ON.
The new feature doesn’t work with scenes, and is a known issue. Work will be done to try and resolve this.
Breaking Change
When crossing over from normal lights to night lights and from night lights to normal lights. If the lights are ON already, they will remain in the state they are in until the lights are turned OFF manually or by the automation. Once OFF, the next trigger will reset the lights back to the automation setting. Light control will no longer adjust the lights to the new setting when this happens. This may be a preferred option anyway as you could be up later on the odd occasion and would like the lights to remain as is. If different lights are selected, the different lights will still turn OFF so the lights don’t remain in the ON state once the automation times out and turns your lights OFF.
usecass 1.
When I bring my kids to bed and open then the dor, the multisensor trigger the light and than she are awake.
usecase 2.
if friends are here, the light trigger always in the anteroom
You also have a few options on what to do if light is on when you turn the by-pass on. I would say for the bed one you would select “Enable the By-pass - If lights are ON, turn lights OFF”. This way it will turn the lights off.
You also have a “By-pass Time Delay” setting. If you set it to “0” it will turn the lights off instantly.
Sorry for the delay in replying, but life got in the way! This suggestion worked fine since I set it up in one room a couple of days ago. I’ll keep a eye on it for a while, so thanks for all the suggestions!
Pat
Just like the night light option, for the Lux option I want to define which lights are affected by Lux. In my office I have two lights I always want on if I’m present, but I have two lights that I want controlled via Lux. Otherwise this is perfect!
The easiest way to do this is to have 2 automations. One for your two lights when you are present, and the other one to control the two other lights with present + LUX. Just simply use the blueprint again to create the other automation, when you click save just name it different. That is one good thing about blueprints you can create a lot of automations using just one blueprint.
Again You’re Awesome. This Blueprint should just be part of HA default install. This blueprint is making my Aqara Fp2’s even better.
Still No donation link or did I miss it?
