Zwave device has stopped working reliably - Leviton DZ6HD

🛎️ Get Help Devices
1

I have a Leviton DZ6HD Z-wave dimmer switch which was my first Hubitat device, and which has worked without problems for a year or more, and has suddenly stopped responding to commands reliably -- possibly when I upgraded to 2.3.9.164 from 2.3.9.136 (I think?). My hub is a C-7.

When the problem started, the device was occasionally responding to commands from the hub but the status of the device on the hub was not updating. I excluded and re-included the device (under a new device, not with "replace"), including a factory reset of the device, but the problem continued.

At that time the Z-wave Details for that device read:

PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined

but the device status showed a checkmark. Here's the whole entry:

SCR-20240802-rjmd
SCR-20240802-rjmd2066×1072 164 KB

The Z-wave route map showed only the hubitat -- before re-pairing, it showed both the hubitat and the switch even though things were not working then.

I rebooted the Hubitat, and that corrected the map and added route details to the device in Z-wave Details:

PER: 2, RTT Avg: ms, LWR RSSI: 1dB
Neighbors: 1, Route Changes: 0

but it is still not always responding to commands from the hub. However, when it does act on commands from the hub, the device state updates as expected (maybe with a short delay).

When a command does not work, I see the debug log entries for the "On" command in the logs but nothing from the device itself:

dev:33 2024-08-02 08:06:33.935 PM debug on()
dev:33 2024-08-02 08:06:14.208 PM debug on()
dev:33 2024-08-02 08:06:10.195 PM debug on()

When it DOES work, I usually (but not always) see much more happening:

dev:33 2024-08-02 08:10:02.655 PM debug parse description: zw device: 0B, command: 2603, payload: 50 50 00 , isMulticast: false
dev:33 2024-08-02 08:10:00.079 PM info Kitchen Lights 2 was turned on [physical]
dev:33 2024-08-02 08:10:00.062 PM debug parse description: zw device: 0B, command: 2603, payload: 50 50 01 , isMulticast: false
dev:33 2024-08-02 08:09:59.980 PM debug parse description: zw device: 0B, command: 8201, payload: , isMulticast: false
dev:33 2024-08-02 08:09:59.606 PM debug on()

When I did a Z-wave Repair, it returns:

Stage: Idle
Finished Z-Wave Network Repair
Failed Nodes: 0B

(where 0B is my switch).

I've also done a hard power cycle of the switch from the breaker.

Unfortunately for troubleshooting purposes, this is my only Z-wave device -- I decided to go all Zigbee after this first one so I can't tell if it is specific to this one or to any Z-wave devices.

Any idea what’s going on here or what else I can do to troubleshoot? Thanks!

2

One more data point: Sometimes things just take a long time (in this case, 29 seconds between the setLevel command and any other logs from the device).

dev:33 2024-08-02 08:31:40.447 PM info Kitchen Lights 2 was set to 99% [physical]
dev:33 2024-08-02 08:31:40.442 PM debug parse description: zw device: 0B, command: 2603, payload: 63 63 01 , isMulticast: false
dev:33 2024-08-02 08:31:40.394 PM debug parse description: zw device: 0B, command: 8201, payload: , isMulticast: false
dev:33 2024-08-02 08:31:40.361 PM debug parse description: zw device: 0B, command: 2603, payload: 43 43 00 , isMulticast: false
dev:33 2024-08-02 08:31:11.172 PM debug setLevel(99, 1)
3

This was a known issue on older firmware. What firmware version is your dimmer running?

1 Like
4

Heck of a question. How would I find out? :smile:

(It's not in either the device state or the device's Data table.)

5

alright, I found the instructions for the Basic Z-Wave Tool and it's returned

infoVersion Report - FirmwareVersion: 1.2, ProtocolVersion: 4.33, HardwareVersion: 255

I hope the tool is not rounding "1.20" to "1.2" but if it isn't that sounds pretty old -- I'll look into upgrading it.

(I also found a bunch of details in this thread... I'll report back how it goes!)

6

Quick update: I never did get around to upgrading the firmware on the device. (I still suspect "1.2" is "1.20".) But after a couple of days, the device started working reliably again. Maybe there was some interference source that eventually stopped? No idea, but it's solid as a rock again now.

1 Like
7

Mine was also on 1.2 when I purchased it but I since upgraded it to 1.22.

Screenshot (104)
Screenshot (104)1346×551 24.4 KB

Mine would randomly drop off the network and effectively "factory reset" itself. There were many times when I convinced myself it was fine because it would go sometimes 6-8 months without a glitch, but it's a bug in the firmware and eventually it happened again. There was a post somewhere on a Home Assistant forum where I found the information and the firmware files. I updated the firmware to 1.22 around a year and a half ago and haven't ever had the device flake out ever again. Actually just go here:

8

Ah, thanks! I'd heard that an old old firmware (1.12 or something?) was particularly flaky so I'd undervalued upgrading from 1.2(0), but it sounds like it might be worth figuring out anyhow!

9

Leviton update instructions here:

[GUIDE] How to update Leviton z-wave firmware - :bellhop_bell: Get Help / Devices - Hubitat

1 Like