You are going in the right direction - adding the manufacturer and device specific lines in theOpenZWave config should allow OZW to identify the device - I have done the same previously.
What platform and install mechanism are you using? If you are using a Virtual Environment, or the Pi All In One with the virtual environment option, there may be another copy of OpenZwave and you are editing the wrong one.
This is the only file I can find! Also … before I added and altered the .xml-files I could not see the parameters of the ZCC5010 device in the open-zwave GUI.
Whatever about the LogicHome, I imagine for a big brand like Fibaro the manufacturer details would be picked up automatically, with no manual hacking is required. Initially gathering of manufacturing data is slow for battery nodes because they sleep - but you can speed it up by waking them up near the controller.
yeah. I think so. I might have a bit mess with my venv. I still have libopenzwave 0.3.3 or something… the keyfob is well listed in manufactures list but wont catch up the config. I cannot config the device at all. i added manually the scenes .now i see the buttons… but couldn’t test yet if hass now accepts the scene ids
the main problem is that i just don’t have any configuration options nothing
I actually got everything working with the fix described above. I think the fix in the end was finding the 3rd and right folder to place the XML filen in. For a long while everything has been running very well.
I have since then moved on to HASS.IO and still we no problems. But problems returned when I had to change one with due to repair and at the same time installed two new switches. Now I can’t get HASS to proper recognize the switches other that instance 1 (which means that only one of four buttons is functional). I have tried to configure using HA, through OpenZwave (I still have the old SD card from my experiences mentioned in the beginning of this thread) and with Domoticz (see: https://github.com/OpenZWave/open-zwave/pull/1025#issuecomment-271178707)
The odd thing is that HA sees all the instances and the software can control the hardware, but the hardware can only control the software on instance 1 (of 5).
To finish this off: I re-read the thread from the link deleted all assosiation to “1” leaving only “1.1”. This I thought was needles since the one working switch has both “1” and “1.1”.
Deleting the assosiation to “1” fixed the problem. Oddly Domoticz re-introduces the assosiation so “1” and “1.1”, but this time everything works.