First of all, Iâm amazed just how much effort you have put into this @Blacky - not just providing the comprehensive Blueprint, but with all your helpful detailed responses to all the questions. A massive asset to this community!
Iâve been toying with the idea of using this Blueprint for a while now, as I only have one issue with my current automation that I put together a while back - and I think itâs the same issue/question as @dkarijopawiro mentioned a couple of posts above.
Currently I have a Hue bulb that is triggered by a Hue motion sensor, providing that the lux measurement from the motion sensor is below a certain threshold. Once there has been no movement detected by the motion sensor for 2 minutes, the light turns back off.
I also have a âmanual overrideâ button on the wall in place of the original dumb light switch. This allows you to turn the light on or off as you see fit. If the light hasnât come on by motion trigger, due to the lux value being too high for example, but you actually want the light to be on, you can click the wall button (Aqara smart button) and this turns the light on. The light will remain on until there has been no motion detected for 2 minutes, and then the original automation turns the light back off again.
Similarly, if the motion triggers the light on, but you donât want it to be on for some reason, you can click the button and it will turn off - and it will stay off until there has been no motion detected for 2 minutes.
All works well, except if you are static for longer than 2 minutes, in which case if the light was motion triggered on originally, the light then turns off and leaves you in the dark - until you wave your hands around! Likewise if the light was motion triggered on, but you turned it off form the smart button, and again, are static for more than 2 minutes, then as soon as motion is detected, the light turns on.
To cure this, I am thinking of fitting a door sensor as a secondary condition. This would use the âWasp in the boxâ principal, so that if the door is opened, and then closed, the motion sensor only has to detect initial motion in order for the light to be turned on, AND STAY ON. If the door is closed and it has detected motion at least once, then you must still be in the room, and so there is no need for the regular 2 minute (in my case) cooldown to then turn the light off.
I did think about just using the âOccupancy Blueprintâ provided here:
Occupancy Blueprint
however I donât know if my âManual Overrideâ smart button would be a problem in that setup. If your Blueprint can incorporate this occupancy detection via an additional door sensor, that would be great - and I believe what @dkarijopawiro was asking also