SOLVED: z-Wave Binding: Leviton Dimmer DZ6HD - Unknown device

ashgupta · March 24, 2017, 6:12am

Please Help here in fixing the zWave Binding.

I am trying to add Leviton DZ6HD Dimmer. This device exists in the device database. Reference id is: 556 (http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/556#)

The device also gets initialized and OpenHab gets the manufacturer ID. It also creates the node.xml file. Attached below is the node.xml file

node26.xml (6.4 KB)

Output from HabMin shows:

Log file shows:
Node26-Log.xml (390.5 KB)

Sorry I had to change the Log file extension to XML otherwise it was not allowing me to upload.

I notice the following error in the Log File:
NODE 26: Device discovery could not resolve to a thingType! 001D:3201:0001::1.13

Also it seems that OH2 is not even getting all of the Leviton devices from the database. When I perform:
grep -i “node 26” zWave.log | grep -i leviton
I get the following:

2017-03-23 22:47:56.220 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzs15_00_000
2017-03-23 22:47:56.225 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_rzp03_00_000
2017-03-23 22:47:56.239 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpd3_00_000
2017-03-23 22:47:56.240 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpa1_00_000
2017-03-23 22:47:56.242 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrp03_00_000
2017-03-23 22:47:56.242 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzmx11lz_00_000
2017-03-23 22:47:56.246 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dz15s_00_000
2017-03-23 22:47:56.246 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrmx11lz_00_000
2017-03-23 22:47:56.261 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpa1_00_000
2017-03-23 22:47:56.264 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpd3_00_000
2017-03-23 22:47:56.268 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrcs2mrx_00_000
2017-03-23 22:47:56.282 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000
2017-03-23 22:47:56.282 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000
2017-03-23 23:00:35.640 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs15_00_000
2017-03-23 23:00:35.640 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs15_00_000
2017-03-23 23:00:36.236 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vri06_00_000
2017-03-23 23:00:36.236 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vri06_00_000
2017-03-23 23:00:36.427 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vre06_00_000
2017-03-23 23:00:36.429 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs05_00_000
2017-03-23 23:00:36.433 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzr15_00_000
2017-03-23 23:00:36.436 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzs15_00_000
2017-03-23 23:00:36.514 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_rzp03_00_000
2017-03-23 23:00:36.607 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpd3_00_000
2017-03-23 23:00:36.609 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpa1_00_000
2017-03-23 23:00:36.612 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrp03_00_000
2017-03-23 23:00:36.613 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzmx11lz_00_000
2017-03-23 23:00:36.784 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dz15s_00_000
2017-03-23 23:00:36.785 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrmx11lz_00_000
2017-03-23 23:00:36.811 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpa1_00_000
2017-03-23 23:00:36.816 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpd3_00_000
2017-03-23 23:00:37.003 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrcs2mrx_00_000
2017-03-23 23:00:37.009 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000
2017-03-23 23:00:37.009 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000
2017-03-23 23:01:39.206 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs15_00_000
2017-03-23 23:01:39.206 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs15_00_000
2017-03-23 23:01:39.221 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vri06_00_000
2017-03-23 23:01:39.222 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vri06_00_000
2017-03-23 23:01:39.246 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vre06_00_000
2017-03-23 23:01:39.250 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrs05_00_000
2017-03-23 23:01:39.261 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzr15_00_000
2017-03-23 23:01:39.280 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzs15_00_000
2017-03-23 23:01:39.326 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_rzp03_00_000
2017-03-23 23:01:39.337 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpd3_00_000
2017-03-23 23:01:39.344 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpa1_00_000
2017-03-23 23:01:39.352 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrp03_00_000
2017-03-23 23:01:39.356 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzmx11lz_00_000
2017-03-23 23:01:39.371 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dz15s_00_000
2017-03-23 23:01:39.372 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrmx11lz_00_000
2017-03-23 23:01:39.387 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_dzpa1_00_000
2017-03-23 23:01:39.454 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrpd3_00_000
2017-03-23 23:01:39.477 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrcs2mrx_00_000
2017-03-23 23:01:39.492 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000
2017-03-23 23:01:39.492 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 26: Checking zwave:leviton_vrf01_00_000

There is no reference to leviton_dz6hd_00_000 which would be the correct device.

How can I fix this ?

chris · March 24, 2017, 7:17am

You don’t mention what version of OH you are using, but please ensure you are using the latest snapshot version.

ashgupta · March 24, 2017, 4:58pm

This was resolved by downloading the latest SNAPSHOT release. I had the SNAPSHOT release from last month.

Thank you.

adlich · March 27, 2017, 6:00am

Hi,

I too had the same issue with this device.

I’m using OpenHAB 2.0, re-installed the the z-wave binding via Paper UI, still seem to get the release from January.

Tried cloning repo and maven clean install onto add-ons, but it seems I’d have to track down unresolved dependencies based on the output of bundle:diag.

Being a newbie on OpenHAB and a dinosaur as far as modern Java development goes, I reasoned it was time to step back and ask: what’s the recommended way of updating the z-wave binding? Is there a way of keeping the device database up-to-date w/o updating binary?

Thanks in advance!

ashgupta · March 28, 2017, 6:01am

I moved the old /opt/openhab2 to /opt/openhab2-old
Installed completely new latest SNAPSHOT install to: /opt/openhab2
Got zWave working
Then copied selected files from /opt/openhab2-old to /opt/openhab (eg: item, rules, sitemap etc)

adlich · March 30, 2017, 5:20am

Thank you!

I had just started with OpenHAB and downloaded the stable distro – didn’t know about the builds on cloudbee.

This works and got my dimmer to work!

For the benefit of other/future readers: besides installing the full snapshot, I have thus far found that the 2.1.0 snapshot of the binding is compatible with the current stable bits, and was able to install it in isolation with bundle:install https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastSuccessfulBuild/artifact/bindings/org.openhab.binding.zwave/target/org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar.

Thanks again!