Z-Wave Timer Errors - Nodes Offline

Add-ons Bindings
1

So I started getting some wierd errors today in my log file and associated nodes respond in the UI but don’t actually change the devices. Here is a sample error set:

2017-02-22 22:15:26.528 [WARN ] [.core.thing.binding.BaseThingHandler] - Error while applying configuration changes: 'IllegalStateException: Timer already cancelled.' - reverting configuration changes on thing 'zwave:device:b985f5e3:node13'.
2017-02-22 22:15:26.529 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalStateException: Timer already cancelled.
	at java.util.Timer.sched(Timer.java:397)[:1.8.0_121]
	at java.util.Timer.schedule(Timer.java:193)[:1.8.0_121]
	at org.eclipse.smarthome.storage.json.JsonStorage.deferredCommit(JsonStorage.java:334)[135:org.eclipse.smarthome.storage.json:0.9.0.201702100936]
	at org.eclipse.smarthome.storage.json.JsonStorage.put(JsonStorage.java:123)[135:org.eclipse.smarthome.storage.json:0.9.0.201702100936]
	at org.eclipse.smarthome.core.common.registry.AbstractManagedProvider.update(AbstractManagedProvider.java:132)[98:org.eclipse.smarthome.core:0.9.0.201702100936]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$1$1.run(ThingManager.java:217)[105:org.eclipse.smarthome.core.thing:0.9.0.201702100936]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$1$1.run(ThingManager.java:1)[105:org.eclipse.smarthome.core.thing:0.9.0.201702100936]
	at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_121]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$1.thingUpdated(ThingManager.java:205)[105:org.eclipse.smarthome.core.thing:0.9.0.201702100936]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateConfiguration(BaseThingHandler.java:478)[105:org.eclipse.smarthome.core.thing:0.9.0.201702100936]
	at org.eclipse.smarthome.core.thing.binding.ConfigStatusThingHandler.updateConfiguration(ConfigStatusThingHandler.java:65)[105:org.eclipse.smarthome.core.thing:0.9.0.201702100936]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1071)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.processNameReport(ZWaveNodeNamingCommandClass.java:265)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveNodeNamingCommandClass.handleApplicationCommandRequest(ZWaveNodeNamingCommandClass.java:127)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[204:org.openhab.binding.zwave:2.1.0.201702121033]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[204:org.openhab.binding.zwave:2.1.0.201702121033]

Happy to run a full debug log if this doesn’t jump out to what I did to my system.

2

@chris Realized this is something I was dealing with a little while back that we never figured out - Out of Memory Errors on Startup

3

It looks like patience may have been a virtue (or need to sleep). I left the system up and running overnight. It wasn’t working when I got up but I restarted it. It changed the Port for the Zwave stick but once I got that configured, now the system seems to be back up and running (though there is currently quite a bit of delay in actions, but at least it’s running). Will leave it alone to see if it stabilizes out and the lag disappears.