I have 2 Zooz ZSE40 4-in-1 sensors and am running openHAB 126.96.36.199 (Release Build) on a Raspberry Pi 3 B.
After setting some very basic rules to switch on lights on Motion I have discovered that I am getting false motion alerts, around once a day and usually overnight. Both of these sensors are in rooms with closed doors, one a shower/bathroom and one a Laundry closet with washer and dryer in it. Both sensors are displaying the same behaviour, last night one triggered at around 02:20am and one at 04:30am. I’ve tried reducing the sensitivity which has not helped and searching other posts the closest I’ve found is this:
where the device was reporting false motion alerts on wake up but I dont think that’s my issue as the binary_sensor isn’t in the data base any more and I’m using the Alarm (motion) Channel.
I’ve looked at the events.log and can see the false motion detection and then the lights turning on but cant work out what is causing this as there is nothing in the openhab.log at corresponding times. My next thought was to move both sensors to the same room to see if they both trigger at the same time.
Has anyone else seen this behaviour or able to suggest what else I should look at or what I might be missing?
I am working with Zooz & their store thesmartesthouse.com to better support OpenHAB as a recognized system. They now list us on their store as compatible. They are also promising to send us new products on the day of release so we can add support.
That database listing was modified AFTER 2.4 was released. Perhaps updating to a snapshot binding using the manual script could help.
I removed my zwave things, upgraded to the latest version of the zwave binding using the script and then re-added my things but unfortunately I am still seeing the same behaviour where the motion sensor state changed to ON in the early hours of the morning, turning my lights on.
I’ll set the DEBUG log level this evening to see what else might be happening around the same time.
I recal some previous thread (cannot find it now) where small hours ghosts were eventually linked to a system backup / reboot at 0100 or something. Then, the first time the battery sensors checked in afterwards …