I’am writing this up based on my post to open-zwave but since i saw a lot of people here having troubles with it, i’ll inform what my problem was.
So basicly you have multiple version of the device.
FGMS-001 v2.4
FGMS-001 v2.6
FGMS-001 v3.x
FGMS-001 etc etc
You can find supported versions here: http://www.openzwave.com/device-database
In you zwcfg.xml you can see your
But this doesn’t show you a sub component. If you use ozwcp and go to the motion sensor and click on “information” you can see the Application Version. In my case this was 2.08.
So 2.06 didn’t work but everyone else on the internet said it worked just fine (because we all match it with the product type and id. But that isn’t just enough, application version matters!
Since i am trying to move from fibaro to home assistant, i still have my homecenter. I added the device in there, checked for a firmware update and there it was. v2.8! and i had v2.4, after updating the device it showed 2.08.
Removed it from homecenter, added it in home assistant. Still no luck, woke it up another time, then restarted hass again and was ready to throw in the towel and poof, it all became alive!
So this could very well be your problem when you checked the id’s checked the open-zwave support and have the same types and it doesn’t work, it could well be that your firmware needs a bump.
Sadly i don’t know how to do it without homecenter, but at least it could give someone a hint or possible solution.
If you come across issues with this device, you can always chat to me on gitter, it seems i’am now a subject matter expert on fibaro motion sensors haha…
Fibaro update screen…
