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

Hi Blacky!
i have some questions for you:

  1. i have a 4-button switch in Z2M, but i cannot specify it’s buttons as a bypass. In Z2M, it seems that it only has a ‘action’ entity that tells whether button 1 was pressed or button 3 was held and so on, but i cannot find it or reference it in any way, in HA. I cannot choose the action entity as a bypass either. However, i can choose the automation that controls what the buttons do, but it doesn’t seem like that’s the right way to proceed. Is it possible for me to still use that as bypass? If so, please tell :slight_smile:
    From Z2M exposes:
    billede
    From HA:

  2. In my bathroom, i have 2 separate lights that are both controlled by the same automation, one in ceiling and one by the mirror. The ceiling light is bright, so i always set that at about 70% which means that the mirror light is also turned on at 70%, since brightness cannot be controlled individually. The problem is that the mirror light is not too happy about being brightness controlled and will make a high-pitched screeching noise while not being at 100%. How can i control the brightness level of the two lights individually, while still using your automation?

  3. In the Bypass section, you mention that one should not use the same entity in more than one bypass option. I have a shelly relay attached to one of my lights and two physical, spring-loaded switches, effectively only giving me one input per switch (which is toggle). The switches are both connected to the same channel on the shelly relay and both are used for turning on and off. Im not sure how to make the automation understand correctly that i just turned on (or off) the lights manually. Any advice?

I’ve been looking through your documentation, but haven’t been able to find answers for these questions. I hope you’re willing to help! Thanks for all your time, the effort and your help! :slight_smile:

I think you need a binary sensor. You can create another helper, a template binary sensor, that mirrors the value of the first helper, then use this template binary sensor in the blueprint.

Or alternatively, you can skip the automation and just use the template binary sensor, writing the 3 minutes rule in the template. Ask ChatGPT or Gemini for help on how to write the template, they’re great with this kind of requests.

I went ahead and asked myself. This should work, just change “motion_sensor” to the id of your motion sensor.

{{ (states.sensor.motion_sensor.state == 'on') and 
           (as_timestamp(now()) - as_timestamp(states.sensor.motion_sensor.last_changed)) > 180 }}
1 Like

Thank you - it´s working!

1 Like

hi @Blacky ,
huge fan of your bluebrint, just saying cause I usually come here with errors.

One of my blue prints topped working. I get an error at the step where there is a first " choose"

Error: UndefinedError: ‘homeassistant.util.read_only_dict.ReadOnlyDict object’ has no attribute ‘brightness’

What could this be?

edit: I found it but can’t solve it. IN teh automation config screen (traces) it still shows an old switch as an entity. Is there a way to remove this?

edit 2: This didn’t seem to be the problem,
I remade the automation by coping the correct automation config.
I gives an error:

Stopped because an error was encountered at January 6, 2025 at 3:35:34 PM (runtime: 104.91 seconds)

@Icecoke7

You will have to create a template binary sensor and add it to your config file. I have a FAQ for this click here for more information but your code is below.

It is similar to REF - TS-2

Once you create it add it into the trigger.

template:
  - binary_sensor:
      - name: 'Dinner Table Delay Motion'
        device_class: motion
        icon: mdi:motion-sensor
        state: >
          {{ is_state('binary_sensor.your_motion_sensor_entity_id_here','on')}}
        delay_on:
          minutes: 3

Blacky :smiley:

1 Like

@Strux

  1. Your entity must have an ON / OFF state. Normally buttons can have no state or a quick ON / OFF. You will have to try and make the button toggle a toggle helper. You could try this blueprint and see if it works then use the toggle helper in the bypass. :nazar_amulet: Press Button - Turn ON & OFF Entities
  2. This is the perfect use case for a scene. Create a scene with your ceiling and mirror lights and adjust the brightness on each entity to your liking. You will then need to create a toggle helper and another scene with everything OFF. Look in the Lights section on were to put everything so it works well.
  3. Have a read of the FAQ on bypasses. It explains everything, click here

Blacky :smiley:

@victoroos

Maybe just start with a fresh automation and enter in all your entities and adjust your settings rather than copy paste.

Blacky :smiley:

Hello @Blacky

I wish you an happy new year.

I’ve tried many different options, but I’m sorry I can’t figured out how to prevent the automation to turn off the lights (never), if they were already on. I tried using “bypass options” with an helper activated when the scene is activated, but never found the right configuration.

I have a couple of lights and a motion sensor.

What I want is :

  • Let the user control the lights using a scene
  • Between 10am and 20pm, if occupation turns on, and the luminosity is under X lux, turn on the lights during Y min)
  • If the lights are off, turn on the lights, if the lights are already on : do nothing !

Any help will be appreciated !

@Hugoliv

Could you please provide us your YAML of the automation… the best one you have configured? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.

Blacky :smiley:

@Blacky

Thanks and this worked as you suggested.

Sorry for all the questions, but I might have one more ask.

So I created the group sensor Other Zone, Desk Zone and Rack Zone.

I have the Other Zone as Cool White and the Desk Zone like you suggested as the night lights with warm white. If I wanted the Rack Zone a different color of lights how would I implement that? I am pretty sure I am getting a little more complex and probably would need a script or something

Thanks for you help

Thanks @Blacky, here is the YAML :

alias: GC Day
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.motion_gc_occupation
    light_switch:
      entity_id:
        - light.top_gc
        - light.desk1
        - light.desk2
    end_scenes: []
    time_delay: 0.1
    light_transition_on: 3
    light_transition_off: 3
    include_ambient: ambient_enabled
    ambient_light_sensor: sensor.motion_gc_eclairement
    ambient_light_options: ambient_light_option_enabled
    ambient_light_value: 4
    ambient_light_high_value: 300
    after_time: "10:00:00"
    before_time: "20:00:00"
    include_light_control: []
    include_time: time_enabled
    include_dynamic_lighting: disable_dynamic_lighting
    boolean_scenes_scripts: input_boolean.gc_day_helper
    include_night_lights: night_lights_disabled
    night_lights_conditions: []
    night_lights_after_time: "20:00:00"
    night_lights_before_time: "10:00:00"
    include_bypass:
      - bypass_enabled_stop
    include_bypass_auto_off: []
    motion_bypass_lights_stop:
      - input_boolean.gc_scene_activated_helper
    bypass_auto_off_delay: 1
    bypass_time_delay: 0
    motion_bypass_lights_off: []
    motion_bypass_lights_on: []

Well, here is the best I have: the helper is turned on when the scene is activated, but it’s not disabled when the lights are turned off (using the voice or the dashboard). So the automation only work while the lights aren’t turned off manually. If so, the automation never turns on the lights again.

If I use the “Enable the auto OFF for the bypass switch”, the automation turns off the helper, and the lights (I don’t want this, I want to keep the lights on if they were activated by the scene.).

Hi,
What may be the cause of having the very same automation work with a Hue Go but not with a hue TV Gradient Stripe ?
I am just changing the light targeted, works with the Go not with the Stripe…

Edit: after reading the docs, it only supports entities as lights and I was using a device…

1 Like

Hello @Blacky

I have tried your suggestion. The script for switching off is running. But if there is a new motion detected while this script is running, the light switches to 100%, but the script keeps running in parallel and turns off the light at the end.
Do you have any idea how I can avoid this behavior? How to cancel the script?

@Blacky thanks for the answer! :slight_smile:
I will try your recommendations. However, i have one additional question: When i have created a scene and a toggle helper, shouldn’t i… like connect those two somehow? like reference the toggle helper in the scene or something else? Or is it enough that i just add both in the same automation, and then the automation knows that the toggle helper is created to help toggle the scene?

@shunopoli

Thanks for letting us know.

Yep, you have to create a scripts.

Blacky :smiley:

@Hugoliv

The automation will turn ON 3 lights if it is after 8pm and before 10am (at night) and only if the ambient sensor is below 4lx and once ON it will disregard your ambient sensor.

If you have a scene and you turn it ON and you don’t want the automation to run / take over then yes use the bypass. In the scene add the bypass to it and turn it ON in the scene. This will disable the automation. You will have to make sure when your turn OFF the scene that you also turn OFF the bypass… you could use the auto OFF in the blueprint if that works for you.

I think that is what your asking.

Blacky :smiley:

@b_tton

You will probably have to use the motion sensor as a trigger to stop your end script.

Blacky :smiley:

@Strux

No the toggle helper is used for the scene status… see scenes have no ON or OFF state and we use the toggle helper for this. It makes the automation run correctly… all you need to do is create a toggle helper just for this automation and add it into the input Scenes & Scripts - Toggle Helper. Remember you will have to create an identical scene with everything OFF and enter it into Scenes - Scripts To Turn OFF so you lights turn OFF.

Blacky :smiley:

New update 7.6

Your lighting experience, your way – take control and customize it to perfection! :bulb::sparkles:

New Feature :new:

  • Dynamic Lighting - You now have 4 new time controlled options. If you live in the far north or south, using sun elevation may not be practical during winter or summer, as daylight hours can be very limited or constant. These new options can help simulate a normal day of artificial lighting, providing a more consistent experience for those without typical daylight patterns. As always, you have full control to customize the settings to your liking.

:bug: Bug Fixes

  • Fixed a bug in Dynamic Lighting cross over from night lights.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

1 Like

Unbelievable Blueprint. Thanks for another refinement.

This Blueprint is the most active in Home Assistant. Bkacky spends so much of his time supporting users. Please buy him a couple of coffees.