Thanks for this video, especially for the way to change the timer, that's very usefull information. In node red, you can also use stoptimer that is timer you specify the amount of time and this one will reset on input (new motion detection in this case), I use it with a switch to combine two motion sensor to control one light.
I just got this sensor based on this review and others like it. What no review mentions (and I only found out first-hand and later reading about it on reddit and the home assistant community discourse) is the awful range of motion detection. Testing it in perfect conditions (chest-level placement, clear field of view, dead on center from the sensor), it only detects me up to 2 meters (6.5 feet). Putting it up in a corner, that range drops to less than 1.5 meters. This is extremely disappointing, especially as I also have the original aqara motion sensor, which works perfectly in my hallway (over 5 meters range). The fact that no reviewer mentioned this (and it's actually a widespread complaint if you go read comment sections) shows that none of them actually use the equipment they're reviewing.
I ordered an Aqara motion sensor just before watching this video. Bummed to find out I ordered the "older" model with his 90 seconds drop off time. Installed it today and to my surprise, in the settings there was a drop off option ! Set it to 5 seconds, pressed the little button and voila, 5 second drop off!
@@touldie573 well, I might have to correct myself a bit. You can indeed set a drop-off time. But it still takes about a minute/minute and a half before it triggers again. In my case no problem, but in some it could be.
Great video, thanks. For the delay part I'm using "node-red-contrib-stoptimer-varidelay" which resets the timer every time a new message comes in. It also can be set to show a countdown in real-time, which I find very useful
Great video as usual! Looking forward to your others. I have also been looking at trying to get alexa to return sensor status with not much luck - might be a good idea for a video!
There are numerous posts complaining about the short range and then there are mmwave sensors available, so I would consider changing the topic on this video as it makes claims that are nowhere near truth.
I copied and pasted your node red, I was able to set my detection interval to 2s, but now cant change it again. I've changed the inject node to 10, deployed, injected. My debug still shows 2
I have not been able to get it to work with z2mqtt and Conbee 2. It shows as unsupported even after updating Conbee firmware. Suggestions? I also have Sonoff Dongle but if I replace Conbee I would have to re-pair 83 devices which I am reluctant to do.
May I comment your node-red flow. Replacing delay node with “wait until” node you can define timeout 5/15minute in what time node wait entity state is not on. This way you can remove reset delay path
Hey Ho! Thanks for this Video- i ordered this P1 from Amazon and just this 30s Problem I have got two Problems: i am from Germany and my english is‘ nt so good. Second Problem: in Germany we say „bloody beginner“ of HomeAssistant. Can you explain this Procedure with NodeRed. Than i can solve this Problem too. Thanks a lot and good Job! Simon from Germany
Thanks Simon that really helped changing the timing, i currently use zha with a sonoff 3.0 zigbee stick. The setups been great but is there any advantage to using zigbee mqtt? Just playing with it experimenting with the sensor and not getting the best detection range though I've set it to high checked the logs to confirm its set to high, but only getting up to about 3m before it detects. Do you have any advice ? thanks great vid as always
I still doubt that it's better than my rock solid, reassuringly expensive, Philips Hue motion sensors. I have tried other motion sensors, and all have fallen by the wayside, except the Hue ones, they really are awesome.
@@HomeSight For me it's a reliability issue. My existing Aqara ones need re pairing occasionally, which is no big issue per se, but i have all the walkways in our home lit up with motion sensors, so they need to just work with NO issues to pass the WAF, and the Philips ones do it perfectly.
Since your minimum delay time to turn off the lights is 5 minutes what is the advantage of having the faster clear time of this sensor vs original? I guess you start your 5 minute wait earlier but I see no real advantage in your use case. If you wanted to take actions quickly when the motion cleared or wanted to detection again more quickly I can see an advantage.
Hi Don, you’re absolutely right! In my case in my office I have the delay set to a min of 5 mins, but i actually plan to use it in in the the hall way where movement is more transient and therefore can make use of the shorter times.
Maybe the sensivity is more accurate than older one. I use it to light up stair leds and sometimes the presence is not detected (nobody has broken legs yet)
I had a little internal debate as to whether it was “ak-ara” or “aqua-ra” too! Not sure if there’s a right answer. I am confident that I got Xiaomi entirely wrong though!!
@@HomeSight It's Ak-ara. Xiaomi is pretty close to Show-me, but with a little "shiow" in it. The one that throws me is the UK pronunciation of "template." I'm still not sure whether the UK dictionary says "tem"-"plate" or "temp" "late" where the "late" is pronounced "lut", which I'm certain is the American English pronunciation. :)
