OH2.2: zwave binding v1.x works / v2.2 doesn't work

Setup, Configuration and Use Installation
,
1

Windows 10 64 bit
OH 2.2 (release build)

Zwave devices:

  • 1x Aeon Labs USB stick Z-Stick Gen5
  • 1x Aeotec Range Extender (EU) DSD37-ZWEU
  • 5x Sensative Strips (door/window sensors)
  • 1x POPP Z-Rain (rain measuring)

Dear all

with migrating to OH2.2 I decided to go with the old v1.x of the zwave binding and it worked pretty well. All devices were discovered and working fine (except POPP Z-Rain).

Today, I tried to migrate to the newer version of this binding but I don’t get my devices discovered. What I did is:

  • uninstalled v1.x binding via PaperUI
  • searched in file system for any zwave related files and deleted them
  • installed new v2 binding via PaperUI
  • checked zwave.cfg
  • checked the config parameter in PaperUI (looks good to me)
# The Z-Wave controller port. Valid values are e.g. COM1 for Windows and /dev/ttyS0 or
# /dev/ttyUSB0 for Linux
port=COM4

# Z-Wave nightly heal time. This is the hour (eg 2AM) at which the automatic nightly
# network heal will be performed.
healtime=2

All I get is this:

image
image.png532×796 48.5 KB 

15-Jan-2018 14:37:13.126 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Connecting to serial port 'COM4'
15-Jan-2018 14:37:13.143 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
15-Jan-2018 14:37:13.145 [INFO ] [al.protocol.commandclass.ZWaveSecurityCommandClass] - Update networkKey
15-Jan-2018 14:37:13.149 [INFO ] [ab.binding.zwave.internal.protocol.ZWaveController] - Starting ZWave controller
15-Jan-2018 14:37:13.149 [INFO ] [ab.binding.zwave.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 1: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 2: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 4: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 5: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 6: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 7: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 8: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 9: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
15-Jan-2018 14:37:16.546 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
15-Jan-2018 14:37:16.546 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - # Nodes = 8

There is no chance to link any items with any of the nodes, all I get is this:

image
image.png1289×759 57.7 KB

How can I get my devices discovered properly?

Thanks & regards
John

2

@chris What is the recommended process in such a situation?

  1. Full reset: hard reset of the Aeon stick and re-include all devices?
  2. Exclude all existing devices and re-include them?
  3. Being patient and hope that my unknown devices will become “known” somewhen in the next 100 years?
3

Meanwhile my log gets spammed with the following entries:

15-Jan-2018 20:04:45.501 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.502 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.502 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.503 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.503 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.504 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:04:45.504 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.647 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.647 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.648 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.649 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.650 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.651 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
15-Jan-2018 20:11:42.652 [WARN ] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
4

What are all these devices? Are they battery devices or mains devices? If they are battery devices, then you might need to wake them up.

5

Sensative strips and Z-Rain are battery devices.

I added a new device (Sensative Strip) and did the wake-up-procedure around 20x - no change, still “unknown device” :frowning:

What I do not understand is: switching back to the old v1.x binding and all my devices appear and work properly. Using the new v2 binding and all devices are “unknown devices” although I didn’t do any changes with the controller.

Is there a chance that the new binding takes over configuration/devices from the old binding?

Honestly, I have no clue what else I could try. Any ideas?

Thanks & best regards
John