I have included it, and I can see it as an unknown device node, but there’s no matching XML file, I only have XML files of all my other z wave nodes
As above, if no XML is produced we need to work out why and that requires a debug log.
1 Like
Wow! You mean the binding documentation can be useful?
to where should I put the newly collected debug log? Ive tested the log here https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer and the viewer can see Node 21 but still no XML file
ehrm off topic question, a command to disable debug mode in karaf, would be very great, the NOOB 
Somewhere of your choice - some people use dropbox, others use similar services.
Just reset the log level using the same command you used previously. Eg instead of using log:set DEBUG, use WARN instead.
1 Like
The binding is requesting some information from the device, but the device doesn’t respond. It does ACK the request very quickly, so the issue isn’t related to communications problems, but the device is ignoring the request.
The initialisation is basically stuck at this point - since the binding doesn’t get the information it needs, it doesn’t produce the XML.
I’d need to see logs from earlier in the interview phase to know what’s happening 100%, but I can guess that the device is a multi channel device, and the binding is requesting information about the endpoints and the device doesn’t respond. If you have an earlier log I’m happy to have a quick look.
Possibly a defective device?
Unlikely that it’s defective as in a faulty device, but it’s quite likely that it doesn’t properly conform to the standards.
1 Like