Bug in Button Device or Zooz Zen34 driver?

🛎️ Get Help
1

I have a Zooz Zen34 700 series switch controlling an outlet via Rule machine. It's to shut off a noisy heater fan in our TV room for 65 minutes when button 2 is pressed, turn it back on if button 1 is pressed. Intermittently, once a week or so (~1 out of 20 times) the actions do not trigger. The outlet controlled by the switch is a Leviton Decora Smart Tamper-Resistant Duplex Outlet but per the debug information below, I don't believe that's relevant to the problem. Rule is below.

Has anyone seen an issue like this? In my analysis correct that this is a bug in Button Device or the Zooz Zen34 driver?

I initially thought the problem might have been people pushing the switch for too long, or pushing it twice, so I updated the rule to also trigger for long presses and double presses:

image
image956×2078 183 KB

Of course (until this time) it always worked fine whenever debug logging was turned on for the devices in the rule.

Here is a properly behaving sequence from the logs (time goes from bottom to top):

dev:1402021-01-23 11:13:34.838 am infoStove Fan Outlet is on [digital]
dev:1402021-01-23 11:13:34.833 am infoBasicReport value: 255
dev:1402021-01-23 11:13:34.830 am debugparse description: zw device: 14, command: 2003, payload: FF FF 00 , isMulticast: false
dev:1402021-01-23 11:13:34.769 am infoStove Fan Outlet was turned on [physical]
dev:1402021-01-23 11:13:34.767 am infoSwitchBinaryReport value: 255
dev:1402021-01-23 11:13:34.764 am debugparse description: zw device: 14, command: 2503, payload: FF FF 00 , isMulticast: false //Outlet turned on
app:1852021-01-23 11:13:34.372 am infoCHAS: Cancel pause button press
dev:2042021-01-23 11:13:34.113 am debugSupervision Get - SessionID: 40, CC: 91, Command: 3
dev:2042021-01-23 11:13:34.107 am debugparse:zw device: 15, command: 6C01, payload: 28 05 5B 03 90 80 01 , isMulticast: false //Button 1 (turn outlet back on)
dev:1402021-01-23 11:13:29.729 am infoStove Fan Outlet is off [digital]
dev:1402021-01-23 11:13:29.723 am infoBasicReport value: 0
dev:1402021-01-23 11:13:29.711 am debugparse description: zw device: 14, command: 2003, payload: 00 00 00 , isMulticast: false
dev:1402021-01-23 11:13:29.660 am infoStove Fan Outlet was turned off [physical]
dev:1402021-01-23 11:13:29.654 am infoSwitchBinaryReport value: 0 //Turn off outlet
dev:1402021-01-23 11:13:29.641 am debugparse description: zw device: 14, command: 2503, payload: 00 00 00 , isMulticast: false //Outlet turned off
app:1852021-01-23 11:13:29.197 am infoCHAS: Pause fan button press
dev:2042021-01-23 11:13:28.842 am debugSupervision Get - SessionID: 25, CC: 91, Command: 3
dev:2042021-01-23 11:13:28.816 am debugparse:zw device: 15, command: 6C01, payload: 19 05 5B 03 8F 80 02 , isMulticast: false //Button 2 (pause fan) pressed

Finally today it failed with debug logging turned on for the switch and outlet...

dev:2042021-01-23 11:11:55.074 am debugparse:zw device: 15, command: 7006, payload: 03 01 00 , isMulticast: false
dev:2042021-01-23 11:11:54.944 am debugparse:zw device: 15, command: 7006, payload: 02 01 01 , isMulticast: false
dev:2042021-01-23 11:11:54.573 am debugparse:zw device: 15, command: 7006, payload: 01 01 01 , isMulticast: false
dev:2042021-01-23 11:11:53.028 am infoStove Fan Pause Switch battery is 100%
dev:2042021-01-23 11:11:53.002 am debugparse:zw device: 15, command: 8003, payload: 64 , isMulticast: false
dev:2042021-01-23 11:11:52.520 am debugStove Fan Pause Switch Device wakeup notification
dev:2042021-01-23 11:11:52.460 am debugparse:zw device: 15, command: 8407, payload: , isMulticast: false
dev:2042021-01-23 11:01:58.001 am debugSupervision Get - SessionID: 30, CC: 91, Command: 3
dev:2042021-01-23 11:01:57.996 am debugparse:zw device: 15, command: 6C01, payload: 1E 05 5B 03 8E 81 02 , isMulticast: false //Nothing happened, so I held button 2 (pause fan). Either of these should have triggered the actions.
dev:2042021-01-23 11:01:57.701 am debugSupervision Get - SessionID: 29, CC: 91, Command: 3
dev:2042021-01-23 11:01:57.635 am debugparse:zw device: 15, command: 6C01, payload: 1D 05 5B 03 8D 82 02 , isMulticast: false //Button 2 (pause fan) pressed
dev:2042021-01-23 11:01:36.717 am warndescription logging is: true
dev:2042021-01-23 11:01:36.716 am warndebug logging is: true
dev:2042021-01-23 11:01:36.714 am infoupdated...
dev:1402021-01-23 11:01:26.004 am warndescription logging is: true
dev:1402021-01-23 11:01:26.002 am warndebug logging is: true

My hub is almost always very idle, I don't have many rules and the rules I have are triggered from infrequent events. There was nothing else going on at the time of this failure.

Also, this isn't the "battery powered buttons can be slow to wake up" issue that appears other places in the forum. The hub clearly got the command from the switch per the logs, it just did not act on it.

2

What version of the hub are you running?

3

A C-7 hub running the latest firmware (2.2.4.158)

4

2.2.5.119 is latest...

5

There was a driver fix in 2.2.5, not sure if it will fix this specific problem, but I'd recommend you try it.

6

Did you mean Leviton smart outlet vs lutron or do you have one of those big lamp dimmers? (Just curious)

7

Cool! The new firmware mist have just come out in the last day or two (at least when I checked for updates Sunday I was told I was running the latest, maybe Hubitat does a gradual rollout?).

I'll update and see if that changes anything. Unfortunately the problem is intermittent so it might take week or 2 for me to know if the problem is addressed.

8

Cool! I'll update and see if that changes anything. Unfortunately the problem is intermittent so it might take week or 2 for me to know if the problem is addressed.

9

The exact outlet I'm controlling (no dimmers involved, it's turning a fan on and off) is a:

Leviton Model #ZW15R-1BW Z-Wave Enabled 15 Amp Scene Capable Receptacle with LED Locator, DZR15-1RZ.

But per the logs, I'm 99% sure the outlet has nothing to do with the problem, the debug logs show the low level button press command coming in from the switch and the applicable rule code never gets executed.

10

Right.... I was confused cause in your original post you said lutron is all...

11

Opps, I didn't notice the mistake in my post. Thanks for pointing it out, I've edited my post to correct it.

1 Like
12

Me too.

I just installed a new one of these and although I can see the button presses in the log, rules that depends on them don't execute.

This thread doesn't say if the issue was ever resolved.