It did take me a little while to get a feel for dimmer speed vs. ramp speed, but I feel I now understand the difference. Yes. The ultimate goal is to have them come on virtually instantly (i.e. Param 51 On and params 1, 3 and 4 set to 0), but to have them fade off over 1 second.
I’ve done a few experiments with rules, params 1-4, 51 and enabling/disabling the physical switch. If I disable the physical button then a rule for 1 pushed to go to 100% at 0 seconds turns on the lights in about 1second.* I also created a rule for 1 held to dim to 0% in 1 second and that took about 1 1/2 seconds. So that worked in the sense that the on and off times were different, but the 1 pushed rule to “dim” (turn on) to 100% in 0 seconds took about 1 second. I found that turning Param 51 on or off did not effect that. (Which I’m assuming is because the physical switch was turned off).
I then tried to go another route. I first deleted the 1 pushed rule. After that I turned the physical switch back on (i.e. I set Disable Physical Switch to No) and then created a rule to delay a 1 Held by 1 second, but that rule was ignored. Setting Param 51 made no difference to that rule doing anything. i.e. if I had Param 51 on, on/off was virtually instantaneous and with 51 off it added the 700 ms back in. but in either case the on/off times where identical. So I have no idea when a rule delaying 1 held by 1 second would ever actually do that.
Here is my 1 Held 1 second delay rule:
So while there seems to be rules to control the dim rate I can’t figure out how to control the ramp rate. I had tried several experiments with setConfigParameter for Parm 4 (ramp rate from the switch), but none of them seemed to do anything (that is setting the params to 0 and setConfigParameter to 1 or vice versa of setting the params to 1 and trying to use setConfigParameter to set them to 0).
In going through some other threads I saw this in post 170 of Firmware v1.52 (Beta):
- The current version of the HA zwavejs integration does not support the changing of config parameters (I believe the feature is coming soon though). Currently, the only way to change config parameters is to use websockets (which I am not too familiar with) or with something like zwavejs2mqtt
- The delay is not adjustable via the config button at this time.
- A config file with the latest beta features is currently not available. I think there are a few people working on it though.
So that may very well answer why the setConfigParameter and setLevel aren’t working when I put them into Hubitat Rules.
Final, BTW, does Param 50 change the 700 ms rate? I’ve been afraid to set it as there is no way to clear it once it is set. Is the default for Param 50 700 ms?
Stuart
*I know my times are not exact due to my reaction time of starting and stopping the stopwatch when I see them turn on or off, but I get pretty consistent results over multiple tests, so the relative times are pretty accurate, i.e. how much of an extra delay I get and what is the initial delay in turning them on or off.