šŸ’” Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

Blueprints Exchange
, , , ,
3000

@vladx

This is not the blueprint it is Z2M update and it is your ambient sensor. Have a look at this post as it is the same as you click here

Then for the solution click here

Hope this helps you

Edit: I see you worked this out already. Nice one.

Blacky :smiley:

3001

@silver323

You just need to do a bit of math.

1 divided by 60 times by your seconds = result.

Example 1 divided by 60 time by 30 seconds = 0.5

Now just type the value into the input and click save.

Blacky :smiley:

1 Like
3002

@btheo

All looks good.

Is your bypass ON? input_boolean.bouton_garage

Blacky :smiley:

3003

@mase

I have another blueprint so if you manually turn the lights ON it will turn a bypass on disabling the automation. I should release it but I havenā€™t as yet. If you would like to test it I can provide the link.

Blacky :smiley:

1 Like
3004

Thatā€™s perfect when we have a set of buttons that work with that light which are also linked to a motion sensor (or more) running out automation, so if we use the buttons it will stop the automation from turning the lights off until we manually turn them off.
Iā€™m very interested on such a thing, been trying to build one myself but without much luck.

3005

@tretabyte

Are you interested in the blueprint that I haven released yet? Is that what your referring to?

Blacky :smiley:

3006

that is correct :heart:

3007

@tretabyte

Okay, I clean it up and release it. Keep an eye out for it.

Blacky :smiley:

1 Like
3008

guess that should do the job. would like to give it a try :slight_smile:

3009

in this blueprint, I noticed thereā€™s a bypass session which should be something similar to what we were discussion, right?
a trigger that skips the motion sensors and keeps the light on (at least thatā€™s my understanding), it should be a helper or something linked to a click of a button right?

3010

I really like this blueprint, but i need to add a conditionā€¦ something like, the automation only turns off the light if the bathroom door is openā€¦
I thought to add the door binary sensor to my presence group, but the problem is that they are inverted on<->offā€¦ any simple way to do this ?

3011

@Blacky,

Iā€™m sorry for the misunderstanding.

Iā€™m agree with you, the bypass 3 prevents the automation to run if the scene is activated. But, as you said, I also need to turn the helper OFF (otherwise, the automation will never run again). And, as soon as the helper is turned OFF (manually or using ā€œEnable the auto OFF for the bypass switchā€), the lights are turned OFF (immediately or after a delay), but I want to keep the lights ON, and I donā€™t want to turn the helper OFF manually (not really user friendly) when I finally decide to turn OFF the lights.

So, the only solution I found is to disable the auto OFF and create another separated automation that turn OFF the helper only if the lights are turned OFF. This way, the lights stay ON as long as I want.

Iā€™m not very happy to have 2 automations for this behavior, this is why I suggest to add a checkbox that allows to never turn OFF the ā€œLights - Switches - Scenes - Scriptsā€ even if the bypass is turned off. It could be seen as a ā€œone way bypassā€. Do you follow me or that makes no sense?

Best.

3012

Hi @Blacky,

Quick question about bypass.
I want to stop the automation to run when I have a set scene switched on. Not sure about the mode I should go between ON and OFF.

For example, I have an automation for lighting a room but when I switch on a scene, I want that scene to stay as long as it is switched on without having the automation to run.

Thanks

3013

For the life of me I canā€™t get my mind around this!!!

Iā€™ve setup a BINARY GROUP for my motion sensors, all these being Shellyā€™s (Motion 1, Motion 2 and Motion BT).
The group appears to be setup properly, meaning both HIDE MEMBERS and ALL ENTITIES are switched OFF.

As a matter of facts, the binary entity goes ON whenever either motion sensor gets triggered.

Here comes the part where I get confusedā€¦

Even if the Sensor binary group goes ON, UNLESS IT IS THE BT SENSOR being triggered, the automation doesnā€™t start!!!

What am I missing??

3014

Had the same issue. For me it was the illuminance sensor used for the ambient feature. Apparently zigbee2mqtt also received an update this week and all motion sensore now report lux as ā€œilluminanceā€ instead of ā€œilluminance_luxā€ and it seems to take quite a while until that propagates. Also, ā€œilluminanceā€ used to be in use for something else before, so you might not even notice anything missing in your Sensor Light config. See more on this issue here:

3015

Thanks but it cannot be as the binary group itself goes on regardless the sensor.

The odd issue is that despite the binary group going on, unless the actual sensor activating the binary group is the BT Shelly, the lights are not being switched on.

I donā€™t get how thatā€™s even possible tbh!!!

The trigger is the binary group not the entities behind it, so why it only trigger automation when the entity that activates the binary group is the BT sensor rather than one of the WiFi sensors??

3016

HI All,

I have a situation where I have some smart light switches that control my exterior lights. I have the automation set so that when cctv motion is detected, it enables the relevant switch outputs to turn on/off the lights - but if I want to turn on the lights manually, and then I walk outside, the lights turn off. A bypass switch adds complexity where there doesnā€™t need to be any - quite literally if the lights already on, then the motion trigger should be ignored unless the motion trigger triggered it previously. Is there any way to configure this with this blueprint ? Thanks heaps for putting it together by the way, its briliant, I just canā€™t sort this last little bug out. :slight_smile:

1 Like
3017

@mase @tretabyte

Here it is.

:stop_button: Manual Control Status Tracker

Enjoy

Blacky :smiley:

1 Like
3018

Iā€™ve found the culprit!

Let me recap the configuration:

Lights activated by GROUP SENSORS (pir 1, pir 2, pir 3)
Ambient enabled reading status from pir 3

Expected outcome: when either of the sensor behind the group would trigger AND luminosity is below 200lux, lights go ON.

Actual outcome: only when pir 3 is activated and luminosity is below 200lux, lights go ON.

It happened to be a conflict between the group and the single luminosity sensor.

SOLUTION: created a LUMINOSITY SENSORS GROUP reading the median value from pir 1, pir 2, and pir 3.

No more conflicts and automation behaves as expected.

I hope this helps somebody in the future and perhaps the author may want to look into this to avoid this kind of conflict in the next releases as not all motion sensors may also include a luminosity sensor and there might be cases where someone may need to society a single luminosity sensor rather than a group of it.

3019

@JorgeMaTeixeira

You will need to create a template binary sensor to invert it. Once created then use it in the automation.

To create a Template binary sensor, follow these steps:

  1. Navigate to Settings > Device & Services > Helpers tab at the top.
  2. Click the Create helper button.
  3. 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, add the code below, replacing binary_sensor.your_door_entity_id_here with your entity ID.

{{ is_state('binary_sensor.your_door_entity_id_here', 'on') }}

Blacky :smiley:

1 Like