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

I have a question to the lux-based options. My motion sensor (IKEA Vallhorn) is in a guest bathroom. There the lux value only rises up to 10 lux, even on a sunny day (see screenshot). Why is a value of like 2lx not possible for the e.g. ambient light sensing high/low value?

@DeckardCain2014

Just simply type the number in and click save. You can set 1.9 if you like totally up to you.

Blacky :smiley:

1 Like

ok if this works I’m happy :grin: Thanks for the quick reply :slight_smile:

Hey Blacky, I think I confused myself.
I want one light not going on when I enter the room at any time. But I want to switch it off when I leave the room.

Where do I configure that it is only turned off, not on.

In the answer to my first post you suggested to use a script…?

I have the same set-up. I want to only turn on two lights when i enter the room. But if i happen to turn on more lights while sitting in the room i want to turn off all lights in the room when I leave.

I managed to do this with two scripts.

Could you share your scripts pls?

Great work as always. Just wondering if is possible to implement making some of the settings collapsable? For example, I’m not using Dynamic lighting in the blueprint, so I can simple collapse all settings related to it, and expand if needed, it should be collapsed by default.

The blueprint is quite powerful and has vast amount of configurations on a single page. which can become overwhelming for some. Hope you understand, thanks.

1 Like

@seblor

Yep a script… example below. A guide on this process can be found Here.

If-Then-Else script into ‘Lights - Switches - Scenes - Scripts’ No toggle helper in ‘Scenes & Scripts - Toggle Helper’

If

Then

Else

Then create a scene with all light OFF and enter into ‘Scenes - Scripts To Turn OFF’

Blacky :smiley:

How can I add an offset for Sunset so lights come on 1 hour before sunset, and 1 hour after Sunrise? I tried tweaking the Sun Elevation either way, but it doesn’t do anything for me for some reason.

You can vote here Collapsible Selector Groups - #2 by Blacky

Blacky :smiley:

1 Like

@iona

Firstly welcome to the community :wave:

Please see the FAQ in this.

Q: Why did you choose sun elevation as the sun option and not sunrise and sunset, I don’t really understand the degrees and elevation, I assume zero is the sun just on the horizon with a + being day time and a - night time.

A: Please read our explanation and how to set it up, it’s easy :slightly_smiling_face: Click Here

Blacky :smiley:

Hi @Blacky first of all your blueprint looks amazing! Thanks you for sharing that with the community. As I am playing around with it, I came to the following issue:

My light gets turned on whenever there is motion and the illuminance is below the lux level I have set. One minute after the last detection of motion it turns off again as it should. However, turning on the light changes the illuminance measured by the sensor, which means the lights do not turn on again when I re-enter the room, because the illuminance is now too high for the automation to trigger. I tried to figure out if I could solve this by using the ambient sensor options your blueprint provides. Unfortunately, I was not successful despite reading the FAQ.

What I guess is missing is a cutoff value for the illuminance in the room, so the automation only runs when the illuminance is below that cutoff value, as well as an illuminance value that is not provided by the motion sensor itself, because then the illuminance would be affected by the light when the light is on. The illuminance value should instead be provided by a number helper which is basically a copy of what the motion sensor’s illuminance would be BUT only changes lux when the light is off (got the idea from here). This way you only get “real” values for the illuminance in the room without any interference when the light is turned on.

I hope I explained this in a way one can understand and am looking forward to your answer. :slight_smile:

@arne.conrad

Is your LUX sensor slow to react?

see ‘Ambient Light - Low Lux Value’

Select ‘YES - My Ambient Light Sensor is affected by the Lights’

If you like then to can create a template helper, then use that for your LUX sensor but when the light is OFF you will need to check LUX at quick intervals as you may close your blinds and the room gets dark. You could get a LUX sensor that reads fast and your problem is solved. See we need data to make things work if you would like it to respond quickly. If you had a LUX sensor that updates fast then everything works. The data is only stored for 10 days so you dont build a big data file thanks to the work from the HA Team.

I think all you need to do is tick the ‘YES - My Ambient Light Sensor is affected by the Lights’.

Blacky :smiley:

1 Like

Hi @Blacky you were of course absolutely right. My bad I got some settings wrong. Thanks for the explanation and your blueprint. This is absolutely amazing!

One final questions: Is there an option to completely block the automation from running at night? As far as I have seen, the night option only makes it possible to have different settings for the lights whenever the night condition is met, but it always means the lights will be ON in some way.

In my old automation, I used a helper that is activated whenever I say Good Night to Siri, resulting in the light automation being blocked. When I say Good Morning, the helper changed its state and the light automation would be active again.

Thanks!

1 Like

This is what the By-pass options can be used for.

I use my ‘Sleep Mode’ helper toggle to turn the lights off and stop the automation until the next morning.

Hope that helps!

2 Likes

Oh great, I did not realize this. I guess I have to read and try out more before asking questions :smiley: Thanks for your help!

Hey, thanks for this work, it’s really awesome especially for new users!
Is it possible to have by-pass inverse option or somehow do a workaround about this?
I’ll explain: i have voice assistant where i want to expose “Auto Kitchen ON/OFF” for example. So if it’s ON - script is working via motion detection, if i ask voice assistant “disable auto on kitchen” - it should work as “by-pass keep current state”.
I’ve tried to mess around with enable/disable automation at all via automation.turn but this one keep stalling or work not as i intended. Very new in this :slight_smile:

Ah great, didn’t realise it was a HA limitation, upvoted.

@Sk1vvy

Firstly welcome to the community and thanks for your kind words.

That is not a good way. If we use the bypass when we turn it ON we can make it do 3 different things and when we turn it OFF it checks the site conditions and tries to preform the correct action. Disabling and enabling and automation will do nothing other than turn it OFF / ON and wont work well.

If you would like the bypass to work in reverse then see templating in the FAQ. See REF - TS-7 and also read REF - TS-9 as this shows you an easy way to make a template.

Blacky :smiley:

Also have a look at this blueprint as it just out an may be what you are looking for.

Blacky :smiley: