I have some buttons set up as Toggle Dimmer to control Jasco dimmers. I set the fade to 3 seconds. When I tap the button to turn then off they fade perfectly. However, when I turn them on, they snap on in a 0 sec count.
If I use the actual dimmer paddle, the lights fade in and out using the default fade time built into the dimmer (which I also can't seem to find in Hubitat).
How do I fix this?
What are you using to do this? Is it a Rule Machine rule? Simple Automation Rule? Something else? Do you have the option to tap to turn on and off and hold the button to fade? It is hard to figure out how to fix it without more information to work with.
I'm using the Button Controllers App.
I posted this elsewhere but received no help.
I have some buttons set up as Toggle Dimmer to control Jasco dimmers. I set the fade to 3 seconds. When I tap the button to turn then off they fade perfectly. However, when I turn them on, they snap on in a 0 sec count.
If I use the actual dimmer paddle, the lights fade in and out using the default fade time built into the dimmer (which I also can't seem to find in Hubitat).
How do I fix this?
Toggle sends a "Set Level" command if on or an "Off" command if off. "Set Level" offers a transition time; "Off" does not -- at least not natively. but your device may offer a preference for this option (e.g., a Z-Wave parameter; for Z-Wave devices in particular, the manual almost always says more).
That being said, most devices will also accept a "Set Level" to 0 as equivalent to off, and fade generally still works in this case. You can re-create your own logic in Button Controller instead of using the "built-in" Toggle action if you wanted to try this, something like:
IF (Light is On) THEN
Set Dimmer: 100, Fade 3
ELSE
Set Dimmer: 0, Fade 3
END-IF
Double posting is generally a bad idea (and against the community guidelines), but if you're hoping posting somewhere else draws more attention (unlikely on Discourse, this forum software that works quite differently from traditional 90's-00's forums you still find a lot of today), it would be good to at least link to your other post and state anything else that may be relevant. Nevertheless, I found your previous posts and merged them chronologically into this topic (the term Discourse uses for "threads") to make things simpler for everyone.
I though I saw someone with a toggle command with a fade in a rule before? Cannot check at the moment.
Either way first test would be to see if your devices works as expected, from the device page with the device off, use the set level command with your desired fade. Does that work as expected?
This will tell us where the issue is, device/driver or rule.
Yes, this option exists, but what I meant is that (per the underlying commands) it only works if it's doing a "Set Level"--it won't work on "Off." So, it only applies to the half of the toggle that turns the light on, not off.
Well, just the opposite is happening here. It fades out just fine but snaps on.
As for trying to execute a fade in the device, I don't see where that can be done. There is a duration parameter that doesn't seem to do anything but that's it.
What driver are you using for this devices, and what is their exact model number?
The "duration" parameter in the "Set Level" command should work (the fade time in seconds). Is this the one you're talking about? If it doesn't work there, it's not going to work with any app, either (whether Button Controller or something else). But unless there is a problem with the device itself, a different driver might be able to address this issue.
I'm using the generic zwave smart dimmer driver. The dimmers are good old GE zw3005 Smart Dimmers.
The "Smart" drivers are intended for use with Z-Wave Plus devices, but the model number you provided is a classic Z-Wave device. I would try Generic Z-Wave Dimmer and see if it makes any difference, or you might want to try searching here and seeing what driver other people have had luck with for that device.
That was the driver Hubitat picked out when I paired the devices.
I switched to the Generic Z Wave Dimmer driver and that indeed fixed the issue. Thanks for your help!
I'd like to correct one thing that was said about these not being zwave plus dimmers. They are indeed. They also call themselves "Smart Dimmers" which would certainly lead one to believe that the Smart Dimmer driver would be the correct one, especially if that is the driver for zwave plus.
This is certainly something to be looked at on the Hubitat side.
Thanks again for everyone's help.
Weird, maybe they re-used model numbers, but the only Z-Wave certification I could find for the model number said classic:
https://products.z-wavealliance.org/products/1197
"Smart" also doesn't necessarily mean "Plus" in a product name--that's just the term Hubitat happened to choose to distinguish the driver names.
Glad you found one that worked, in any case!
I wanted to bring up the Toggle/fade issue again as I'm working with another device that isn't working the way I think it should-ZEN54 0-10V dimmers. If I read bertabcd1234's post correctly, Hubitat does NOT send a fade command when it toggles off a dimmer? That seems very odd to me. The fade command should be sent for both on and off. Even better, one should be able to assign different times for on and off when the action is set to toggle.
See what commands are being sent to the device by the app from the "Events" tab on the device detail page for the dimmer. Look for commands specifically, not events (despite the name, the page shows both) -- so "command" under the "Type" column, and just those "Produced by" this app.
You'll definitely see a "setLevel" (or "command-setLevel") for the toggling on, as a Set Level command will turn on the device if off under standard behavior. The Set Level command supports transition times.
You'll likely see "off" (or, again, "command-off") for the turning off. This command, like the "on" command, does not support a transition time -- it's just a parameterless command. (Some devices/drivers may offer options, but there is nothing in the command, per the capability spec.)
Some devices may take "0" as a value for the "Set Level" level, and any that does anything with it at all will probably turn the device off. Some of these may also obey a transition time if provided with this device. But an app has no way to know if this will work this way at all or work this way specifically. I don't know what BC does specifically, but I'm fairly confident it's just going to be an "off" for this reason, as this is what most apps would do, and for this reason.
If your device does do this, you can just make it use the command by re-creating the same logic yourself like I suggested above. This kind of logic is all RM is doing its own code anyway, except here you can use "Set Level" to 0 instead off "off":
Download the Hubitat app
