Z wave issues

Hi,

I am totally new to zwave and openhab and unfortunately I am having issues with getting my Aeotec ZW090-C Z-Wave USB Adapter with Battery GEN5 and Aeon Labs Multisensor 6 - Z-Wave Plus working.

I have done the following

  1. Paired the stick with the sensor as directed in the instructions that came with the sensor and stick

  2. I have a wifi dongle attached to my raspberry pi 2 and have placed the stick into another usb port on the raspberry pie

  3. I have made sure that I am using zwave binding 1.8.0-snapshot.jar

  4. I have changed the openhab.cfg so that the zwave config is as follows:

    ################################ Z-Wave Binding ######################################

    The Z-Wave controller port. Valid values are e.g. COM1 for Windows and /dev/ttyS0 or

    /dev/ttyUSB0 for Linux

    #zwave:port=/dev/ttyUSB0
    zwave:port=/dev/ttyACM0

    Z-Wave nightly heal time. This is the hour (eg 2AM) at which the automatic nightly

    network heal will be performed.

    zwave:healtime=2

  5. I have followed the instruction from http://www.makeuseof.com/tag/openhab-beginners-guide-part-2-zwave-mqtt-rules-charting/

and executed the following command

sudo usermod -a -G dialout openhab

  1. I have the following messages when the sensor is on and the stick is plugged in. Both are within site of each other.

    2015-11-29 18:55:53.882 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
    2015-11-29 18:55:53.884 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
    2015-11-29 18:55:53.885 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM0
    RXTX Warning: Removing stale lock file. /var/lock/LCK…ttyACM0
    2015-11-29 18:55:54.023 [INFO ] [b.z.i.protocol.ZWaveController] - Serial port is initialized
    2015-11-29 18:55:54.774 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
    2015-11-29 18:55:54.783 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
    2015-11-29 18:55:54.799 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
    2015-11-29 18:55:54.815 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
    2015-11-29 18:55:57.052 [ERROR] [eController$ZWaveReceiveThread] - Message is not valid, discarding
    2015-11-29 18:55:57.055 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (NAK), discarding
    2015-11-29 18:55:57.066 [WARN ] [eController$ZWaveReceiveThread] - Protocol error (OOF). Got 0x5A. Sending NAK.
    2015-11-29 18:56:02.065 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
    2015-11-29 18:56:07.068 [WARN ] [WaveController$ZWaveSendThread] - Receive queue TIMEOUT:

— Any help would be much appreciated

You really need to provide a debug log - otherwise it’s pretty much impossible to say what’s happening… Take a look at the zwave wiki - toward the bottom of the page there’s information on how to configure this.

I found that Im getting the following message in the debug log

19:31:57.708 [DEBUG] [.zwave.internal.ZWaveActivator:36   ] - Z-Wave binding started. Version 1.8.0.201511280245
19:31:57.761 [DEBUG] [.z.internal.ZWaveActiveBinding:175  ] - ConverterHandler not initialised. Polling disabled.
19:31:57.764 [INFO ] [.z.internal.ZWaveActiveBinding:325  ] - Update config, port = /dev/ttyACM0
19:31:57.766 [INFO ] [.z.internal.ZWaveActiveBinding:330  ] - Update config, healtime = 2
19:31:57.768 [DEBUG] [.z.internal.ZWaveActiveBinding:282  ] - Initialising zwave binding
19:31:57.771 [INFO ] [.service.AbstractActiveService:169  ] - ZWave Refresh Service has been started
19:31:57.859 [INFO ] [b.z.i.protocol.ZWaveController:148  ] - Starting Z-Wave controller
19:31:57.866 [INFO ] [b.z.i.protocol.ZWaveController:156  ] - Z-Wave timeout is set to 5000ms. Soft reset is false.
19:31:57.868 [INFO ] [b.z.i.protocol.ZWaveController:322  ] - Connecting to serial port /dev/ttyACM0

Serial Error: Port /dev/ttyACM0 does not exist

Ok so I have done the command’
ls /dev/tty*

and found that the config should have been /dev/ttyACM1

I changed that now I have the following messages

2015-11-29 19:45:44.836 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyACM1
2015-11-29 19:45:44.838 [INFO ] [.z.internal.ZWaveActiveBinding] - Update config, healtime = 2
2015-11-29 19:45:44.842 [INFO ] [.service.AbstractActiveService] - ZWave Refresh Service has been started
2015-11-29 19:45:44.930 [INFO ] [b.z.i.protocol.ZWaveController] - Starting Z-Wave controller
2015-11-29 19:45:44.931 [INFO ] [b.z.i.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2015-11-29 19:45:44.933 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM1
2015-11-29 19:45:45.063 [INFO ] [.service.AbstractActiveService] - XBMC Refresh Service has been started
2015-11-29 19:45:45.085 [INFO ] [b.z.i.protocol.ZWaveController] - Serial port is initialized
2015-11-29 19:45:45.552 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
2015-11-29 19:45:45.559 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
2015-11-29 19:45:45.580 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
2015-11-29 19:45:45.597 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
2015-11-29 19:45:45.624 [WARN ] [ApplicationCommandMessageClass] - NODE 2: Not initialized yet, ignoring message.
2015-11-29 19:45:46.651 [ERROR] [eController$ZWaveReceiveThread] - Exception during Z-Wave thread: Receive     java.lang.ArrayIndexOutOfBoundsException: 1
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveReceiveThread.run(ZWaveController.java:1468) ~[na:na]
2015-11-29 19:45:53.099 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-11-29 19:45:55.090 [WARN ] [veController$WatchDogTimerTask] - Threads not alive, respawning
2015-11-29 19:45:55.101 [ERROR] [WaveController$ZWaveSendThread] - Exception during Z-Wave thread: Send
java.lang.InterruptedException: null
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1039) ~[na:1.8.0]
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) ~[na:1.8.0]
	at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:582) ~[na:1.8.0]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveSendThread.run(ZWaveController.java:1202) ~[na:na]
2015-11-29 19:45:55.110 [INFO ] [b.z.i.protocol.ZWaveController] - Disconnected from serial port
2015-11-29 19:45:55.112 [INFO ] [b.z.i.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM1
2015-11-29 19:45:55.123 [INFO ] [b.z.i.protocol.ZWaveController] - Serial port is initialized
2015-11-29 19:45:55.437 [INFO ] [rialApiGetInitDataMessageClass] - NODE 1: Node found
2015-11-29 19:45:55.439 [INFO ] [rialApiGetInitDataMessageClass] - NODE 2: Node found
2015-11-29 19:45:55.441 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2015-11-29 19:45:55.442 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2015-11-29 19:45:55.442 [INFO ] [rialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2015-11-29 19:45:55.443 [INFO ] [rialApiGetInitDataMessageClass] - # Nodes = 2
2015-11-29 19:45:55.445 [INFO ] [rialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2015-11-29 19:45:56.871 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 2: No item bound for event, endpoint = 0, command class = SENSOR_BINARY, value = 0, ignoring.
2015-11-29 19:45:58.289 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 2: No item bound for event, endpoint = 0, command class = BATTERY, value = 100, ignoring.
2015-11-29 19:45:58.814 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 2: No item bound for event, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 25.3, ignoring.
2015-11-29 19:46:01.948 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 2: No item bound for event, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 0E+1, ignoring.

Your OH discovered the network and communicates with it.

2015-11-29 19:45:55.437 [INFO ] [rialApiGetInitDataMessageClass] - NODE 1: Node found
2015-11-29 19:45:55.439 [INFO ] [rialApiGetInitDataMessageClass] - NODE 2: Node found
2015-11-29 19:45:55.441 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2015-11-29 19:45:55.442 [INFO ] [rialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2015-11-29 19:45:55.442 [INFO ] [rialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2015-11-29 19:45:55.443 [INFO ] [rialApiGetInitDataMessageClass] - # Nodes = 2

Now you need to create items that will represent the z-wave nodes…
ZWaveActiveBinding] - NODE 2: No item bound for event, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 25.3, ignoring.

Like:
Number Sensor_Temp "Temperature [%.2f °C]" <temperature> { zwave="2:command=sensor_multilevel" }

Check the thread with working z-wave binding configs to learn more.

Good luck.

1 Like

Thank you, ill try that.

I dont like to beg for help here without trying to solve the problem also. As you can see I have tried to find the answer.

Take a look at the wiki - there’s a lot of information there about defining items there. Additionally, people have added information in the forum, so try a search.

There’s also the following thread which contains a lot of configs for zwave…

1 Like

I have resolved this issue by modifying the items file and it now works.

Thank you for your help