Error adding Zipato RGBW led bulb

Add-ons Bindings
,
1

Hej @jaydee73,

I just installed the new openhab 2 RC1 from scratch.
I discovered everthing but when I tried to add my Zipato RGBW lightbulb an error was thrown in the logs.

eventslog:

2017-01-18 20:02:34.547 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from UNINITIALIZED to INITIALIZING
2017-01-18 20:02:34.548 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from ONLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2017-01-18 20:02:34.558 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-01-18 20:02:34.590 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-01-18 20:02:34.591 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR): Could not update configuration, because callback is missing to INITIALIZING
2017-01-18 20:02:34.592 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-01-18 20:02:34.593 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-01-18 20:02:34.593 [ThingUpdatedEvent         ] - Thing 'zwave:device:e25d115d:node18' has been updated.
2017-01-18 20:02:34.597 [ThingUpdatedEvent         ] - Thing 'zwave:device:e25d115d:node18' has been updated.
2017-01-18 20:02:34.598 [hingStatusInfoChangedEvent] - 'zwave:device:e25d115d:node18' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): Could not update configuration, because callback is missing
2017-01-18 20:02:34.598 [ConfigStatusInfoEvent     ] - ConfigStatusInfo [configStatusMessages=[]]

And openhab logs:

017-01-18 20:02:34.560 [WARN ] [.core.thing.binding.BaseThingHandler] - Error while applying configuration changes: 'IllegalStateException: Could not update configuration, because callback is missing' - reverting configuration changes on thing 'zwave:device:e25d115d:node18'.
2017-01-18 20:02:34.566 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while initializing handler of thing 'zwave:device:e25d115d:node18': java.lang.IllegalStateException: Could not update configuration, because callback is missing
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Could not update configuration, because callback is missing
	at java.util.concurrent.FutureTask.report(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.FutureTask.get(Unknown Source)[:1.8.0_111]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:188)[98:org.eclipse.smarthome.core:0.9.0.b3]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:81)[98:org.eclipse.smarthome.core:0.9.0.b3]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:65)[98:org.eclipse.smarthome.core:0.9.0.b3]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9.run(ThingManager.java:710)[105:org.eclipse.smarthome.core.thing:0.9.0.b3]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.FutureTask.run(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[:1.8.0_111]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[:1.8.0_111]
	at java.lang.Thread.run(Unknown Source)[:1.8.0_111]
Caused by: java.lang.IllegalStateException: Could not update configuration, because callback is missing
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateConfiguration(BaseThingHandler.java:480)[105:org.eclipse.smarthome.core.thing:0.9.0.b3]
	at org.eclipse.smarthome.core.thing.binding.ConfigStatusThingHandler.updateConfiguration(ConfigStatusThingHandler.java:65)[105:org.eclipse.smarthome.core.thing:0.9.0.b3]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.updateNodeProperties(ZWaveThingHandler.java:1401)[209:org.openhab.binding.zwave:2.0.0.RC1]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:454)[209:org.openhab.binding.zwave:2.0.0.RC1]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:147)[209:org.openhab.binding.zwave:2.0.0.RC1]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:713)[105:org.eclipse.smarthome.core.thing:0.9.0.b3]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$9$1.call(ThingManager.java:1)[105:org.eclipse.smarthome.core.thing:0.9.0.b3]
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:179)[98:org.eclipse.smarthome.core:0.9.0.b3]
	at java.util.concurrent.FutureTask.run(Unknown Source)[:1.8.0_111]
	... 3 more
2017-01-18 20:02:34.590 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Initialising Thing Node...

Is this normal or should I be worried? :slight_smile:

2

eh, couldn’t edit the post, however, could the error be that i tried to add too many things too fast?

3

Hard to say. Sometimes the binding throws an exception during the initialization. I have also seen this before. Normally the device is added nevertheless.

Yes, when too many devices are added at the same time, it could lead to problems. Let it run for a couple of hours, maybe things will sort themselves…

4

I see another thread with this error so I will try and look at this as soon as I have time (I hope tonight).

5

The devices are added and works so I think it’s due to me being to quick to add several items at the same time.
As always, great work with the z-wave binding!

6

Hi, I have also a problem with this device. The discovery doesn’t work. This is in the log:

2017-01-26 22:45:02.771 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Timeout while sending message. Requeueing - 2 attempts left!
2017-01-26 22:45:02.772 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 13: Got an error while sending data. Resending message.
2017-01-26 22:45:07.777 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Timeout while sending message. Requeueing - 1 attempts left!
2017-01-26 22:45:07.778 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 13: Got an error while sending data. Resending message.
2017-01-26 22:45:12.817 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Timeout while sending message. Requeueing - 0 attempts left!
2017-01-26 22:45:12.818 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 13: Got an error while sending data. Resending message.
2017-01-26 22:45:17.844 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=13, callback=79, payload=0D 02 26 02
2017-01-26 22:47:18.529 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-01-26 22:47:37.768 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Node advancer: Retries exceeded at DYNAMIC_VALUES
2017-01-26 22:48:23.885 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Initialising Thing Node…

Anyone an idea?
How can I wakeup this device manually? I taped the bulb, switched to green light but that’s all…

7

You can’t - it’s a mains device so it doesn’t support wakeup.

Given it’s timing out, either it’s too far from the controller, or it’s not included properly, or something else is wrong - for which we’d need to see a debug logfile to comment on…

8

Included again, now it works. Thanks.