[SOLVED] Adding Zipato RGBW bulb to OpenHab issues

Hi all,

I’m a complete beginner to Z-Wave and OpenHab and am having problems with my first go. I’m using OpenHab 2.0.0 release, with an Aeon Gen 5 Z-Stick and a Zipato RGBW bulb. The bulb is in my desk light and the server is located in the next room, about 3 metres away. There is a thick wall in between. OpenHab immediately sees the bulb and adds it, but immediately after it declares the node DEAD - I’ve tried what others did to make the bulb work, but not having any luck - am hoping someone can help me please? I’ve already tried reinstalling OpenHab, healing the node, and a few others. I’ve even tried changing the bulb as I’ve got two of them, but the exact same error occurs.

2017-03-30 00:13:01.889 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
2017-03-30 00:13:01.904 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2017-03-30 00:13:01.905 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2017-03-30 00:13:01.936 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2017-03-30 00:13:01.936 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2017-03-30 00:13:05.099 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2017-03-30 00:13:05.099 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 2: Node found
2017-03-30 00:13:05.100 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2017-03-30 00:13:05.100 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2017-03-30 00:13:05.100 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2017-03-30 00:13:05.100 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 2
2017-03-30 00:13:05.101 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2017-03-30 00:13:05.375 [WARN ] [rialmessage.IsFailedNodeMessageClass] - NODE 2: Is currently marked as failed by the controller!
2017-03-30 00:13:09.507 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
2017-03-30 00:13:14.490 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
2017-03-30 00:13:15.627 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2017-03-30 00:13:15.632 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-03-30 00:13:15.639 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:5cd69f06:node2' to inbox.
2017-03-30 00:13:24.507 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
2017-03-30 00:13:26.758 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising Thing Node...
2017-03-30 00:13:44.536 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
2017-03-30 00:14:24.504 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
2017-03-30 00:15:44.460 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.

Advice on how can I fix this issue would be greatly appreciated? Many thanks!

Update: I turned the light fitting around so the bulb has a “clear line of sight” to the server and it works! The light fitting is metal which might have affected the radio signal. It seems that the range is really disappointing, that those two struggles to communicate over 3 metres.