I have number of Leviton DZ6HD dimers running with Vera Plus hub without any problems. As I was looking to expand my system, I purchased number of ZW6HD dimmers. Even though documentation states that this Dimmer is fully backward compatible, I found that ZW6HD does not work well in Vera’s All Lights on/off. Then I decided to move to Hubitat C-8 Pro, and observed the same behavior as with Vera, described in scenario below.
Observing ZW6HD in “All on/off” Vera or adding this dimmer to Hubitat’s Groups and Scenes App, scenario is as follows.
Use pedal to turn light on/off, status is properly reflected in either Hub (Vera/Hubitat).
Start with all lights off, use All lights ON/Off and Groups and Scenes, works well on both Hubs
Start with all lights off. Use pedal on ZW6HD to turn single light ON. Now use “All Lights On/Off”. The ZW6HD, that was operated by pedal, does not respond to All Lights. It just stays ON. Put that Dimmer back to off state manually, now it appears “in sync” and works with all lights on/off function. Same behavior on both hubs.
If in Hubitat’s Group and Scenes I disable “Enable on/off optimization?”, Dimmer works properly.
If I create automation with Room Lighting app, with single ZW6HD, it has problem as described above.
If I create same automation using Simple Automation Rules app, it offers “Enable on/off optimization (must be off for Scene and Group Activators)”, and once I disable that, automation works.
Is it a problem on my part, something I missed to configure? If bug, is it fixable (workaround to be implemented) in the driver, some automated app/procedure, or Hubitat or Leviton should do something?
Problem 2
Parameter 1 and 2 are fade on/off, respective. When I configure Fade ON to b=e instant and Fade Off to be gradual, Dimmer works well when operated by Pedal. But when Hubitat sends on/off, it is instant in both cases.
Basically, configuration works well for the physical dimmer action, but from Hubitat, it is defined only by Parameter 1. If configured with 0, it is instant on for both, on and off, if set with 2, it is fade for both on and off.
I had a problem with Google Home and my Leviton ZW6HD not staying in sync. Turn it on with the physical switch then tell Google Home to turn it off. GH would report the device being turned off but what I got was a NOP (no operation) instead. That was until I tried this.
It was a simple stand alone rule that allowed GH and my device to stay in sync.
What is the firmware version for this device? Here is a link that talk about buggy firmware for these. It would probably be helpful to read most of the linked thread below.
And as stated, they do have some bugs in the original firmware regarding state change reports. After updating mine and using my driver, I found all issues were resolved.
Be aware of this also, there is no way to tell if you have the bugged firmeware or the fixed one. Only way to know is to flash the current file and see if it fixes it. Both old and new report the SAME version back to the hub.
Yes, first thing I did was to install Universal Z-Wave Driver. I was trying to switch back and forth, same behavior
At the moment I'm just battling ZW6HD, learning Hubitat (and it's bugs :-), and slowly transferring some of the devices over. Once I get to DZ6HD, I'll give it a go to the custom driver too.
I did try firmware update, and yes, it driver reports same version 1.01. I got firmware from this page: https://hubconnecteddecorasmart.leviton.com/hc/en-us/articles/7151993826075-Updating-Decora-Smart-Z-Wave-Using-Home-Assistant
Update took, literarily, 12 hours!!! I moved Hub to be next to the dimmer, so distance was not the issue. Is that normal, expected time to update?
At the end, nothing changed, including displayed version of the firmware. I just assumed that update was not successful.
To install firmware update I first installed Hubitat Package Manager, then installed Device Firmware Updater, then uploaded that driver from Leviton site using Update Z-Wave Firmware.
Now, there is confusing part. "Update Z-Wave Firmware shows 2 Target Firmwares: 0 Version: 1.01, and 1 Version: 2.01. I assumed that target should be 0 - 1.01 and did update against that target.
So to summarize firmware update question: 1) Did I use good procedure? 2) is it normal that process take so many hours? If not, what is wrong?
One thing I didn't try yet is to do factory reset on the Dimmer. I'll give it a try ...
Thank you @croweflight, I tried to setup that using "Rule Machine", but I got stuck at the "Select Action to run", could not find "Track Dim" action. Is it may be "Adjust dimmer"?
The Device Firmware Updater tool has a checkered history overall (long story), but the native/stock version (i.e. not the one available in Hubitat Package Manager [HPM]) works very well these days with a couple undocumented caveats...
First, rebooting the hub in between each update attempt (successful or not) is key -- if you don't reboot, that's when it takes forever (12+ hours) and will often fail anyway.
But otherwise, the update should just take several minutes and the progress should be steady. I've updated quite a few devices lately (LR and mesh, ZIP and JS) and they've all gone well.
My own technique is to save my own copy of the update file (for my own records), then install the native Updater app, load the file, and do the update. Once complete, I purge the file out of the app, then remove the app. I only ever install the app when I need to do an update.
If I need to update more stuff, I reboot the hub, and then repeat above steps. Rinse, cycle, repeat all those steps until all devices done.
HA!!! Yes that is the one I was using, why did I thought that I installed it by package manager? No idea. Just confirmed, it is not coming from any package, it is native one ... I'll try reboot/recycle/open window/close window ... good old days
There is a version of it available on HPM too... That one looks very much the same overall (and maybe exactly the same - I don't recall for sure) -- that's part of the checkered history I mentioned.
