If you have other zwave devices, you must not be in the right directory. For an apt-get (like openHABian is), it would be /var/lib/openhab2/zwave. It’s a mains powered device, so initialization should be quick (slower for a battery powered device). I expect the file to be there, you just need to find it!
I’m not familiar with openHABian, but that share sure looks like it would be the right place.
Once your device initializes, it may be recognized. It looks like you’re in the right directory. I take it the zwave directory is empty? Is the file browser your using hiding certain file types? But that’s assuming the device is initialized. You did include it, right? What does the device look like in Habmin? If it is not initialized, I’d suggest turning on debug for the zwave binding (log:set DEBUG org.openhab.binding.zwave) in Karaf, restart OH, and see if the log has anything helpful in it. Just remember to set it to INFO when you’re done.
I think the device is the same, exept a swiss plug. Not Schuko.
The folder is still empty, also no hidden file.
Turned on the debug logging now. Looks good but there are some errors which I don’t know where they come from:
2018-07-21 22:08:38.093 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 31ms/4611ms.
2018-07-21 22:08:39.501 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$EmptySet, genericType=class java.util.Collections$EmptySet.
2018-07-21 22:08:40.382 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
You’re issue right now appears to be that the device is not initializing. Once initialized, you’ll have an xml file. If the device is identified, you’re all set. If not, it may be as simple as adding the type/id to the existing device. The logs will be the only way to determine why it is not initializing. You can view the log better with the log viewer, but if you post it somewhere I’ll take a look.
That error shouldn’t affect anything. It’s already been resolved in a snapshot build.
I’ve not looked at the log in any detail, but node 9 is not initialising as the device is not responding to the manufacturer data request -:
The binding keeps requesting this data, but it never gets the information. The device is receiving the request from the binding as there is an ACK, but it’s not sending the data that is needed.
edit: other nodes look to be doing the same thing - at least nodes 10, 11 and 12. This is pretty strange - are all these nodes exactly the same? It could be that the controller is faulty (not receiving properly) - it does seem a little unlikely, but no more so than every device not responding to a fundamental request like this.
Initialization is done during inclusion, but there is a partial initialization that is done when the binding (or OH) restarts.
Are you resetting the device and then including it again? This will leave nodes in the controller, that you can remove through Habmin> Configuration> Things> select Thing> Tools> Advanced> Remove device from the controller
You may need to set it as failed first though.
Do you only have the one device? There are 12 node IDs, so it looks like you have included it 11 times. I looks like a node is working it’s way through initialization, a new discovery is started, and a new node pops up. Try cleaning up the old nodes, then shut down OH, delete the openhab.log file, power cycle the device, power cycle the Pi, and then restart OH. Don’t do anything… just wait about 10 minutes. Then send another log. I doubt it will have much more info, but it should be a lot easier to read through. And restarting the Pi should power cycle the controller, which could help.
Hello, sorry for the delayed answer.
I did a reset of the controller Sigma Designs - Controller USB Z-Wave Plus with the zipgateway and raspberry pi.
Also the devices (3 in sum) seems to work with the controller and the zipgateway software.
But I would not say that the controller is for sure 100 % OK. I can be an issue.
So I did the test with the new boot and added the log.
The controller is connected directly over the USB and the local interface of the raspberry.
Maybe you see what is wrong, or what should I try next?
Using the zipgateway is likely the source of the issue that @chris pointed out. Is it possible to connect the controller directly to the device running OH? Even just to test? If not, you may want to test one of the other serial over IP solutions to see if they cause the same problem.
ZIP Gateway is a Sigma IP to ZWave implementation that handles all the low level communication with the stick. It doesn’t handle anything to do with higher level device communication, but it sorts out network management, encapsulation etc.
I installed an other instance of openHAB running on my windows PC. The Z-wave stick is shown as a ‘serial USB device’ with COM-Port Number.
So I did the same and added the new device (node).
But the result is still the same: The device is shown as an ‘unkown device’. Also there is no file written unter:
So the question is again: How do I get the needed information to add the ‘new’ Z-Wave device to the database?