Fibaro FGMS-001 Gen 5 Z-Wave Plus Motion Sensor

My new Fibaro FGMS-001 Gen 5 Z-Wave Plus Motion Sensor first paired as "Device" which I took to mean its exact fingerprint wasn't recognised. Now it appears to accept being changed to either Generic Z-Wave Motion Sensor or Fibaro Motion Sensor ZW5. I am only interested in motion and nothing else for this particular sensor. Would I be better off sticking to the generic for longer battery life?

[dev:916](http://192.168.1.202/logs#pastdev916)2022-07-09 13:52:06.877 [info](http://192.168.1.202/device/edit/916)Z-Wave command:SensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[1, 26], size:2, scaledSensorValue:28.2)

[dev:916](http://192.168.1.202/logs#pastdev916)2022-07-09 13:51:27.771 [info](http://192.168.1.202/device/edit/916)fingerprint mfr:"010F", prod:"0801", deviceId:"1002", inClusters:"0x5E,0x86,0x72,0x59,0x80,0x73,0x56,0x22,0x31,0x98,0x7A"

[dev:916](http://192.168.1.202/logs#pastdev916)2022-07-09 13:51:27.761 [debug](http://192.168.1.202/device/edit/916)building fingerprint for unknown Z-Wave device...

[dev:916](http://192.168.1.202/logs#pastdev916)2022-07-09 13:51:25.742 [debug](http://192.168.1.202/device/edit/916)configure() called...

Also it's still giving temperature and luminence events even after disabling them all in the Preferences. Possibly not quite the right driver for this device?

If you want the settings to take immediate affect, do your preference changes, hold in the B button until it goes into config mode (blue led going dark/light) and press the config button on the device page on the UI.
In the logs you should see the config being set.
If not you can wait until the device wakes up and downloads the new config.

I'm using the 'Fibaro Motion Sensor ZW5' driver and it is working OK for me.

1 Like

Oh ok. I don't fancy getting it out of its bird house again right now so I'll wait. As I didn't see any scheduled jobs listed I thought it had already tried sending the commands and it hadn't worked