Page 1 of 1
Neo Coolcam PIR Motion Sensor triggering constantly
Posted: Monday 21 October 2019 15:26
by Timmiej93
I've had the Z-wave version of the Neo Coolcam PIR for a while now, but recently it started triggering constantly. Basically, it triggered, stays on for the on-duration, turns off, and triggers again immediately. It does this constantly, so you can imagine my annoyance with it. Today I measured the battery, which seemed very low (2.4V without load, 2.1V when inserted), so I'm thinking that may be the issue. Has anyone else had the same issue? I've now replaced the battery with a 3V power supply, and everything seems to be working fine again. I'm still not 100% sure if that was the issue though, but I hope that was it.
Re: Neo Coolcam PIR Motion Sensor triggering constantly
Posted: Monday 21 October 2019 16:10
by knielen
Yes, could indeed be the battery, came up to me right before you mentioned this in your post.
Re: Neo Coolcam PIR Motion Sensor triggering constantly
Posted: Tuesday 22 October 2019 10:05
by lost
Timmiej93 wrote: ↑Monday 21 October 2019 15:26
I've had the Z-wave version of the Neo Coolcam PIR for a while now, but recently it started triggering constantly.
Had the exact same issue + battery level report of this device is a shame: One started to trigger non-stop with 30% remaining, the other 20%.
Plan to change batteries under 40% battery reports for these ones, maybe more if you plan to leave your home for a few days & use them to trigger alarm: This may not make your neighbors happy...
Neo-Coolcam products on 220V were also poorly designed & most plugs failed after a few days/months (+ unsafe design) and should IMO be avoided: Their CE mark must be the "China-Export" hack... 1 or 2 years later, you discover their battery devices are also flawed (at least, may not cause fire in your home not being AC powered)!
Well, that's cheap but this does not value more... maybe even less depending on use-case.
Don't know if this was fixed in the latest version of their PIR, but this one at least proved to share the same IDs for 2 versions (one with temperature sensor, other without) causing integration/XML config file selection issues! That's no good sign of a design improvement path.