The same story my sensor notification in the kitchen at this moment 90 lx I set ambient light sensor on minimum 40 lux and max 400 lux lights whont on. They only turn on when the light sensor is completely covered. Main motion sensor/Trigger is presence sensor
Found solutiona long time ago I installed the adaptive light add-on I forget about this which automatically added my kitchen lights entity. I removed entity form Adaptive Lights and all works great.
I do have this on my list to do so it is on the road map but I donāt want to guarantee or give false hope to when this will happen. Thanks for you suggestion.
@Blacky I have about 30 Smart & Sensor BPs so far. Iāll have at least 50 by the time Iām at full production. One ask is a way built-into the BP to indicate when its in Bypass. I know we can monitor the bypass entities in a separate automation, but that is a lot of work, and a lot of additional automations just to monitor entities that only do 1 thingā¦ bypass your BPs. Having the BP itself set a Helper Entity would save a ton of work!
side note: it would be useful to have a āwarningā timeout where the lights fade down/up prior to the bypass timeout or (for Sensor Light for no motion timeout)ā¦ so the user would know they are running out of time.
IMO the best for everything is to combine Smart & Sensor BPs because the function difference between them is the initial trigger (motion, switch, etc ā which should not matter, its just a trigger). Then add the motion sensor option as a bypassā¦ when motion is detected, it restarts the bypass timeout.
ā this would combine all your functions into a single BP and provide the most flexible automation for lighting.
OK, back to the the initial thought. The way you put it is funny but, yesā¦ a single entity to hold bypass status for all Smart Light and Sensor Light automations. Use can quickly see which bypasses are on and have a one touch was to turn them all of off.
Think of this situationā¦
User is in a workshop/garage/office/etc
Want lights to stay on entire time
Motion sensors may not pickup motion due to the low-movement activity and/or location of sensors being blocked by cars, cabinets, etc.
both Smart Light and Sensor Light have this awesome ābypassā so user sets a physical zwave relay switch (like from a very popular Zooz double switch) to be the bypass.
bypass timeout is either completely disabled or set to 4 hours (the max allowed) because the user works long periods of time in that location and its important lights for not going out (cutting wood vs cutting fingers off ; soldering electronics vs 3rd degree burns!, etc)
ā¦ either the bypass timeout is not set, or when leaving, the user forgets to physically click the relay button to disable bypass. The lights stay on forever.
If there is a āstatusā entity showing that lights are in bypass, users have a single place (entity) to see status for all bypasses, turn all bypass off (manually or automation), and even provide notifications on after a given # of hours (6 hrs, etc)
Thanks for your suggestion, I will add it to the list.
It canāt happen as it works differently
Maybe have a look at my State Notifications & Actions. You can enter in your bypass and it will give you a notification that it is ON, You can even include an action button to turn it OFF.
I am going to release a Be In The Hive Sensor blueprint that you may like to use in your workshop/garage/office/etc as long as you have a door and a motion sensor.
Iāve been still operating a quite big automation on iobroker including lights and much more. Recently had a look on HASS and it impressed meā¦Now trying to find out, how to import my lighting automation, but havenāt found yet the right setup with your BPsā¦ Following use case:
ON (ambient setup):
Trigger by light sensor, if presence and awake (virtual switch)
Trigger by Awake (virtual switch), if light sensor
Trigger by Presence, if light sensor
LIGHTS: morning: white/50%, evening: warm, 10%
OFF: trigger by light sensor, sleep, absentā¦
Additionally there are some motion sensors, which trigger the lights to light up to 100% for some time - if no motion, the light should come back to the ambient light setup - the color of the light shall stay as it was setup by the ambient light (morning white, evening warm).
When I combine Smart light and Sensor light, I need to use scenes to come back to ambient light level, but then I canāt use dynamic light to change from cold to warm automatically. Same for conditions in Smart light, there is no option to activate the ambient light only if present or awakeā¦
Could you give an idea how to set it upā¦? There are much more use cases, but this is the one, where I stuckā¦ Thanks in advance!
@DariusM73 you need to create a few separate automations for each BP (Sensor // Smart). You have one āSensorā trigger so that needs to be separate unless Blacky adds that trigger to Smart Light. OR write a script to get the level of detail you want, you have a lot of variations there.
@Blacky this is a good example where is a Sensor trigger was added to Smart Light, Darius could use a single Smart Light automation for much of what he needs. You have said you cannot add a sensor to Smart Light but do not explain why. ou have the Sensor trigger in āManual Lightā. Essentially Manual Light BP could merged into Smart Light and Smart Light could have all that functionality. I also found that using Manual Lightās āsyncā feature can also eliminate the need for some Entity Groups.
To my engineer brain any Entity should be able to easily be a trigger (in this case, Occupancy = On) no different than any other.
I dont see any reason motion sensor could not be a trigger in Smart Lights. Its a binary, like all other triggers. You do a Trigger check and the result is True or Falseā¦ entity is on or off
sunrise or its not
time is 24:30 or its not
If you want to use a motion sensor in this blueprint to turn your light on and off, you absolutely canā¦ but keep in mind that the blueprint was not designed for it, as it relies on a fixed triggers.
However, you can use a motion sensor (dynamic trigger.) in night lights to temporarily increase brightness. For example, you could have the lights turn on at a fixed time and off at a fixed time, but when motion is detected, the night lights feature increases the brightness. Once motion is cleared, the lights return to their normal brightness.
In night light control, youāll find an option called Use crossover time delay from night lights to normal lights. This setting helps manage the transition from motion-activated brightness back to normal lighting. It prevents the light from dimming too quickly if youāre still in the area or if the motion sensor gets triggered again.
Use Case Example:
Your outdoor lights turn on at night at a low brightness. When someone approaches the front door or walks through a stairwell, the motion sensor detects movement and increases the brightness. Once the person leaves, the lights gradually return to their original dim level.
If for some reason you would like both option of the sensor light and smart light blueprint then you would use the sensor light blueprint.
Looking at the smart light blueprint the triggers are:
State: Just use the entity. Sun or Ambient: Template binary sensor (see below). Time: With the schedule helper, you have more flexibility than simply setting the light to turn ON or OFF at a specific time every day. It provides you with greater control and customization for your lighting schedule.
Code below for your template binary sensors:
To create a Template binary sensor, follow these steps:
Navigate to Settings > Device & Services > Helpers tab at the top.
Click the Create helper button.
Select Template and then choose Template a binary sensor.
Next, provide a Name and Device class of your choice. If applicable, you can link this template to an existing device so it appears under that deviceās details.
In the State template field choose your code below,
Sun Code
{{ (((is_state_attr('sun.sun', 'rising', false))
and (state_attr('sun.sun', 'elevation') < -1.5)))
or (((is_state_attr('sun.sun', 'rising', true))
and (state_attr('sun.sun', 'elevation') < -4.0))) }}
Ambient Code
This one is a bit trick as you need to create the template binary sensor first and then enter in the entity ID into binary_sensor.this_binary_sensor_id
Then if you wanted to use a motion sensor with one of the fixed triggers you would group your motion sensor and / or the entity state, a schedule helper or template binary sensor you created. Now you have fixed triggers and a dynamic trigger in one entity (your group). You then use this group in the sensor light trigger or just use the fixed trigger.
Sorry for confusion, let me try again:
I have indoor ambient lights, which get activated with a light sensor, but only, if we are at home. If not, the lights get activated, once we approach home, only if itās dark (light sensor). The ambient light is on 10% - and if there is a motion detected, the lights light up to 100% for 2min, then should return to 10%.
Then, when we go sleeping, a sleep helper changes from awake to sleep, and all the lights go off. if there is a motion in the night, lights get activated on 5%, then go off (night=dark + sleep helper). in the morning, the sleep helper goes to awake and the ambient light gets triggered with 10%, if itās still darkā¦ the lights finally go off, when the light sensor says itās bright. Additional: in the morning and evening the color of the lights is different.
Hope now itās more clearā¦ I would need some initial advises how to set it up, Iām afraid the combination of sensor BP, smart BP, helpers, templates ā¦ is too much for a newbieā¦
I ran into an obvious (with hindsight) problem this morning. I have some outside lights controlled using this blueprint that I have set to come on at a fixed time in the morning and off when the sun elevation reaches a certain point. This has been working perfectly over the winter, but this morning the sun was already above that elevation when the time was passed. So of course the lights came on and have stayed on. Just wondering what the neatest way to allow for this?
I could have it turning on and off based on elevation, but then I would have it coming on in the middle of the night.
Guess I just want to find the easiest way to say donāt bother turning on, if the sun has already risen?
but, yesā¦ a single entity to hold bypass status for all Smart Light and Sensor Light automations. Use can quickly see which bypasses are on and have a one touch was to turn them all of off.