💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

[Blacky]

@dimatx

Hi Dima

@dimatx

Thanks for your contributions.

No problem.

@dimatx

I have a few helper toggles that allow me to easily turn my light automations off for the whole home, per floor, etc. So, my light automations always check that various toggles are ‘enabled’ before proceeding. A kill switch of sorts.

This can be done with the by-pass already + more

@dimatx

I was thinking the newly added condition selector could work great here:

I had a look at it today, but unfortunately I had to roll back as there was a bug in the release for me. Hope they fix it.

When I add a condition I make sure it works through the whole blueprint. Example;

By-pass (helper toggles or a kill switch): If you just added a condition it would prevent it from running. I have made sure it will do more. You have options when you turn the bypass ON and when you turn it OFF it analyse your automation and reacts correctly. So The bypass will prevent the automation running but let say you would like to turn on a helper (bypass / kill switch) and if any light are ON turn them OFF too. This will do that. But the other light you would like ON, no problem. What happen when you come home and your motion group is ON and you turn the bypass OFF. This will check that and turn your lights ON if required.

Sun: If you put a condition it would prevent it from running. I have made it analyse your automation and it reacts correctly.

Ambient: If you put a condition it would prevent it from running. I have made it analyse your automation and it reacts correctly. You also have more options.

A new one is coming out in the next release that I realy like. I have more on the road map to.

So the conditions in this blueprint do more that just prevent it from running. It all works together to analyse your automation with a simple click. You can use none of them or all of them. Code goes through the whole blueprint for this to happen. Condition selector will not do this.

The condition selector could be added and would say it probably will. If I add it now everyone would have to have the latest HA, and I don’t have it yet.

If you find that you cant do something let us know as I do add a lot of suggestions.

PS: I also added a sensor light add on blueprint. For anyone else reading this, a bug was fixed so check it out and update. It links to this automation so you can have, movie lights, smoke detector light, alarm lights. Be sure to check this out.

Sensor Light Add On - Media & Movie Lights - House Alarm Lights - Smoke Alarm Lights & Exhaust Fans + More

[chrismelba (Chris)]

Thanks Blacky, my settings look to me to be the same as yours, but I cover the sensor, lux goes to 1 and the lights turn on, I uncover the sensor, lux goes to 87 but the lights just stay on. Is this expected?

Here is my yaml

alias: Living Sensor Lights
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.anyone_home_sensor
    light_switch:
      area_id: dining_room
      entity_id:
        - light.dining_table_light
        - light.dining_wall_light
    include_ambient: ambient_enabled
    ambient_light_options: ambient_light_option_disabled
    ambient_light_value: 37
    include_time: time_disabled
    after_time: "10:30:00"
    before_time: "23:00:00"
    include_sun: sun_disabled
    include_zone: zone_enabled
    zone: zone.home
    night_light_transition_on: 4
    night_light_colour_temperature: 4500
    include_bypass: bypass_enabled
    motion_bypass: input_boolean.bedtime
    ambient_light_sensor: sensor.living_room_lux_illuminance

[firecat8]

I’m about a week into being a HA user - and absolutely loving this blueprint. I’m hoping someone can point me in the right direction on this situation:

I have a door sensor, and a motion sensor in a hallway outside the door. The door is always closed (except for passage), together they should allow me to infer which direction someone is traveling. Aka - turn lights on in bedroom if motion sensor triggers then door sensor triggers, or turn lights on in hallway if door sensor triggers then motion sensor triggers.

I think I understand enough about automations that I could create this automation as a standalone, but I specifically like ALL the options already in this blueprint. So is there an easy way to create something this blueprint would still recognize as a “binary sensor” that is based off the sequential order of two other sensors?

I’ve created groups for other applications already, but that doesn’t have the sequential nature. I also understand I can add lots of options to my own custom automation triggers, but I don’t understand how to make those then report as a binary sensor for this blueprint to read.

As with most things HA I’ve encountered so far, I am guessing this is much easier than I am making it out to be, and I just need a little help getting pointed in the right direction. Thanks!

[Blacky]

@chrismelba

Hi Chris

Thanks for providing your YAML it makes it easier to resolve.

I will jump to the problem and then answer your question.

In “Lights - Switches - Scenes” you have entered in a “Area” called “dining room”. We can’t use areas or devices and it must only be entities. I am amusing that your lights “dining_table_light” and “dinning_wall_light” are the only lights you would like to control. If so remove your area “dining room” from the automation and you will be good to go.

In the “The Settings & Best Practice Guidelines” Click Here see under “Lights - Switches - Scenes” for a better explanation on this.

@chrismelba

I cover the sensor, lux goes to 1 and the lights turn on, I uncover the sensor, lux goes to 87 but the lights just stay on. Is this expected?

No, but a few things are also considered in the automation for this condition and option selection

If your trigger is ON then this happens. If you cover the sensor and it crosses over your setting (high to low) then the light will turn ON and your trigger is active. If you then remove the cover from the sensor and it crosses over your setting (low to high) the light will turn OFF after your “Time Delay” setting.and trigger is disabled.

If the trigger is OFF the light will not turn ON if the sensor goes from (high to Low) and from (low to High) it just allow the trigger to be active when it is below your setting so the lights can turn ON if triggered.

If the trigger is ON and you cover the sensor and it crosses over your setting (high to low) then the light will turn ON. If the trigger then goes OFF it starts the time delay from that point. If you then remove the cover from the sensor and it crosses over your setting (low to high) and the light is still ON the light will still turn OFF and your trigger is disabled.

There are more scenarios but I think you get the idea. There are so many to consider in this automation and this is just one option with a few scenarios .

Idea is you just don’t notice anything behind the automation and it just works

Let us know if this solves your automation.

[Blacky]

@firecat8

Firstly welcome to the community.

I understand what your trying to do but running through some scenarios in my head.

Scenario 1 - Motion sensor in the Hallway

1. When motion is detected, hall light turn ON - Done
2. If you are in bedroom and you walk out into hallway motion detected hall light ON - Done
3. If you are in hall way entering bedroom motion detected hall light ON - Done.

All option covered with just motion. Light turns OFF when motion is not detected.

Scenario 2 - Bedroom Door sensor.

1. In hallway enter bedroom (door sensor), bedroom light ON - Done
2. In bedroom enter hall open door bedroom light ON, but it should be ON already as you could be in the dark - Not Done

Questions:

• What turns it OFF?
• Do you leave the door open when you would like the light ON and then close it to turn the light OFF? If so then that would work

Scenario 3 - Bedroom Door sensor. If the door is the trigger then it just works of a time delay. Door is open and closed.

1. In hallway enter bedroom (door sensor), bedroom light ON after some time light OFF - Done
2. In bedroom enter hall open door bedroom light ON…, but it should be ON already as you could be in the dark, so you have manually turned the light ON already, ok. so we leave bedroom close the door light is ON after some time light OFF - Done

This seems to work but only for a short time

Scenario 2 & 3 seams unresolved Would a motion sensor be better for a bedroom (Room) as door sensors work well for cupboards or small rooms like food storage, clothes rooms etc.

Maybe I don’t fully understand what you are trying to do in its entirety.

Blacky

[chrismelba (Chris)]

@Blacky

If your trigger is ON then this happens. If you cover the sensor and it crosses over your setting (high to low) then the light will turn ON and your trigger is active. If you then remove the cover from the sensor and it crosses over your setting (low to high) the light will turn OFF after your “Time Delay” setting.and trigger is disabled.

Is this saying that I would have to leave the room (presence clear) before the lights would turn off? I have a main room that can be used all day. What I would like is that in the morning when it is still dark the lights will turn on, but as the sun rises (and the lux value goes low->high) the lights would turn off, even though I’m still in the room. Is that the intended behaviour? I removed the room from the lights, they still turn on when lux goes high->low, but as long as I’m in the room they just stay on forever.

[Blacky]

@chrismelba

I removed the room from the lights, they still turn on when lux goes high->low, but as long as I’m in the room they just stay on forever.

The should go off

can you give me your YAML now.

[chrismelba (Chris)]

Of course, here’s the one where it would not turn off when the lux went low->high with presence

alias: Living Sensor Lights
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.anyone_home_sensor
    light_switch:
      entity_id:
        - light.dining_table_light
        - light.dining_wall_light
    include_ambient: ambient_enabled
    ambient_light_options: ambient_light_option_disabled
    ambient_light_value: 37
    include_time: time_disabled
    after_time: "10:30:00"
    before_time: "23:00:00"
    include_sun: sun_disabled
    include_zone: zone_enabled
    zone: zone.home
    night_light_transition_on: 4
    night_light_colour_temperature: 4500
    include_bypass: bypass_enabled
    motion_bypass: input_boolean.disable_sensor_lights
    ambient_light_sensor: sensor.living_room_lux_illuminance

[Blacky]

Can you set a delay time and save. Default is 5 min so can you set it to 1 and test it then you can go back to 5 and test it. Thanks.

[Blacky]

New update 4.3

New Features

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

Enjoy

Blacky

[oOWaXOo]

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.

@Blacky

Version: 4.3 - 9 July-23

[Blacky]

@oOWaXOo

Thanks for that awesome work and constantly improving this blueprint!

No problem, there was a lot of work (code changes) in this release.

@oOWaXOo

Just a minor thing i want to point out there is a typo in the change log date of V4.3.

All fixed

[oOWaXOo]

@Blacky

No problem, there was a lot of work (code changes) in this release.

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.

@Blacky

All fixed

awesome!

[andyblac (Andy Blackburn)]

this integration can do 'Time Travel` as well

[Blacky]

New update 4.4

Bugs Fixes

• 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

Enjoy

Blacky

[chrismelba (Chris)]

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

[Blacky]

@chrismelba

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.

Good news!! If it work then I take that

@chrismelba

Thanks so much for all the time you put into your automaton blueprints

No problem at all, your welcome. Thanks for letting us know

Enjoy

Blacky

[dimatx (Dima)]

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.

[hassuser99]

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)

YAML:
alias: Motion - Closet Mommy
description: “”
use_blueprint:
path: Blackshome/sensor-light.yaml
input:
motion_trigger:
- binary_sensor.lumi_lumi_motion_ac02_iaszone_5
light_switch:
device_id: b81a458eeafb2b29e1e02a4aab11ae66

[Blacky]

@hassuser99

In “Lights - Switches - Scenes” you can’t use areas or devices. You will need to expand down to entities.

Please see “The Settings & Best Practice Guidelines” Click Here as it will guide you on “How To”

Blacky