Zwave exceptions and ghost node

Hi there,

I’m a ZWave noob and tried to get a foot on deck by connecting a Zwave.me stick to my Raspberry Pi 2 / openhab2 installation with the zwave 1.9 binding.

After configuring the port (serial-device), it seems to be detected. However, I get strange exceptions, I don’t understand. Anyone can interpret them for me? Currently, I have only the stick, no other nodes (they are in delivery), so I have no idea what Node 2 could be. I doubt, that any of my neighbours might had Zwave nodes…

    19:04:59.826 [INFO ] [ng.zwave.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyACM0
    19:04:59.827 [INFO ] [ng.zwave.internal.ZWaveActiveBinding] - Update config, healtime = 3
    19:04:59.830 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - InterruptedException during Z-Wave thread: sendQueue.take {}
    java.lang.InterruptedException
            at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)[:1.8.0]
            at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048)[:1.8.0]
            at java.util.concurrent.PriorityBlockingQueue.take(PriorityBlockingQueue.java:549)[:1.8.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveSendThread.run(ZWaveController.java:1240)[162:org.openhab.binding.zwave:1.9.0.201603040                                                     213]
    19:05:00.549 [INFO ] [ve.internal.protocol.ZWaveController] - Disconnected from serial port
    19:05:00.554 [INFO ] [ve.internal.protocol.ZWaveController] - Stopped Z-Wave controller
    19:05:00.555 [INFO ] [ve.internal.protocol.ZWaveController] - Starting Z-Wave controller
    19:05:00.556 [INFO ] [ve.internal.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
    19:05:00.557 [INFO ] [ve.internal.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM0
    19:05:00.567 [INFO ] [ve.internal.protocol.ZWaveController] - Serial port is initialized
    19:05:00.574 [ERROR] [org.openhab.ui.habmin               ] - [org.openhab.binding.zwave.configuration(43)] bind method [addConfigurationService] not found
    19:05:03.629 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during Z-Wave thread: Input.
    java.lang.NullPointerException
            at org.openhab.binding.zwave.internal.protocol.SerialMessage.getMessageBuffer(SerialMessage.java:219)[162:org.openhab.binding.zwave:1.9.0.201603040213]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1195)[162:org.openhab.binding.zwave:1.9.0.20160304                                                     0213]
    19:05:03.804 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
    19:05:03.805 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 2: Node found
    19:05:03.807 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
    19:05:03.808 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
    19:05:03.808 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
    19:05:03.810 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 2
    19:05:03.811 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
    19:05:09.101 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
    19:05:13.221 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Got an error while sending data. Resending message.
    19:05:17.374 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:05:21.553 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:05:25.658 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:05:44.003 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:06:24.019 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:06:43.639 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:07:43.976 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:08:13.641 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:09:43.690 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:10:19.871 [ERROR] [nitialization.ZWaveNodeStageAdvancer] - NODE 2: Node advancer: Retries exceeded at PING
    19:11:13.647 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:12:43.666 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.
    19:14:13.640 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 2: Node is DEAD. Dropping message.

The message about the dead node seems to continue on and on. This does not look right, is it?
Is openhab2 (beta) and zwave 1.9 the recommended combination (stable?) or should I try zwave 2?

Cheers,
Hauke

I believe the recommended configuration is zwave 2.

Have you installed and configured habmin? That is the user interface to administering your zwave network. If the controller has marked Node 2 as dead you can remove it from there and then try re-adding the node to your network.