Unknown device Leviton Decora DZS15-1LZ

Add-ons Bindings
1

Having trouble getting OH to fully recognize the Leviton Decora DZS15-1LZ switch

Installed OpenHABian Stable 2.0

I included the switch to the Z-Stick using the stick’s blue button and the switch’s inclusion mode (press top rocker for 7 seconds, light blinks amber, press again, light blinks green and Z-stick blinks blue.)

OH sees the Z-Stick. When I click the + icon to add new Thing and choose Z-Wave the Thing is added to Inbox.

Click on the Thing in the Inbox and I get the following:

Z-Wave Node 2 (001D:3401:0001:1.15)
Unknown Device
zwave:device:f853423d:node2
visibility_off delete

When I click to Add Thing. It gets added. When I click the Thing I get this:

This device has not been fully discovered by the binding. There are a few possible reasons for this -:
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.

Debug logging while trying to add Thingy: (filtered out all the other devices).

2017-03-22 21:00:29.455 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
2017-03-22 21:00:29.461 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2017-03-22 21:00:29.463 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Starting ZWave inclusion scan for zwave:serial_zstick:f853423d
2017-03-22 21:00:29.465 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery completed
2017-03-22 21:00:29.468 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:act_45602_00_000
... // filtered out non Leviton devices
2017-03-22 21:00:30.151 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_dzmx11lz_00_000
2017-03-22 21:00:30.153 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_dzpa1_00_000
2017-03-22 21:00:30.156 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_dzpd3_00_000
2017-03-22 21:00:30.158 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_dzr15_00_000
2017-03-22 21:00:30.160 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_dzs15_00_000
2017-03-22 21:00:30.163 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_rzp03_00_000
2017-03-22 21:00:30.165 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrcs2mrx_00_000
2017-03-22 21:00:30.167 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrf01_00_000
2017-03-22 21:00:30.169 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrf01_00_000
2017-03-22 21:00:30.171 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vri06_00_000
2017-03-22 21:00:30.173 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vri06_00_000
2017-03-22 21:00:30.175 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrmx11lz_00_000
2017-03-22 21:00:30.177 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrp03_00_000
2017-03-22 21:00:30.179 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrpa1_00_000
2017-03-22 21:00:30.181 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrpd3_00_000
2017-03-22 21:00:30.183 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrs05_00_000
2017-03-22 21:00:30.185 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrs15_00_000
2017-03-22 21:00:30.187 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:leviton_vrs15_00_000
... // filtered out non Leviton devices
2017-03-22 21:00:30.530 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Checking zwave:zyxel_st812_00_000
2017-03-22 21:00:30.535 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 001D:3401:0001::1.15
2017-03-22 21:00:30.543 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:f853423d:node2' to inbox.
2017-03-22 21:00:30.544 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2017-03-22 21:00:30.545 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.
2017-03-22 21:00:30.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:00:30.547 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:00:30.558 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70 
2017-03-22 21:00:30.560 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70 
2017-03-22 21:00:30.564 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:00:35.567 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2017-03-22 21:00:35.574 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:00:35.577 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:00:35.582 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70 
2017-03-22 21:00:35.586 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70 
2017-03-22 21:00:35.590 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:00:40.593 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2017-03-22 21:00:40.609 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:00:40.611 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:00:40.615 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70 
2017-03-22 21:00:40.619 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70 
2017-03-22 21:00:40.622 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:00:45.624 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2017-03-22 21:00:45.626 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:00:45.633 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:00:45.637 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70 
2017-03-22 21:00:45.640 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70 
2017-03-22 21:00:45.642 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:00:50.646 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=C1 01 
2017-03-22 21:00:59.463 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
2017-03-22 21:00:59.465 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2017-03-22 21:00:59.467 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:00:59.467 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:00:59.469 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end inclusion
2017-03-22 21:00:59.472 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4 
2017-03-22 21:00:59.475 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4 
2017-03-22 21:00:59.477 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:01:04.479 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2017-03-22 21:01:04.482 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:01:04.487 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:01:04.492 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:04.496 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:04.499 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:01:09.501 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2017-03-22 21:01:09.503 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:01:09.515 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:01:09.519 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:09.523 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:09.525 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:01:14.527 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2017-03-22 21:01:14.529 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-03-22 21:01:14.605 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-03-22 21:01:14.610 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:14.614 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4 
2017-03-22 21:01:14.617 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-03-22 21:01:19.621 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=05 01

The logs show it checking for DZS15 but this switch is the DZS15-1LZ.
Is it missing from the database?

For what it’s worth, I previously had Home Assistant (hassbian) on my PI and had no problems including and controlling the switch.
Now I have openHABian.

2

I’m also having the exact same issue.

Thanks

3

Yes - it looks like it’s not in the database. Please see the information here on how to add devices.

4

I’m still having issues however is this not the switch in the database?
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/523?layout=openhab2. I using a raspberry Pi and the z-stick gen5 this is the first device i’m trying to setup. The zave controller status states that it is online in paper ui and has a green check mark in habmin

thanks in advance for any assistance

5

What version of the binding are you using - the snapshot or release version? This device might not be in the OH2 release.

6

I have downloaded org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar and placed it in /usr/share/openhab2/addons. I then restarted openhab. I don’t think karaf is running on my pi, by default with my install of openhab, it’s installed on raspbain
Thanks

7

I don’t know if I did the database import correctly

8

I don’t think you can not run Karaf so it must be there.

In any case there has been a problem with the build system and the last binding update was a week ago now - I’ve just started another build, so let’s see if that is successful - it will probably take a day or two for it to feed through to the package you are using.

9

Should I update openHAB or place the jar file in the appropriate directory?

10

Well it looks like the builds are still failing, so until this is finally solved, unfortunately there’s no solution.

11

How do I find out if a build is successful

12

You can check the status on Cloudbees.

https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/

13

Typically how often do they not have a successful build?

14

Not very often - it normally works fine, but something is clearly broken in the system. It’s probably not specifically related to OH - it’s quite possibly in the CI system itself.

15

Is there someone to notify if ci is broken?

16

We are already aware that it is broken ;). The maintainers get notified whenever builds fail - it’s all part of the CI system.

17

Is there any other options in try to get my device to work with the ci not creating a successful build

18

Now that we have a successful build how do i get tn installed on my PI, Thanks

19

If you are running the snapshot environment, then just install the zwave binding. If it’s already installed, then uninstall it first, then install it again.

20

How do I determine if I’m running a snapshot environment