I posted this on Hubitat forum then I remember that Inovelli have it own forum as well so I am going to post the similar question on here.
I have Red Dimmer using the Inovelli User driver which I grabbed from guthub and installed in Hubitat.
The configuration settings are blank so I filled in some of it because there are some settings which I wanted to be different than the default one like ramp rate, dim level etc but I left all other blank and saved the parameter.
I notice the switch is not functioning exactly what I expected. Should I be filling in all the settings even with default setting to have no blank configuration setting and save it?
Like the ramp rate, default at 3 so I set it to 0 because I wanted to be instant on and off at both the physical switch and the digital switch. The ramp rate on Physical is instant off and on but the ramp rate on digital switch (from my phone dashboard) still act like at the default 3 even I set it to 0 in the configuration setting.
Can anyone help me with this or offer a feedback on it?
I have noticed that to make changes, I have to click Save Preferences, then scroll down and hit Save Preferences a second time before Hubitat reports back that the switch’s parameters are configured as I had expected.
I personally fill in all of the options, even if its just setting it to the default value.
Reason being, you don’t know the state the switch is in and what the value currently is on the switch. At least if you set it in the driver it will force the setting of that value and you visibly can see what it is set to now.
@TechBill - like @harjms I only fill in the parameters I want to be changed.
What I personally observed with Hubitat (using the custom Inovelli drivers for LZN31-SN) is that I’ll change a parameter, hit save, Hubitat page saves my settings in its database, the page reloads with the values I saved, but it reports that the switch parameters values are different. Then I click Save Preferences again, and when the page reloads, it reports the parameters values are correct.
There is a workaround fix for it by making some edit in the driver. I don’t know if they are going update the driver or what their plans are with the fix.
You can message support and ask them if they will share the fix with you but you will need to know how to edit the driver to apply the fix to it.