Fibaro FGMS-001 not working correctly

Configuration Z-Wave
21

That looks realy incomplete. Not sure what the parameter means, but that query_stage="Dynamic" looks suspicious to me.
For my sensor it says query_stage="Complete". I also have roletype="6" devicetype="3079" nodetype="0" attributes that seem to be missing for your sensor.

Maybe deleting the file will trigger a “rescan” by hass? - Just a wild guess…

Here’s the first lines from my sensor:

        <Node id="8" name="" location="" basic="4" generic="7" specific="1" roletype="6" devicetype="3079" nodetype="0" type="Notification Sensor" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" secured="true" query_stage="Complete">
                <Manufacturer id="10f" name="FIBARO System">
                        <Product type="801" id="1001" name="FGMS001 Motion Sensor" />
                </Manufacturer>

Sebastian

22

I think you’re right. I just looked at the openzwave log and it doesn’t look quite right there either, even though the OZWCP looks fine. As soon as I have time, I guess I’ll factory reset the thing again and try to re-add it to the network.

Is there something that I could have messed up with the secure node? I uncommented the network key line and replaced the default key with my own in the config files in both “/srv/hass/src/python-openzwave/openzwave/config” and “/srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config”. Then I used the “add secure node” function in the OZWCP to add the Fibaro sensor. Anything I missed there? Is there a way to add a secure node with the button on the z-wave stick? I didn’t see anything in the manual…

23

I did it the same way. Set a key and re-added the device securely using ozwcp.
I’m not sure that it’s possible via the zstick’s button since (I think) the stick does not know anything about the network key you set in your config file.

Sebastian

24

Well, the factory reset on the Fibaro was a no-go - it ended up with the same results. As best as I can tell, it looks like the sensor configuration information is not being correctly transmitted/interpreted by the hass-openzwave interface, but I haven’t been able to figure out a way to force that to happen. I’ll keep poking around and see what turns up.

25

Good news! I finally got it working. The problem seems to have been in my manufacturer_specific.xml - there was one line in the Fibaro configuration options (before the listing for this sensor) that was not indented correctly, and I think it was stopping my sensor from being identified. I fixed that and after a short time, the sensor states started tracking in hass. Now to do something with them…

26

:thumbsup:

27

I found this thread after having issues with the v35. First off in 0.39 it wouldnt show up at all, yet would in the OpenZWave Control panel… had to roll back to 0.38 - then upgrade again to 0.39 (as 0.38 has leaky memory issues for me!)

The missing piece of the jigsaw was that there were two options.xml files that needed adding the network key I generated!

For me:
pi@raspberrypi:/srv/hass $ find . -name options.xml
./lib/python3.4/site-packages/libopenzwave-0.3.2-py3.4-linux-armv7l.egg/config/options.xml
./src/python-openzwave/openzwave/config/options.xml

Then the motion seemed to come through in more real time

28

I also struggled quite a lot to get the Fibaro v3.2 working. The device was showing up fine in the OpenZWave Control Panel, but the OZW_Log.txtlogfile always showed unhandled command class, as also discussed here. The solution was to do the add_node_secure with an unpaired Fibaro motion sensor within HASS:

As far as I understand, the device really wants to safe battery and does expose the features rarely and once after pairing.