I updated to the latest snapshot build and restarted everything.
I have exceptions during startup, in idle mode and when try to switch one device since I upgraded to the latest snapshot today.
I attached a complete log for one server startup with one action on node10.
2017-04-16 21:24:41.466 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:a62f5073:node10:switch_binary --> OFF
2017-04-16 21:24:41.469 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling handler: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:220)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:189)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:358)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:46)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:192)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:181)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
Caused by: java.lang.NullPointerException
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBinarySwitchCommandClass.setValueMessage(ZWaveBinarySwitchCommandClass.java:144)[196:org.openhab.binding.zwave:2.1.0.201704151452]
at org.openhab.binding.zwave.internal.converter.ZWaveBinarySwitchConverter.receiveCommand(ZWaveBinarySwitchConverter.java:90)[196:org.openhab.binding.zwave:2.1.0.201704151452]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleCommand(ZWaveThingHandler.java:911)[196:org.openhab.binding.zwave:2.1.0.201704151452]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:361)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:1)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:218)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
… 12 more
Unfortunately device where this eception occurs are no longer control-able via OH.
I don’t have a full system configured for the master branch, but it does run ok without any exceptions. One thing I’ve noticed is that the XML files are now badly screwed - probably due to the logger change from static . XStream is now writing them out into the XML which is making the files enormous. I’m not sure if this is causing the problem, but it’s the only thing I can see that’s wrong - other than this, it works ok here in the IDE.
I just did an apt-get update & upgrade as well. All my zwave components stopped working except virtual ones.
openhab is printing lots of java exceptions in the karaf logs
I’ve tried a few things in the last hour to try to fix the issue. I reinstalled the zwave binding and restarted the system.
No luck there.
Did a new apt-get update/upgrade. but that didnt change anything either.
Now I’ve turned on DEBUG for zwave to start gathering more logs.
Getting lots of this in the log everytime one of the nods try to communicate.
In the below snippit, I’m trying to turn on a power plug in the kitchen. (node 13) (it doesn’t turn on)
00:14:35.052 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Switch_Uttag_Kok_Lampa' received command ON
00:14:35.056 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Command received zwave:device:1593d34c72c:node13:switch_binary --> ON
00:14:35.058 [INFO ] [marthome.event.ItemStateChangedEvent] - Switch_Uttag_Kok_Lampa changed from NULL to ON
00:14:35.059 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling handler: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:220)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:189)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:358)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:46)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:192)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:181)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[: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]
Caused by: java.lang.NullPointerException
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBinarySwitchCommandClass.setValueMessage(ZWaveBinarySwitchCommandClass.java:144)[216:org.openhab.binding.zwave:2.1.0.201704151452]
at org.openhab.binding.zwave.internal.converter.ZWaveBinarySwitchConverter.receiveCommand(ZWaveBinarySwitchConverter.java:90)[216:org.openhab.binding.zwave:2.1.0.201704151452]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleCommand(ZWaveThingHandler.java:911)[216:org.openhab.binding.zwave:2.1.0.201704151452]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:361)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:1)[106:org.eclipse.smarthome.core.thing:0.9.0.201704011656]
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:218)[99:org.eclipse.smarthome.core:0.9.0.201704011656]
... 12 more
I’ve just made a change to avoid writing the loggers into the XML - I’m not really sure it will make a difference since the system works ok here either way.
I think I read that someone downgraded to the older version, but that didn’t help - is this correct (anyone)?