That did it. I was removing with YAML. Thank you!
1 Like
I think this is nearly perfect, certainly looks to be the easiest blueprint for this functionality⌠except one thing but that is probably my configuration
Basically what I am after is:
-
Turning on:
â By occupancy/PIR (EP1)
â Toggle of Physical switch (Shelly) -
Turning off:
â Timeout of occupancy/PIR
â Toggle of Physical switch
At the moment all is working perfectly⌠except the toggling to turn off. I am assuming that the having the same states for the same device in both on and off are causing this.
If I only set âpoweredâ for on, and ânot poweredâ for off then there is a really odd feeling not knowing if the switch will work. For example if I walk in and the sensors turns the light on, but when I walk out I press the button⌠it will not turn the light off until I press it a second time.
Any ideas how I could achieve this?
1 Like
NEW RELEASE:
23/01/2024 - Version 2.5
- Corrected logic in the turn off functions where the triggers where activated regardless of the required conditions in some cases.
A couple of things:
- There was an issue in the turn off logic where lights would be triggered to go off immediately after being triggered on. In practice, this meant that they actually never came on.
You may have been affected by this issue, so I would suggest re-importing the blueprint by going to: Settings > Automations & scenes > Blueprints. Once there, click on the 3 dots and select âRe-import Blueprintâ. - I would suggest always using âstateâ triggers instead of âdeviceâ triggers.
Device triggers never work great in my experience. So in your case, your trigger to turn on should be: State âOffice PIR motionâ turned to âon/detectedâ. And state âOffice occupancyâ turned to âoffâ to turn the light off.
See below for an example configuration:
thanks for that I have updated it. But I think my question is still the same.
If I walk into the room and the light switch is set to off; and the sensor turns the light on for me it is all ok. The light will stay on until occupancy is no longer detected.
But when a guest goes to leave the room they often try to manually turn the light off due to habit.
But cause the current state of the switch is âOffâ, it will change to âOnâ and hence the light also stays onâŚ, So as a result they will often mash the button.
How do I get the light to turn off with a single press of the button?
I think youâre better off making a separate automation that changes the buttonâs state when the light goes on.
Hi
Thanks for a great blueprint.
Mine is working to the extent that when I restart the automation then it correctly adjusts the light brightness, However, it does not dynamically change as the lux sensor lux changes.
My bulbs are smart dimmable, and some color as well, but they are old and I am guessing that the supported feature is not there to dynamically chage the brightness of the bulb.
Am i correct in this assumption, or is there something I am missing? Once i turn off the light and re trigger the motion sensor I can see that the brightness has changed.
Thanks again for your blueprint, and assistance.
Thatâs correct behavior: the trigger in you case is the motion sensor and not the lux sensor. so only when the motion sensor gets triggered the automation goes through the calculation again and sets the light to the changed value.
If you want it to work with the lux sensor only, you could try my other blueprint: đĄ Smart lux dimmer - Adjust light brightness depending on light sensor value
Thank you for that information
Am trying your other Blueprints
1 Like
Hi @AntonH. I am a huge fan of your blueprint. I have one more suggested feature.
I use the blueprint to turn on the lights in a room, if thereâs motion detected in the room. I use the staircase option to countdown x minutes.
In my use case, I would like the lights in the room to turn on when I enter the room as they do now, but then only to turn off if there hanât been any motion in the room for x minutes.
For this, I would like the staicase countdown to restart if any of the triggers fire off again during the staircase timeframe.
Hope this makes sense.
1 Like
Hi @AntonH
I just switched from one of your templates (controlling just the brightness) to this one, which helped me delete a few of my own automations (thanks for that 
). I have two question.
I have two motion sensors in my hall because it is build like an L. Therefore I have set two deactivation triggers (certain amount of time after one of the sensors does not detect movement anymore), which only work if none of the two detects movment, so that there are no unsure states. The deactivation trigger condition does somehow prevent the deactivation flow to be executed and Iâm not sure how to correct that. Without the condition the deactivation flow is executed but if there is continuous movement just one of the two sensors is detecting, the deactivation is still triggered.
I only want the automation to work between 7:00 - 22:00 but the deactivation triggers shall still work outside the given time plan. This does not seem to work so I have to set up an additional deactivation automation.
1 Like
The Blueprintâs mode is set to ârestartâ, so what youâre describing should work by default. Each time itâs triggered the staircase timer resets.
Do take into account that motion sensors usually have a built-in cool down period during which they will not re-trigger.
This is normal. The mode of the blueprint is set to ârestartâ. This means that it will restart the automation when one of the sensors is triggered and reset the turn off triggers.
I donât understand what you mean by this. Could you clarify a little more?
This is normal. The mode of the blueprint is set to ârestartâ. This means that it will restart the automation when one of the sensors is triggered and reset the turn off triggers.
That does not seem to work for me. If sensor 1 starts the deactivation flow (because a switch to no movement was recognised) and I move within the area only sensor 2 is detecting, the deactivation flow will still be executed (because sensor 1 is not detecting movement) and deactivate the light for the whole area.
Imagine there is movement at 21:59 (continuously until e.g. 22:03) the deactivation flow will not run anymore or this happened for me at least.
From your explanations, I understand that you have a trigger of âno movement detectedâ to start the deactivation. I think this is whatâs causing your issue.
I would work with a staircase timer in your case. That would start counting down from the moment movement is detected and be reset every time motion is detected again.
1 Like
Still, this will not do the trick. If there is a room with continious movement the staircase function will be triggered and executed (there will be no switch of the trigger, which will stay enabled). I would assume that triggering it with âno movement detectedâ would be better in addition to the condition that all sensors in this area do currently not detect any movement. I already created that flow as an additional automation (which works) but it would be cool if it could be enabled in your template as well 
Hi - I think this will be a daft question, but hopefully someone will take pity and help. I can get this automation to run once when a trigger is fired (motion or door open) but thatâs it. Itâs set to Dynamic so my expectation is that it will continue to run dynamically adjusting the lights until the Off trigger is fired. Instead it runs once then stops.
Any idea what Iâm doing wrong?
If your trigger doesnât re-activate then the automation will run only once.
If you want something that runs continuously you can look into my other blueprint: Smart lux dimmer - Adjust light brightness depending on light sensor value
Ah yes, already got that one (which works a treat). I was looking for one single blueprint with extended facilities to do the whole thing - motion, dynamic light based on lux, colour temperature that changes through the day, and then switches the lights to red on motion at nighttime. Iâll keep looking, but thanks very much for this one.
NEW RELEASE:
23/01/2024 - Version 2.6
- General spelling corrections
- Amended syntax to new guidelines (HA 2024.8 & 2024.10 changes)