Fibaro Motion Sensor with Z-Wave Plus Multisensor

Hardware Home Automation
1

Has anyone used this sensor? I’d like to use it in my family room, but wanted to know if anyone had success with OpenHab 1.8

2

I do not, but maybe it helps if you add the correct fibaro part number of the device? And have a look at the zwave database:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list

Is it already listed there? If so, you have a good chance that somebody is using it already. If not, it has to be added to the DB first, otherwise it will not work with OH.

3

If you mean the FGMS001: yes, works without any problems.

4

I am having terrible difficulty with this sensor (new version with 5 association groups).
Initially, I thought that the reason I wasn’t getting motion events was that I hadn’t used the correct Association Group and, when I changed it, it seemed to work. However, I can now not get it working again. I have previously seen Lux, Temp and Motion updates but now I only get Lux updates and no Temp or Motion events.
Messing around with it, I have had it working, not working, working, not working etc without ever getting to the bottom of it. Below is my setup - I would really appreciate any assistance because I have been banging my head against a wall for over 2 weeks now (I have used various other sensors and have always got them working quickly and all of my other sensors on this system are operating correctly)

I’m using Openhab 1.8.3 with 1.9 addons on a Rpi3 and Aeon Labs Z-Stick Gen 5

fgms001-a.png1904×1022 106 KB

fgms001-b.png1904×1022 129 KB

fgms001-e.png1336×648 25.6 KB

fgms001-c.png1740×987 70.5 KB

fgms001-d.png1904×1022 120 KB

5

I have the slightly older sensor and am not using openHAB1 anymore, but maybe we can get it to work anyway:

  1. Set the Lifeline association group to the controller, remove the other associations.

  2. Remove ALL the unnecessary refresh_interval's from your items definition and try:

Contact Kitchen "Kitchen PIR [%s]" { zwave="6:command=sensor_binary"}

And please try to paste the text code you wanna have checked, not a picture … it’s horrible to type everything that has to be changed instead of being able to do a copy and paste … thx.

6

Hi!

I’ve also experienced a lot of problems with this sensor before I got it working.
I have Z-wave plus version (Gen5), however I’m also running it under OH2.
I don’t know much about OH1, but for OH2, I had to

  1. Exclude it
  2. Hardware reset it
  3. Include it again

Make sure the device is fully initialized. It can take a long time before it is. Mine wasn’t and that caused problems, some functions worked (Like reading temperature and light), whereas the actual movement trigger didn’t.

In general my experience with z-wave is that it can be quite tricky to initialize the devices, include them in the z-wave network to get them up and running. Once they are included and properly initialized they seem to work quite well.

Regards, S

7

Hi Seaside - thanks for replying - doing a hardware reset on the sensor did seem to help and I got it working almost immediately after re-inclusion. Thanks for that. Incidentally, I get two x ON and 2 x OFF from the motion sensor - do you and, if so, did you manage to get round it?

8

Hi sihui - thanks for replying - I actually got somewhere following seaside’s suggestion to do a hard reset on the sensor so I’m going to give it a go. As I write, I am receiving motion events on Association Group 2 and I have seen Temp updates too.
And point taken about code not images.

9

Hi!

No I have not noticed that.

I have the following items:

Group ZwaveEye1                     "Motion Sensor"                                         (Zwave)
Number ZwaveEye1Lux                 "Motion Sensor [%.2f Lux]"    <sun>                     (ZwaveEye1) { channel="zwave:device:be1078de:node29:sensor_luminance" }
Number ZwaveEye1Battery             "Motion Sensor [%d %%]"      <battery>    (ZwaveEye1)        { channel="zwave:device:be1078de:node29:battery-level" }
Number ZwaveEye1TempProxy           "Motion Sensor [%.1f °C]"     <temperature>    (ZwaveEye1)    { channel="zwave:device:be1078de:node29:sensor_temperature" }
Number ZwaveEye1Temp                "Motion Sensor [%.1f °C]"     <temperature>    (ZwaveEye1,Temperature)
Switch ZwaveEye1Motion              "Motion Sensor [%s]"           (ZwaveEye1)     { channel="zwave:device:be1078de:node29:sensor_binary" }
Switch ZwaveEye1Alarm               "Motion Sensor Alarm [%s]"             <fire>   (ZwaveEye1)      { channel="zwave:device:be1078de:node29:alarm_general" }
Switch ZwaveEye1AlarmBurglar        "Motion Sensor Alarm b [%s]"             <fire>   (ZwaveEye1)      { channel="zwave:device:be1078de:node29:alarm_burglar" }
Number ZwaveEye1Seismic             "Motion Sensor Seismic [%f]"             <present>   (ZwaveEye1)      { channel="zwave:device:be1078de:node29:sensor_seismicintensity" }

And when triggering the detector both the burglar alarm and the motion sensor are triggered.
I have a rule that looks on several items, so it can be triggered multiple times. I use a Lock to keep the same code from executing several times at the same time.

rule "TurnLightsOnHallway"
when
    Item ZwaveEye1Motion received update or
    Item ZwaveEye1AlarmBurglar received update or
    Item ZwaveEye1Alarm received update or
    Item LightsHallProxy received update
then
  if (mMotionLock == null) {
         mMotionLock = new ReentrantLock()
    }
    mMotionLock.lock()
    try {
       logInfo("DimmerHall", " Motion Triggered in Hall")
       <CODE FOR HANDLING DIMMER WITH TIMER ETC>
   } finally { mMotionLock.unlock() }
end