Leviton Zwave Plus Switches Not Reporting back to the C7

@bobbyD @mike.maxwell

I have migrated my Leviton Zwave Plus switches from a C4 to a C7. On the C4 they worked flawlessly. On the C7, they will not report their status back to the C7 when physically turning on/off the switch. Has anyone else run into this issue?

I have done a factory reset on the switches with no luck. I am using the Generic Zwave Smart Switch driver.

Here are some lines from the debug logs from one of the switches:
[dev:2537] 2020-08-04 10:54:15.418 pm [debug] skip: Hail()

[dev:2537] 2020-08-04 10:54:15.414 pm [debug] parse description: zw device: 34, command: 8201, payload: , isMulticast: false

[dev:2537] 2020-08-04 10:53:47.009 pm [debug] skip: Hail()

[dev:2537] 2020-08-04 10:53:47.004 pm [debug] parse description: zw device: 34, command: 8201, payload: , isMulticast: false

Is that the driver that the switch selected when it joined?
Also, please post a screen shot of the data section of the driver details, thanks!

That is the driver they picked on the C4 and the C7. Here is your requested screenshot:

This might not be a C4 vs C7 issue. This could be a platform update and I didn't notice it in the past several weeks, since I generally don't pay attention to some of the minor automations.

This has already been fixed by @bcopeland in the driver. I expect it will be included in the next release.

@mike.maxwell My Yale lock is not reporting back either unless I manually refresh the device. I think there are other devices too. Some report back slower after the move. My Leviton dimmers work with the Leviton Dimmer driver, if that counts.

I see that you're referencing a driver that has a fix in it. Do you know if that driver exists in the wild yet?

Struggling to get my Leviton VRS15 switches to report back any physical changes.


It is in 2.2.4. However the fix is particular to the DZ15S. You might contact @bcopeland and ask him about a hail fix for your particular switch.

You will need to provide him the information from the Data section of your device. Looks like this:

  • deviceType: 13313
  • inClusters: 0x5E,0x85,0x59,0x86,0x72,0x70,0x5A,0x73,0x25,0x20,0x27,0x2C,0x2B,0x7A
  • zwNodeInfo: D3 9C 00 04 10 01 5E 85 5C 59 86 72 70 5A 73 25 20 27 2C 2B 7A EF 82 68 23
  • outClusters: 0x82
  • deviceId: 1
  • manufacturer: 29

I've reached out to Bryan. Fingers crossed he comes up with something.

Happy New Year!

1 Like