Happy to help 
Let me know how you get on.
Everything is showing up in the ui, again thank you very much.
However i think the motion detection time-out is 30 sec, is it possible to reduce it?
Thanks
I’m not familiar with fibaro, I have Vision and Aeotec, but…
Try going to Configuration → ZWave
Select your node
And check for anything under ‘Node Config Options’
I was able to reverse the state indication, and fix some sleeping issues this way
Ok, i will have a look at it.
Thanks.
Ok i have found the option but when i change from 30 to 10 it’s going back to 30 sec.
Any idea how to fix this?
I have the same issue with my window sensors.
The problem is that they go to sleep VERY quickly after sending their info.
Have your new info typed in and ready to go with the mouse on the ‘Set Config Parameter’ button.
Press the Pair / Zwave button on your sensor, and almost instantly press your mouse button.
I was often having to try two or three times before I got the timing right.
1 Like
Ok, i will try this. My sensor needs 3 short press, hope it will not be so hard.
Thanks.
Thanks It’s working perfectly!
Glad to hear it !
It was only a few weeks ago that I set up my zwave sensors so it’s all still pretty fresh in my head
Cannot get the Figaro FGMS-001 to pair with the Z-Stick. Can I ask for some assistance please?
Fresh Hassbian installation. The first and ONLY thing I am trying to do is get the Z-Stick and the Figaro working.
The Z-Stick is plugged in and I have rebooted (several times this morning already). The device looks to be configured correctly.
I have tried to pair the devices through HASS UI (Config > Z-Wave > Add Node, then pressing 3x on the Figaro’s internal button) and also unplugging the Z-Stick and pressing the physical button.
Same effect = no pairing.
I see data in the OZW_Log.txt, specifically when clicking the “Add Node” action:
2019-04-05 11:10:26.955 Detail, Queuing (Controller) Add Device
2019-04-05 11:10:26.956 Info, Add Device
2019-04-05 11:10:26.956 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2019-04-05 11:10:26.956 Detail, Notification: ControllerCommand - Starting
2019-04-05 11:10:26.957 Detail,
2019-04-05 11:10:26.958 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2019-04-05 11:10:26.961 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x01, 0x00, 0x00, 0xb9
2019-04-05 11:10:26.961 Detail,
2019-04-05 11:10:26.961 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-04-05 11:10:26.962 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2019-04-05 11:10:26.962 Detail, Node001, Expected callbackId was received
2019-04-05 11:10:26.962 Detail, Node001, Expected reply was received
2019-04-05 11:10:26.962 Detail, Node001, Message transaction complete
2019-04-05 11:10:26.962 Detail,
2019-04-05 11:10:26.962 Detail, contrlr, Removing current message
2019-04-05 11:10:26.962 Detail, Notification: ControllerCommand - Waiting
2019-04-05 11:10:26.965 Info, WriteNextMsg Controller nothing to do
If I select the Overview option from the main menu, it shows this, suggesting the device is not on?
the toggle in that card doesn’t do or indicate anything. you can completely remove it if you want. the thing that matters is on the next line where it says the device is “ready”.
I can’t help with the specifics of how to pair a fibaro device since I don’t have any.
After you attempted to pair the device have you looked in either the z wave control panel section of the configuration area or in the dev-states page (or both) to see if any additional z wave devices are showing up?
Thanks @finity
The setup looks good. devices are reporting as “Ready”, blinking lights, etc…
When I click the “Add Node” button, I get some of the lines from log file, and then the log file has no futher entries than the:
Info, WriteNextMsg Controller nothing to do
The Fibaro device does not appear in any part of the HASS interface.
Others are using a different openzwave web interface, I think on port 8888. This doesn’t resolve on my system. I presume this is the native openzwave software, which HASS integrates with? How can I view this interface? Are there additional log files or settings that I can apply?
I haven’t set a Network Key, as I don’t have any “secure devices”. Could this cause this issue?
click on the hamburger menu on top left. click on “Configuration”. Click on “Z-Wave”.
in there should be a drop down with all the z wave nodes listed.
or in the same hamburger menu go to the bottom, second from left and click the <> icon to bring up all your entities and go to the bottom and look for “zwave.xxx” entities.
The only Node is the Z-Stick itself, which I can select.
There are no entities beneath it or other Nodes.
I’m not sure then.
You probably should go ahead and set a network key even if you don’t use it now you likely will later if you get additional devices. However, I don’t think that would prevent you from pairing even if the device was secure because if you can’t pair a device securely I think it will by default drop back to un-secure pairing.
I know that there are some zwave devices that are extremely finicky with the pairing process. It might even come down to holding your mouth right to get it to work! 
One last thing to ask tho is have you restarted your HA after trying to pair the device?
Have you tried excluding the device first, and then including it? Sometimes this works.
@finity yes, plenty reboots. And I thought the same as you about keys. I read somewhere it auto generated it, but maybe that’s using a different distro / platform choice. But it looks like I needed to specify it.
@freshcoast yes, my understanding is “remove node” puts the z-stick into exclusion mode. Also tried this a few times as well.
Some threads from couple years back reference udev rules. Still applicable?
they are generally still applicable but not in your case since the Z stick itself is being discovered and z wave is being configured by the system. That only solves the problem of zwave getting errors due to the usb device path changing periodically so the system can no longer find the stick.
something else you might try is to factory reset the fibaro device (not the stick) before trying to pair it. I’ve heard of that fixing pairing issues before.
@finity the device hard reset seems to have worked. up until the next stage at least…
the device now shows in the interface, and in the logs. happy days! guys, thanks for the inputs, suggestions, etc.
I was expecting to easily be able to see live data, i.e. temperature and light levels that should have regular values (unlike the motion sensors that are based upon movement which might not be there) and the device seems to be listed permanently as “sleeping”.
Sleeping isn’t necessarily bad for a battery powered device. It’s strange that it isn’t showing any values.
Do any of the values change when it detects motion?