Yesterday I migrated from OZW to ZWaveJS which was overall a very smooth experience and almost everything is working better than before. Everything except for my motion sensors. I’ve got the Fibaro FGMS001 multisensors running on Firmware version 3.2. The motion sensors were working perfectly on OZW but on ZwaveJS they retrigger automatically right when the previous motion was ‘undetected’. I’ve got all the motion settings still at their default setting with a 30s cancellation delay and this is how the activity looks like:
mm:ss
00:00: Motion detected (this is the only time actual motion is there)
00:31: Motion no longer detected
00:32: Motion detected (false)
01:02: Motion no longer detected
01:03: Motion detected (false)
01:33: Motion no longer detected
01:34: Motion detected (false)
This goes on for between 3-7 cycles or so until it shuts up. Sometimes I’ve noticed multiple reports of no motion detected in a row, without there being any motion detected prior. For example:
03:40 Motion no longer detected
04:11 Motion no longer detected
04:42 Motion no longer detected
05:13: Motion no longer detected
The led indicator on the sensor itself does not light up during these false reports, which it does when there is a real motion.
Does anyone have a clue?
update:
I just tested one of the sensors in a different part of the house and couldn’t reproduce the there. I went back to its original location and there it happened again even though I’m pretty sure there is no actual motion.
I also checked the ZwaveJS logs and whenever this happens there are four entries:
2022-01-11T09:36:31.657Z CNTRLR [Node 003] treating BasicCC::Set as a report
2022-01-11T09:36:31.693Z CNTRLR [Node 003] treating BasicCC::Set as a report
2022-01-11T09:36:32.794Z CNTRLR [Node 003] treating BasicCC::Set as a report
2022-01-11T09:36:32.832Z CNTRLR [Node 003] treating BasicCC::Set as a report
Update2:
The led indicator actually does blink as if there really is a motion. I’ll try adjusting the sensitivity settings.
Update3:
It does seem that adjusting the sensitivity actually fixed the issue for my motion sensors. I don’t understand how migrating to ZwaveJS caused this and I’m still getting that “treating BasicCC::SET as a report” message in the logs but at least the signals are correct again.