Hubitat C7 running 220.127.116.11
webCoRE community app
Zooz Zen77 dimmer HW 1.0 running FW 10.30 (5 devices behaving the same)
Ramp rates operate as expected from the paddle and Hubitat device page (Set Level, On, Off). I converted to the community Advanced driver to ensure access to parameters (9, 27, 28, 29) and easily confirm their values.
Previously, I was using the native Zen77 driver, FW 10.10, and only setting parameter 9 to control all ramp rates. The update to FW 10.30 and change in drivers was an effort to unlock these ramp rates.
However, sending a Set Level command from a webCoRE piston results in an abrupt (<1 second) change. Behavior remains the same no matter what ramp rate is set on the device. Does Set Level behave differently when it is sent from the device page versus webCoRE? Do I need to include a transition time with each Set Level command?
Below is a green snapshot of an example piston, for reference. I happen to use device variables, but have also tried using the device name directly during troubleshooting. Any guidance is greatly appreciated.
I also noticed my kitchen and bedroom lights no longer follow the transition time in the device settings. Kitchen lights are GE dimmers and bedroom is a Sengled dimmable bulb. If I change the level in the device settings, it transitions over 5 seconds. If I trigger piston (button press, etc), it changes in less than a second. I use the set level command in my webCoRE pistons.
Hm, I do see the duration as an optional setting in webCoRE now. That must be new. Since it's optional, if it's not set explicitly in the piston wouldn't/shouldn't it default to whatever is set in the device settings?
Agreed. Duration does work. Thankfully @Equis recalls a similar change in behavior, so I feel slightly less crazy.
Device page Set Level (time blank) respects ramp parameters.
webCoRE Set Level (time blank) now seems to force a duration value of zero.
webCoRE seems to have behaved like the device page in the past.
Going back to tweak each piston with durations is not such a huge deal. I do rather like the idea of a ramp rate, though. Hopefully having it recorded here will save someone else some wasted time chasing drivers, parameters, or firmware.
@Hatallica let me know if this seems to be a problem with my driver. Grab some debug logs and post. The driver should use the device defaults if setLevel is called with no duration, which I think is what you want.
Thanks. I don't have any reason to suspect the driver, since behavior is as you describe from the device page. Also, I initially observed the behavior using the native driver and various other devices.
There were some recent changes to WebCoRE to allow duration of zero (Set Level - Duration of 0 - #22 by jtp10181) that seems to have broken the default and I had to go back and add a level command to all of my Set Level commands. That said, having the option to use zero is great for a few of my scenarios.