Hi Chris, hi Bruce,
I tried to include my door lock in S0 security mode. But the xml (see attachment network_d5817d5e__node_10.xml) generated during inclusion isn’t nor very expressive neither very detailed. Not even the manufacturer, the deviceID nor the deviceType are set according to the Z-Wave document ABUECFA3010S. And there are only four command classes in the xml file whereas in the certification document of the ABUS door lock there are 17 command classes listed.
So I tried to adopt the xml file of the Fibargroup Smart Implant device “FGBS222” but I had difficulties in defining the channels (couldn’t find appropriate typeID’s for the channels nor the corresponding command classes) and the device properties (values behind the colons of a command class and the value betwwen the triangular braces after the command class).
May be you can help me to finalize the xml so that the “ABUS Z-Wave HomeTec CFA3010” can be added to the database.
So, work is done
I was able to include the door lock so that it produced a better xml. I then uploaded it to the device data base, completed the database entry with data from the manual and the Z-Wave document ABUECFA3010S and requested a review. Hopefully the review will be positive and the device will be included in the next database release
But how can I use the xml I exported from the database in my openHAB installation? Where do I have to put it so that my door lock will be recognized correctly afte re-inclusion? I’m running openHABian 2.5 on a Raspberry Pi 4…
@Chris:
I used the device editor for the first time and it was fantastic. You did a great work
Would you please remove the heading2 tags. I started editing it but you did use it on almost every entry and I don’t have time to finish this.
This is important for the documentation and its visual display.
Hi sihui,
to my mind all h2-tags are removed. I think they where included when I did copy and paste from the online manual of the manufacturer. Now I hope it satisfies the needs of the database.
A hint for your next database edit: copy content from online manuals or pdf to an ascii editor first (for example notepad++) and then to the database window.
This removes all those nasty tags.
I believe it should work with OH3. The database entry is here.
That usually means a battery operated device has not been woken up enough to be fully discovered. Door locks in secure mode can be especially problematic due to tight timing constraints.
They need to be factory reset between secure attempts… Inclusion needs to be through the binding.
It seems to me that the binding is not communicating with the device if it doesn’t know the manufacturer information. It is however a bit hard to know what is happening without seeing what’s in the logs…
That’s not really important though, and doesn’t mean that there is communication with the device and the binding. It doesn’t mean that the device has securely included either.
If you can provide the log during the secure inclusion it might be useful.
I did everything again (Exclude, Reset, Switch from S2 to S0 & the include over openhab).
Now I found the Log:
2020-12-27 23:55:14.300 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 126: SECURITY_INC State=FAILED, Reason=GET_SCHEME
2020-12-27 23:55:14.307 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 126: Device discovery could not resolve to a thingType! Manufacturer data not known.
I can’t really add a lot - clearly the secure inclusion has not worked. Without seeing the full debug log, I can’t really comment much more. Take a look at the binding docs if you haven’t enabled debug logging (and maybe also read the part about secure inclusion ).