Agreed. I was actually surprised how well four of these dimmers sync'd when using just the basic button controller to command setpoints. I assumed I'd need to do direct association to get that. The other factor in my case is that these are the primary lighting for the space so having that baked in association is of interest (I'm not using the Zen54 switched inputs). Thanks again.
UPDATE
Version [1.2.0] - 2024-09-14
- Added singleThreaded flag
- Update library and common code
- Added option to set level to 0 when turned off
- Fix for range expansion and sharing with Hub Mesh
- Fix setLevel to work with mobile app sending values as strings
1 Like
I have just installed a ZEN54 to control the speed of a duct booster fan. I started with the stock Hubitat driver but I prefer to use jtp10181's drivers.
I set the fan speed using the setLevel command in a Rule and both drivers do this. However the advanced driver does not appear to update the Current States on the driver page, you have to hit refresh to see the current value. Similarly the event list does not show what level has been set. The screenshot below shows the event list with two setLevel commands with values 76 & 51 using the stock driver followed the same two setLevel commands using the advanced driver. The advanced driver does not show the actual level set consequently I cannot see the history of what the level has been.
The values are when the device replied with the level and then the driver posts the event.
For some reason it seems when using my driver it is not getting the responses back.
Did you run the Configure command when you switched drivers?
After doing that turn on trace logging and then try to set the level again. Post a screenshot of the resulting logs.
Yes, I always hit configure on each driver change - I have done this test a few times before I posted here. Will repeat with Trace logging enabled and post again, although it might take me a a few hours to get to it.
Screenshots of logs below. Starting at the bottom, the first setLevel command was sent at 03:33:22.142 using the stock driver, followed by the second at 03:34:21.613. The advanced driver was loaded at 03:35:35.605 and the first setLevel command at 03:38:21.636, the second setLevel command at 03:40:21.638. The event log shows the same as before, just the command-setLevel event with no level event.
What is your hub firmware/platform version?
After running configure on my advanced driver, try cutting power to the ZEN54 for 30 seconds. I suspect maybe it is that hidden setting #13 and it takes a restart of the device to take effect.
I tried setting all my settings the same as yours and it still works fine for me. Same device firmware.
It also looks like the system driver might be issuing a refresh as soon as the supervision report comes back, where I am waiting for the device to finish its transition and report the new level on its own. The system driver is (incorrectly IMO) pre-emptively posting the level event before the device is done transitioning. So the device may never be reporting on its own but the system driver has a build in band-aid to that issue. This is another issue that a power cycle of the device may fix.
Hub is a C8
Platform version is 2.3.9.201
Z-Wave firmware is 7.18
Device firmware is 1.30
Driver version is 1.20
I set parameter 13 to 1, hit configure and when finished pulled the power for 30 seconds. No difference in the reporting, still needs a refresh for the hub to "see" the level.
Not sure what the problem is, I cannot reproduce. Works fine for me.
You could try putting all the settings on the advanced driver back to the indicated defaults. Sometimes a certain combo of settings will have unexpected results. I tried to reproduce using your settings but it continues to work fine for me. Both of mine are paired with S2 security, one is paired as LR.
How is it paired? Can you show screenshot of that device on the z-wave details page?
Device is paired as LR, see screenshot below. Reset all Preferences to defaults, except ramp rates which I put at 15 seconds. Hit configure and power cycled the device, still does not show the level in the event list.
I can try an exclude/factory reset/include sequence in a couple of days, is that worth a try?
Yeah that is probably the next thing to try. It should be sending a report on its own when the transition is done. I do not see it doing this on either driver but the system driver looks like it has a refresh built in so that gets you the updated level event you are seeing. It would be a pretty simple patch on my driver to add that as well but it should not be needed.
For sure do not skip the factory reset after excluding, that will ensure all settings are reset to the defaults, an exclude may not reset everything.
