Can anyone please tell me what is wrong with the following automation that, even being close/in front of the motion sensor and moving around, sometimes the light goes out?
Hi Taras, thank you for your help!
I’m testing it out and will let you know how it goes.
The strange thing with the way I had done it: most of the time it worked flawlessly and occasionally you would be in the dark.
I didn’t know why/where it went wrong but the most important is that it works now.
TBH: your solution, I get every step separately but not the logic behind the whole.
Would you mind elaborating a little please because I like to understand/learn?
Hi Taras, or anyone else, there seems to be some issue with this automation.
It has happened again, maybe 3 times, since: that the light turns off, even being in front at about 1,5 meter of the sensor and moving all the time in the detection field.
It just happened again right now, from the history:
detected
cleared: 6 minutes, 59 secs later
detected: 2 minutes, 58 secs later
cleared: 14 secs later
I don’t understand the effect of the 2 minutes in this all, what does it do in simple words.
On top of that, I don’t understand why/where it goes wrong so any help is highly appreciated!
As mentioned in my previous post, if the suggested automation fails to work reliably, it’s not the automation’s fault but the motion detector. Check its motion sensitivity and cooldown period (if it’s adjustable).
You should be able to check the cooldown time in the logs.
Also not sure which zigbee you use, but with zigbee2mqtt i can change the cooldown timer on my ikea motion sensors
Yea, that is the cooldown.
Before I found out that i could change my cooldown (180 s) on the ikea motion sensor, i used to make sure the light would be on for at least 4-5 minutes, so the sensor would have 1-2 minutes to re-activate
No, my 2 minute time frame ensures the lite would not switch off during the cooldown time.
But within that 2 minutes the motion sensor should be triggered again for the light to stay on.
I don’t get it…
Do you mean that the sensor has to be triggered IN the 2 minute timeframe so the light stays on AFTER the 2 minutes have passed?
This seems to me the obvious course of events, the way a light should work with a motion sensor and from what I understand, this automation works that way, no?
Yesterday, again light off, even being close to the sensor (about 1,5m) and moving.
After 30s, the light switched on again.
That doesn’t make sense with a sensor that has 10s cooldown, no?