Suddenly all Zwave devices are GONE! Can someone help?

dinki · July 14, 2016, 8:41pm

We had a power outtage last night and when the power came back on I noticed that I could not control one of my Zwave lamp switches. I tried doing a heal on the node and reinitialize, but that didn’t work. I then tried a heal on the network but that didn’t work either. I just got home and could not control a different lamp module. I rebooted the server and now when I go into habmin and look a Zwave binding I do not see anything listed. Not even my controller.

Here’s my openhab.log file:

http://pastebin.com/0TFLHybf

and my zwave.log file:

2016-07-14 15:29:57.236 [INFO ] [.z.internal.ZWaveActiveBinding:337 ]- Update config, port = COM7
2016-07-14 15:29:57.237 [INFO ] [.z.internal.ZWaveActiveBinding:342 ]- Update config, healtime = 2
2016-07-14 15:29:57.247 [INFO ] [b.z.i.protocol.ZWaveController:152 ]- Starting Z-Wave controller
2016-07-14 15:29:57.247 [INFO ] [b.z.i.protocol.ZWaveController:160 ]- Z-Wave timeout is set to 5000ms. Soft reset is false.
2016-07-14 15:29:57.247 [INFO ] [b.z.i.protocol.ZWaveController:326 ]- Connecting to serial port COM7
2016-07-14 15:29:58.551 [INFO ] [b.z.i.protocol.ZWaveController:347 ]- Serial port is initialized
2016-07-14 15:30:06.559 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-14 15:30:11.561 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-14 15:30:16.564 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-14 15:30:21.565 [WARN ] [WaveController$ZWaveSendThread:1355]- NODE 255: Too many retries. Discarding message: Message: class = GetVersion (0x15), type = Request (0x00), payload = 
2016-07-14 15:30:26.567 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-14 15:30:31.570 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-14 15:30:36.572 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-14 15:30:41.574 [WARN ] [WaveController$ZWaveSendThread:1355]- NODE 255: Too many retries. Discarding message: Message: class = MemoryGetId (0x20), type = Request (0x00), payload = 
2016-07-14 15:30:46.576 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-14 15:30:51.579 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-14 15:30:56.580 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-14 15:31:01.582 [WARN ] [WaveController$ZWaveSendThread:1355]- NODE 255: Too many retries. Discarding message: Message: class = SerialApiGetCapabilities (0x07), type = Request (0x00), payload = 
2016-07-14 15:31:06.585 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-14 15:31:11.587 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-14 15:31:16.589 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-14 15:31:21.591 [WARN ] [WaveController$ZWaveSendThread:1355]- NODE 255: Too many retries. Discarding message: Message: class = SerialApiSetTimeouts (0x06), type = Request (0x00), payload = 96 0F 
2016-07-14 15:31:26.594 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-07-14 15:31:31.595 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-07-14 15:31:36.597 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-07-14 15:31:39.204 [ERROR] [eController$ZWaveReceiveThread:1486]- Got I/O exception No error in readByte during receiving. exiting thread.
2016-07-14 15:31:41.600 [WARN ] [WaveController$ZWaveSendThread:1355]- NODE 255: Too many retries. Discarding message: Message: class = GetSucNodeId (0x56), type = Request (0x00), payload = 
2016-07-14 15:31:48.557 [WARN ] [veController$WatchDogTimerTask:1604]- Threads not alive, respawning
2016-07-14 15:31:48.558 [ERROR] [WaveController$ZWaveSendThread:1243]- InterruptedException during Z-Wave thread: sendQueue.take {}
java.lang.InterruptedException: null
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014) ~[na:1.8.0_60]
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048) ~[na:1.8.0_60]
	at java.util.concurrent.PriorityBlockingQueue.take(PriorityBlockingQueue.java:549) ~[na:1.8.0_60]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveSendThread.run(ZWaveController.java:1240) ~[na:na]
2016-07-14 15:31:48.568 [INFO ] [b.z.i.protocol.ZWaveController:433 ]- Disconnected from serial port
2016-07-14 15:31:48.568 [INFO ] [b.z.i.protocol.ZWaveController:326 ]- Connecting to serial port COM7
2016-07-14 15:31:48.756 [INFO ] [b.z.i.protocol.ZWaveController:347 ]- Serial port is initialized

I did pull the Zstick and reinsert it so you can see that in the log file above.

Does anyone have any idea on what I can do to get these devices back?

chris · July 14, 2016, 8:47pm

It looks like the stick is not responding to any messages. From this I’d hazard a guess that the stick is dead, but it might be something else (I guess).

dinki · July 14, 2016, 8:54pm

Thanks for the speedy reply. I changed ports and rebooted again and now I see my devices and can control some. I looked in habmin and see a few reds including the controller:

Is my stick dying? Any suggestions on getting things working again?

chris · July 14, 2016, 8:58pm

I’m not sure - clearly it’s not 100% dead as it seems to be responding. I’m not sure why the controller would show red - I guess it’s not responding to some messages, but without looking at the log, it’s hard to be sure.

You could put the binding into debug log mode and look at the log using the online log viewer (www.cd-jackson.com) - that might help to show what’s up…