[FIXED] Z-Stick GEN5 not working with openHAB and zwave binding

I tried everything I was able to find on the internet to get my new Z-Stick GEN5 up and running with openHAB and the zwave binding.

This is the content of the log when sarting the server, (I removed many many duplicate lines telling Error 0x16)

Launching the openHAB runtime... osgi> 2016-03-04 23:11:46.687 [WARN ] [o.config.core.ConfigDispatcher] - Main openHAB configuration file 'configurations/openhab.cfg' does not exist. 2016-03-04 23:11:46.734 [INFO ] [.o.core.internal.CoreActivator] - openHAB runtime has been started (v1.8.1). 2016-03-04 23:11:48.765 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - mDNS service has been started 2016-03-04 23:11:49.390 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - Service Discovery initialization completed. 2016-03-04 23:11:52.362 [INFO ] [penhab.io.rest.RESTApplication] - Started REST API at /rest 2016-03-04 23:11:59.707 [INFO ] [.o.u.w.i.servlet.WebAppServlet] - Started Classic UI at /classicui/openhab.app 2016-03-04 23:12:03.466 [INFO ] [.o.io.habmin.HABminApplication] - Started HABmin REST API at /services/habmin 2016-03-04 23:12:08.810 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht.. Write action failed! Input/output errorError 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht.. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht.. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht.. Error 0x16 at src/windows/termios.c(512): Das Gerõt erkennt den Befehl nicht..

The error messages are spamming the log file very fast.

My configuration is as following:

zwave:port=COM3 zwave:healtime=4 zwave:softReset=false zwave:masterController=true

The port is correct. I tried it in the IMAtool. There the stick and a switch that I added to the network is shown correctly.

Is there anyone out there who knows this phenomenon and is able to help me solve the problem. I’m stumped.

I’m using gen 5 stick with Ubuntu and it’s working fine.

I just started and not that familIar with openhab yet.

From your log, it seems that your openhab.cfg does not exist, maybe you can start looking at that.

You are quite right. Sorry for taking the wrong shot… I corrected that and it does not change anything. I found some information in the zwave.log. But I do not know how I solve the problem…

2016-03-05 11:18:51.997 [DEBUG] [.zwave.internal.ZWaveActivator:36 ]- Z-Wave binding has been started. 2016-03-05 11:18:52.035 [INFO ] [.z.internal.ZWaveActiveBinding:301 ]- Update config, port = COM3 2016-03-05 11:18:52.036 [INFO ] [.z.internal.ZWaveActiveBinding:306 ]- Update config, healtime = 4 2016-03-05 11:18:52.099 [INFO ] [b.z.i.protocol.ZWaveController:136 ]- Starting Z-Wave controller 2016-03-05 11:18:52.099 [INFO ] [b.z.i.protocol.ZWaveController:141 ]- Z-Wave timeout is set to 5000ms. 2016-03-05 11:18:52.100 [INFO ] [b.z.i.protocol.ZWaveController:299 ]- Connecting to serial port COM3 2016-03-05 11:18:52.107 [DEBUG] [.z.internal.ZWaveActiveBinding:98 ]- Zwave Network isn't ready yet! 2016-03-05 11:18:53.282 [DEBUG] [eController$ZWaveReceiveThread:998 ]- Starting Z-Wave receive thread 2016-03-05 11:18:53.283 [INFO ] [b.z.i.protocol.ZWaveController:312 ]- Serial port is initialized 2016-03-05 11:18:53.288 [DEBUG] [WaveController$ZWaveSendThread:855 ]- Starting Z-Wave send thread 2016-03-05 11:18:53.293 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 255: Creating empty message of class = SerialApiSoftReset (0x08), type = Request (0x00) 2016-03-05 11:18:53.294 [DEBUG] [o.b.z.i.protocol.SerialMessage:226 ]- Assembled message buffer = 01 03 00 08 F4 2016-03-05 11:18:53.332 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 255: Creating empty message of class = GetVersion (0x15), type = Request (0x00) 2016-03-05 11:18:53.333 [DEBUG] [b.z.i.protocol.ZWaveController:389 ]- Enqueueing message. Queue length = 1 2016-03-05 11:18:53.333 [DEBUG] [WaveController$ZWaveSendThread:860 ]- Took message from queue for sending. Queue length = 0 2016-03-05 11:18:53.334 [DEBUG] [o.b.z.i.protocol.SerialMessage:226 ]- Assembled message buffer = 01 03 00 15 E9 2016-03-05 11:18:53.334 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 255: Creating empty message of class = MemoryGetId (0x20), type = Request (0x00) 2016-03-05 11:18:53.334 [DEBUG] [b.z.i.protocol.ZWaveController:389 ]- Enqueueing message. Queue length = 1 2016-03-05 11:18:53.339 [DEBUG] [WaveController$ZWaveSendThread:889 ]- Sending Message = 01 03 00 15 E9 2016-03-05 11:18:53.340 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 255: Creating empty message of class = SerialApiGetCapabilities (0x07), type = Request (0x00) 2016-03-05 11:18:53.341 [DEBUG] [b.z.i.protocol.ZWaveController:389 ]- Enqueueing message. Queue length = 2 2016-03-05 11:18:53.342 [DEBUG] [i.p.s.GetSucNodeIdMessageClass:30 ]- Get SUC NodeID 2016-03-05 11:18:53.342 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 255: Creating empty message of class = GetSucNodeId (0x56), type = Request (0x00) 2016-03-05 11:18:53.343 [DEBUG] [b.z.i.protocol.ZWaveController:389 ]- Enqueueing message. Queue length = 3 2016-03-05 11:18:54.641 [ERROR] [eController$ZWaveReceiveThread:1028]- Got I/O exception No error in readByte during receiving. exiting thread. 2016-03-05 11:18:54.641 [DEBUG] [eController$ZWaveReceiveThread:1093]- Stopped Z-Wave receive thread 2016-03-05 11:18:57.108 [DEBUG] [.z.internal.ZWaveActiveBinding:98 ]- Zwave Network isn't ready yet! 2016-03-05 11:18:58.341 [ERROR] [WaveController$ZWaveSendThread:921 ]- NODE 255: Timeout while sending message. Requeueing 2016-03-05 11:18:58.341 [DEBUG] [b.z.i.protocol.ZWaveController:389 ]- Enqueueing message. Queue length = 4 2016-03-05 11:18:58.342 [DEBUG] [WaveController$ZWaveSendThread:860 ]- Took message from queue for sending. Queue length = 3 2016-03-05 11:18:58.343 [DEBUG] [o.b.z.i.protocol.SerialMessage:226 ]- Assembled message buffer = 01 03 00 15 E9 2016-03-05 11:18:58.344 [DEBUG] [WaveController$ZWaveSendThread:889 ]- Sending Message = 01 03 00 15 E9 2016-03-05 11:18:58.552 [ERROR] [WaveController$ZWaveSendThread:897 ]- Got I/O exception Input/output error in writeArray during sending. exiting thread. 2016-03-05 11:18:58.553 [DEBUG] [WaveController$ZWaveSendThread:942 ]- Stopped Z-Wave send thread 2016-03-05 11:19:02.108 [DEBUG] [.z.internal.ZWaveActiveBinding:98 ]- Zwave Network isn't ready yet! 2016-03-05 11:19:03.285 [WARN ] [veController$WatchDogTimerTask:1127]- Threads not alive, respawning 2016-03-05 11:19:03.986 [INFO ] [b.z.i.protocol.ZWaveController:380 ]- Disconnected from serial port 2016-03-05 11:19:03.987 [INFO ] [b.z.i.protocol.ZWaveController:299 ]- Connecting to serial port COM3 2016-03-05 11:19:04.002 [INFO ] [b.z.i.protocol.ZWaveController:312 ]- Serial port is initialized 2016-03-05 11:19:04.002 [DEBUG] [eController$ZWaveReceiveThread:998 ]- Starting Z-Wave receive thread 2016-03-05 11:19:04.002 [DEBUG] [WaveController$ZWaveSendThread:855 ]- Starting Z-Wave send thread 2016-03-05 11:19:04.003 [DEBUG] [WaveController$ZWaveSendThread:860 ]- Took message from queue for sending. Queue length = 2

The messages repeate…

It seems there’s some sort of serial driver exception - what hardware are you using?

AEOTEC Z-Stick Gen5 .

Windows 10 on a NUC.

Prozessor Intel® Celeron® CPU N2830 @ 2.16GHz, 2159 MHz, 2 Kern(e), 2 logische® Prozessor(en)

No - I meant what computer hardware!

Prozessor Intel® Celeron® CPU N2830 @ 2.16GHz, 2159 MHz, 2 Kern(e), 2 logische® Prozessor(en)

BIOS-Version/-Datum Intel Corp. FYBYT10H.86A.0034.2014.0513.1413, 13.05.2014

Windows 10 Home

Got it working by reinstalling a fresh version of openhab 1.8.1

The only difference to the last installation seems to be, that I am now working with binding version 1.8.0.

I’m not sure what fixed it. I’m sorry for the inconvenience and many thanks for your help!