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

valiksheva · November 2, 2023, 9:09pm

Thanks for reply.

By-pass is definitely a cool feature but it does function completely opposite of what I’m trying to achieve here:)
I want my switch function just the same as if the sensor detected movement, that’s all.

Blacky · November 3, 2023, 6:05am

@Anaconda

You could try this if you are keen… note I have not tested and just did the code here quickly. This is my thinking.

Create a button helper… when you push it, it will turn on the new sensor if the total room sensor is ON. Then when your total room sensor goes OFF your sensor light automations time delay starts. I put a delay of 30 seconds just to give it a buffer if it comes back on but you can remove it or make it longer, like this for 10 minutes change the seconds to minutes in the template.

          minutes: 10

Create a your template binary sensor by adding this to your “configuration.yaml” file. Then restart HA or reload as shown below. You will have to change “input_button.your_button_helper_here” to your button helper entity ID and “binary_sensor.your_total_room_sensor_here” this is your entity id for the total room sensor. The “Button Motion Sensor” is the name of your new sensor… change it to your liking.

template:
  - trigger:
      - platform: state
        entity_id: input_button.your_button_helper_here
      - platform: state
        entity_id: binary_sensor.your_total_room_sensor_here
        to: "off"
        for:
          seconds: 30
    binary_sensor:
      - name: "Button Motion Sensor"
        device_class: motion
        icon: mdi:motion-sensor
        state: >
          {{ is_state('binary_sensor.your_total_room_sensor_here', 'on') }}

Once done then group this new binary sensor with the zone motion sensor in each automation. So you will have say zone 1 + this sensor in a group, then zone 2 + this sensor in a group. Then add the correct group to the automation trigger for the zone (only this group in the trigger). Now when you push the button it should turn ON this new sensor in every group turning ON all your lights or keeping them ON and only when the total room motion detection goes OFF then this sensor will go OFF and your lights will turn OFF Nice hay No need for by-pass and your two automations… you only need this temple sensor.

To reload the template sensor if you make a change go into developer tools and click"template entities"

Hope it works… it should

Let us know if this works for you

Blacky

Blacky · November 3, 2023, 6:18am

A switch is not a motion sensor. You have to turn it ON manually and something has to turn it OFF.

So you could use the by-pass turn light ON with the delay to turn it OFF if you forget. When you turn the switch ON light will come ON or Stay ON and then the delay will turn it OFF if you forget to turn it OFF and your light will go OFF.

Blacky

Anaconda · November 3, 2023, 11:43am

Thank you so much for this. I will give this a try for sure and let you know !!

Anaconda · November 3, 2023, 1:13pm

Ok so I have just done it and here is the outcome

When I push the button, all lights come on and stay on while whole room presence is detected.
When I leave the room, the lights stay on for 30 seconds (I guess) and if no presence, turn off.
When I come back only the zone where I am in turn on, however, when I move from zone to zone, some zones now don’t turn on, (depending on which order I walk/change zones in the room, those which don’t turn on are different) while they were before in same conditions. I have ambient options enabled for all zones and checked that it is affected by lights.

Any idea what the issue could be ?

Thank you !!!

EDIT: So I have disabled the ambient options and now it all lights come on normally … I don’t know why it worked previously without issue and not now.

Blacky · November 3, 2023, 1:33pm

@Anaconda

Looks like the template sensor works

Try this to work out the bugs.

Disable ambient lights in all automations.
Add to your dashboard each zone and the total room detection + the new template sensor so you can look on your phone as you walk around to see what is being triggered. This way you can check the zones triggers to the automations.

Blacky · November 3, 2023, 1:43pm

Okay so now in your ambient light options try this.

Don’t select the site conditions to yes. Select “NO”. This is because one automation is effecting the other one.
When it is dark outside, turn all your lights ON 100% brightness and see what your ambient LUX sensor is . Say it reads 100 LUX. Then set your “Ambient Light - High Lux Value” to 120 lux and adjust higher if the light ever turn OFF when you would like them ON. Set all your automations to this. That is if your “Ambient Light - Low Lux Value” is a lower setting. The “Ambient Light - High Lux Value” must always be = or higher than your low setting.

EDIT: You will also need to play around with the “Ambient Light - Low Lux Value” to get that right so the other automation will trigger ON.

EDIT: Or you can select “YES” but your “Ambient Light - Low Lux Value” must be higher when all your lights are ON.

Let us know how you go.

Blacky

Anaconda · November 3, 2023, 2:07pm

Thank you very much !!! At least I know where the issue comes from, so I will play with the ambient light setup.

I hope some day you will create a blueprint for the Aqara FP2, it is a great presence sensor when it works, but needs a lot of knowledge to set it up. Without your help, I would have sent it back for sure !

Blacky · November 3, 2023, 2:13pm

No problem, your welcome.

If you have brightness control then forget about ambient and try and use the dynamic lighting in the automations.

Yea, maybe if Aqara is reading this they will send me out one.

Enjoy

Blacky

oleksii-kalinin · November 3, 2023, 3:01pm

Hey there.
Amazing job with so complicated blueprint. I’m trying to get it to work with the Aqara P1 motion sensor and I can’t. So I have configured the minimum required fields and I didn’t even get automation triggered.

alias: New Kitchen Lights
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.motion_kitchen_occupancy
    light_switch:
      device_id: cd4368f348b055e070ae573f246a9db2

Blacky · November 3, 2023, 3:05pm

@oleksii-kalinin

Firstly welcome to the community

You are using a device and you can only use entities so you will need to expand down to entities. Then it will work.

A good starting point is to read “The Settings & Best Practice Guidelines” Click Here.

Blacky

Adaaks · November 3, 2023, 3:09pm

thanks it works BUT i can only have one bypass option so either one button to turn it on or off… it doesnt sadly have a feature to toggle the bypass on and off with one button

oleksii-kalinin · November 3, 2023, 3:12pm

Thanks! (for the welcome and advice)
Changed to the entity and automation works.

alias: New Kitchen Lights
description: ""
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.motion_kitchen_occupancy
    light_switch:
      entity_id: light.kitchen_lights
    time_delay: 3

Blacky · November 3, 2023, 3:18pm

it should toggle the by-pass ON and OFF. What state is your button, what does it do when you push it?

Anaconda · November 3, 2023, 3:59pm

I am on 4.7 so don’t have the dynamic lighting option. I am looking into information on how to update the blueprint … Is there an easy step by step guide ? i never done it before …

Blacky · November 3, 2023, 4:11pm

@Anaconda

Yep it is easy and in the FAQ

Q: How do you update the blueprint and not delete / recreate existing automations?

A: Please follow these steps Click Here.

Anaconda · November 3, 2023, 4:25pm

thank you very much very clear, done in 2 minutes, easy peasy

About Dynamic lighting you suggested, I am now using scenes for lights, with the Hue natural light scene. Should I just let it like that ?

Edit: Sorry I just read it was not working with scenes.

Edit 2 : The way Dynamic lighting works is the contrary of what I have now, the darker it gets the more light/brightness you get, while with hue natural lighting for example the later in the evening, the less light you get.

Anaconda · November 3, 2023, 8:10pm

Blockquote

Now when you push the button it should turn ON this new sensor in every group turning ON all your lights or keeping them ON and only when the total room motion detection goes OFF then this sensor will go OFF and your lights will turn OFF Nice hay No need for by-pass and your two automations… you only need this temple sensor.

==== > The issue I have now with the above is that if I push the button, finish what I need to do with all the lights on, and turn off the lights, without leaving the room, the following happens

Lights turn on again, as presence is still detected everywhere.
I have to press a second time to make it turn off.
I can’t just go to sleep and make the FP2 work again if I wake up at night, lights stay off. I have to quit the room to make the new sensor turn off, and fp2 working again as usual.

valiksheva · November 4, 2023, 5:41am

In basic scenario, the sensor turns my switch ON, and then the switch turns off after a delay, right,? Basically what I need, is so that manual switching ON also has same delay as if sensor detected motion, and so that if motion is still detected the light will not turn OFF.

I think I can use By-pass, but then I will not have a regular by-pass (like when I need it to stay on for longer time), and it will turn OFF after the set period of time anyways, even if the motion is detected, right?

harryfine · November 4, 2023, 2:14pm

Blacky, I’m a bit confused about ambient light.

I have the following situation. I want to turn a light on with motion any time of day for 30 seconds from last motion, but only if the ambient light is below a certain level, let’s say 30. No night light option, no sun elevation. Also there is a bypass off when I set a boolean helper to nighttime.

But what does the ambient high value of 80 do? Does the light not turn OFF when motion is no longer detected? Why is there a needs for a high value?

alias: Front Hall Light on with Motion & Lumens
description: Front Hall Light on with Motion & Lumens
use_blueprint:
  path: Blackshome/sensor-light.yaml
  input:
    motion_trigger:
      - binary_sensor.front_hall_motion_and_occupancy_sensor_for_light
    light_switch:
      entity_id: light.front_door_dimmer_switch_z_wave
    time_delay: 0.5
    include_light_control:
      - use_brightness
      - use_transition
    light_brightness: 75
    light_transition_on: 1
    light_transition_off: 1
    include_night_lights: night_lights_disabled
    include_night_light_control:
      - use_brightness
      - use_transition
    night_light_transition_on: 1.5
    night_light_transition_off: 1.5
    night_lights_conditions: []
    night_time_delay: 3
    include_sun: sun_disabled
    night_lights_sun_elevation: -3
    include_ambient: ambient_enabled
    ambient_light_sensor: sensor.front_hall_motion_and_presence_sensor_illuminance
    ambient_light_options: ambient_light_option_disabled
    ambient_light_value: 30
    include_bypass:
      - bypass_enabled
      - bypass_enabled_stop
    include_time: time_disabled
    night_light_brightness: 20
    sun_elevation: -1.5
    motion_bypass:
      - input_boolean.day_night_mode
    motion_bypass_lights_stop:
      - input_boolean.day_night_mode
    after_time: "17:00:00"
    before_time: "07:00:00"
    sun_elevation_rising: -4
    ambient_light_high_value: 80