I believe that you are correct, But I think its a calculated based over the range of the min to max settings.
Trying to use the 6 pushed/held and 8 pushed/held to raise and lower the dimming on some smart bulbs. But the commands donât seem to be sent from the dimmer (LZW31-SN running 1.44 firmware) until I release the button. Iâve held it for 30 seconds and the dimming never starts until I release the button. And of course when I release, itâs just as if Iâd turned it on or off (all the way on or all the way off).
Iâm using Button Controller 3.0 in Hubitat and using the âstart raisingâ and âstop changingâ attributes of âset dimmersâ mapped to buttons 6 and 8 as described above to try to get this to work (6 pushed, start raising, 8 pushed, stop changing, etc.) What am I missing?
Do you have the latest driver installed? Also, are the events showing up in the event list? It sounds like you have it setup correctly, but maybe post a screenshot of your button controller setup.
Edit: actually looking at what you have I believe you have 6 & 8 backwards ( I think I also have them mixed up in the main post ). Notice my Rule Machine config below:
Edit: I fixed the main post.
Ah, yep. That was the problem. I switched them and it works as expected now. Thanks!
Has there been a change in the way the Disable Local Control is presented in the Hubitat driver?
Using a Red Series dimmer here that previously worked well with CoCoHue and Hue colour bulb. I did a driver update to a June version and only had time now to troubleshoot odd behaviour.
Now I see the disable local/remote control switches are gone, only the drop down option remains and thereâs some sort of âsmart bulbâ option that I canât find documented.
I think my previous setting of disabling the local relay was reset until I did the eight clicks of the configuration button. It still reverts if I configure from the Hubitat device page.
I donât believe that it has changed in some time. It has been a drop down for as long as I remember. There is a child device option that is a true/false setting.
With the latest driver if you set local protection via the Hubitat interface or via the switch it doesnât matter. Either way will work.
Is there a way to set up different ramp speeds for on vs off from the physical switch?
I like having on set to 0 - nice and quick, but would like off to be set to 1 or 2 - to give a nice little fade as youâre exiting the room.
Any quick and dirty ways to edit the DTH to make this happen?
IDEA: simply set the ramp speed for the zwave parameter (I think thatâs parameter3) to 1, and then set the physical ramp speed parameter (I think thatâs parameter4) to 0, and then add the appropriate code to use parameter3âs setting when issuing an off command (instead of parameter4âs setting) when using the physical paddle. I poked around in the code for a but, but it wasnât obvious on how to accomplish that.
Suggestions welcome.
Cross-posted
At least in Hubitat, when I go into the device I see the parameterâs title, e.g. âDimming Speedâ, but not itâs #, (for Dimming Speed that would be #1). When referring to the parameters to set, such as for Associations, the instructions inevitably refer to the parameters by their number without also giving their name. Thus the instructions for Associations are to set parameters 2 and 4. But when I go into the deviceâs settings, since there are no numbers, I had to assume they were in order and then count them out. For 2 and 4 it wasnât hard, but harder than need be. Plus, without the name of the parameter in the instructions and no number at the device itself, one cannot be a 100% sure they adjusted the right setting. There is a situation where we are to adjust parameter 12 and for 3 ways, maybe 21 and 22. Counting those out can be a pain and adds needless uncertainty. So, please add the heading names to go along with the parameter numbers in your instructions and/or add the parameter number to the parameter heading inside the device where we actually set the parameter.
Thank you,
Stuart
That seems reasonable and maybe Inovelli (@EricM_Inovelli) might consider adding parameter numbers to the parameter names displayed on the device settings page? Maybe something like this:
parameter.parameter1name="Dimming Speed (parameter 1)"
Until Inovelli updates the descriptions in the driver files, here is a cheat-sheet you can use for the Inovelli Red Series LZW31-SN file. (parameter numbers will vary with other models)
parameter.parameter1name="Dimming Speed"
parameter.parameter2name="Dimming Speed (From Switch)"
parameter.parameter3name="Ramp Rate"
parameter.parameter4name="Ramp Rate (From Switch)"
parameter.parameter5name="Minimum Level"
parameter.parameter6name="Maximum Level"
parameter.parameter7name="Invert Switch"
parameter.parameter8name="Auto Off Timer"
parameter.parameter9name="Default Level (Local)"
parameter.parameter10name="Default Level (Z-Wave)"
parameter.parameter11name="State After Power Restored"
parameter.parameter12name="Association Behavior"
parameter.parameter13name="LED Strip Color"
parameter.parameter14name="LED Strip Intensity"
parameter.parameter15name="LED Strip Intensity (When OFF)"
parameter.parameter16name="LED Strip Effect"
parameter.parameter17name="LED Strip Timeout"
parameter.parameter18name="Active Power Reports"
parameter.parameter19name="Periodic Power & Energy Reports"
parameter.parameter20name="Energy Reports"
parameter.parameter21name="AC Power Type"
parameter.parameter22name="Switch Type"
parameter.parameter50name="Button Press Delay"
parameter.parameter51name="Disable Physical On/Off Delay"
parameter.parameter52name="Smart Bulb Mode"
THANKS for taking this to heart so quickly!!
Maybe because Iâm so literal, and so new to all of this, but it took me a while to understand âPreferencesâ and âParametersâ were the same thing (and the fact that they werenât numbered before just made me more unsure). Likewise, people talked about switching out the drivers, but inside the deviceâs setting it is called âTypeâ. I donât know if this is just in Hubitat or if there is anything Inovelli can do about it, but maybe they could mention that someplace. Consistency in terminology is a big part of the UI experience. I know most of the people up here are very advanced and I am a complete noob, but I also think that most of us love Inovelli and would like them to succeed by reaching a vastly larger audience. To do so, that means talking to more noobs like me, so the easier, more obvious it is, the better.
Yeah, no problem. A lot of the time what will happen is that we will write a document and then the platform that the document is about will change something. So at one time that screen may have said âDriverâ instead of âTypeâ. We could definitely do better at keeping things up to date. We are hoping to push out a âwikiâ type resource that our users can help keep up to date. Since we are a small company we donât have that many resources to always be on top of things, but we are trying!
My experience with your products so far has been extremely positive. I can imagine how hard it is to expand rapidly having to deal with COVID and other supply issues and hiring. After a Black and Red Series maybe the next line can be an (M go) Blue series. 
Hum⌠let me guess⌠zigbee time?
Awwww yeahâŚ
I cheer for Sparty except one game a year, and especially when you play the team named for a nut.