Many zwave errors in openhab.log

Add-ons Bindings
1

Hello Chris,

these errors occure all the time in my logfile:
Doesn’t matter if battery devices or not. Node 2 and 40 are Aeotec Micro Smart Energy Illuminator G2 and Node 26 is a Stella-Z thermostat

2016-12-07 07:28:33.589 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 40: Timeout while sending message. Requeueing - 2 attempts left!
2016-12-07 07:28:33.590 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 40: Got an error while sending data. Resending message.
2016-12-07 07:28:38.609 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 40: Timeout while sending message. Requeueing - 1 attempts left!
2016-12-07 07:28:38.610 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 40: Got an error while sending data. Resending message.
2016-12-07 07:28:43.629 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 40: Timeout while sending message. Requeueing - 0 attempts left!
2016-12-07 07:28:43.630 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 40: Got an error while sending data. Resending message.
2016-12-07 07:28:48.650 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 40: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=40, callback=9, payload=28 03 32 01 28
2016-12-07 07:28:53.669 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 26: Timeout while sending message. Requeueing - 1 attempts left!
2016-12-07 07:28:54.700 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
2016-12-07 07:28:59.719 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-12-07 07:28:59.722 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
2016-12-07 07:29:04.739 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-12-07 07:29:04.741 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
2016-12-07 07:29:09.759 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-12-07 07:29:09.761 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
2016-12-07 07:29:14.779 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=2, callback=21, payload=02 03 32 01 28
2016-12-07 07:29:19.836 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 0: Polling aborted due to exception
java.lang.NullPointerException
        at org.openhab.binding.zwave.handler.ZWaveThingHandler$1.run(ZWaveThingHandler.java:360)[198:org.openhab.binding.zwave:2.0.0.201612051634]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_111]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_111]
        at java.lang.Thread.run(Thread.java:745)[:1.8.0_111]
2

Did you update the zwave binding while openHAB was running?
Then it might be related to

It looks like a simple reboot solves the problem.

3

No openhab was stopped for the snapshot update. I have this error for a long time and versions now even after a few reboots

4

@chris : have you seen this topic? :slight_smile:

5

No - sorry, I missed this.

For the “Node 0” problem - I’ve seen this error before. I think (not certain though!) that it might be associated with a node that’s not properly initialised - do you have any nodes like that?

For the timeouts, I’m not sure there’s much I can say - timeouts happen from time to time and without more information from a debug log, and knowing if it’s systematic or not, I can’t really say too much more…