Fibaro motion sensors misbehaving since migration to ZwaveJS

Configuration Z-Wave
1

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.

2

Hi

I’m having the same issue having just migrated from the depreciated zwave to the new zwavejs - the migration failed and I had to remove and re-add all the FGMS001 sensors. Previously they had been in use for a couple of years activating a light on movement, but on zwavejs this no longer works correctly with either the light staying off or staying on.

Would you have an example of your automation/FGMS001 setup for sensitity for me to compare?

Did you use the security binary sensor or motion sensor? Not sure either would make any difference??

Cheers

3

I changed the sensitivity to 50 and then I had no more problem. However of course that reduced sensitivity does mean it takes longer for the lights to come with motion. I’m going to try different sensitivity settings.

4

I set parameter 1 (motion sensitivity) to 10 and have had great results (previously I set to 8 from the default 15), so 50 seems really high if its the same setting?

5

Yes 50 is indeed too high. You need to be really close to the sensor for it to detect you. It was just for testing basically and I’ve since then increased sensitivity again. Mine was acting up at the default setting of 15 so I’ll try to increase sensitivity further.

6

Since the update to the latest Z-Wave js all my Fibaro Motion Sensor are not sending any movement. The integration detects going asleep and awake very well as well as lux, but no motion. Beofre the update, it worked - some times.

In my opiniion, Z-Wave JS does mix up things on every update and is very unstable and unreliable. I will go back to Fibaro Home Center fpr Z-Wave as long as Z-Wave JS is such a bullsh*.