Pretty automatic. The switch will send Hubitat the how many pressed or held and Hubitat will perform the rule you assigned.
Request: Is there a way we could have access in ST to reset power (via Webcore if possible)?
I’d like to understand month to month how much we are using different lighting and by sending kwh to stream and resetting each month I think I should be able to accomplish that.
There should be the “reset” command that you can use to reset the accumulated energy statistics. It is a tile in the classic SmartThings app and you should be able to access it with WebCoRE by just selecting the reset command.
Like this?:
Note @Inovelli_Switches is a global device list corresponding to all of my switches. Easier to add once into my system that way.
Seems easy enough, will let you know. Thanks for the reply!
1 Like
Update: Are you guys still tracking the 3-way shutoff issue over 80% when using dumb switch as aux? Mine are still having this issue. Locked it into 80% max via WebCore but it’s still an issue as late as 1.43.
Can you tell me what the 80% issue is? I just posted in the Hubitat section that I was having an issue with one switch turning itself off. I also have it in a 3-way configuration with a dumb switch.
Basically if I set my switch in a 3 way at 100% on, after about 30 seconds the switch turns off. Switch was brand new when installed and has a VERY small load (3W registered) and is not overheating or anything.
When I set to 80% it works as expected.
Edit: Found this up top, sounds like it’s being worked on:
Load shutting off when dimmer is set at a higher level in 3-way w/Dumb switch . There is a method that the dimmer uses to detect when one of the dumb switches is toggled. At higher levels, the dimmer sometimes interprets a toggle when one does not occur. Firmware engineers are looking into this, but currently the workaround is to set the maximum level to between 80 & 90.
Thanks - mine does not turn off that quickly. I also found the thread that talks about the issue with the 3-way installation, dumb switches and lights turning off and I have added to the thread so I should get notified if there is a resolution.
One question (if you are on Hubitat or if your hub has similar access to parameters) - which parameter did you set to 80%? I set Parameter 6 (Maximum Level: The maximum level that the dimmer allows the bulb to be dimmed to. Useful when the user has an LED bulb that reaches its maximum level before the dimmer value of 99. Range: 55…99 Default: 99) in Hubitat to 80 but when I looked at the “Current States” it still showed Level as 99, so not sure if it is not sticking or if that is expected. I did turn the switch on/off (both from the hub and physical switch) after I changed the setting but still no change.
Yes, parameter 6 in my ST is 80 and it’s been working flawlessly. I actually can’t tell the difference in brightness and load is under 5W.
1 Like
Can you see the current state in ST? If so, can you tell me know what value you see for “level”?
In Hubitat, I don’t see it change and even though I set the parameter to 80, it shows 99. Not sure if what it is showing is the same as the max value but if you show 99 as well, then I will go back and set param 6 to 80 again. This is what my hub shows currently.
My understanding is that the parameter does a calculation and does percent of max setting. so 99% of 80% is 80% (ish). Level still works 1-99, but only really provides the amps for low to high (as set in applicable parameters).
2 Likes
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.
1 Like
Ah, yep. That was the problem. I switched them and it works as expected now. Thanks!
2 Likes
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.
Thank you Eric, I was able to read up on the Smart Bulb Mode a little more in the 1.47 firmware post. I found the following screenshot that illustrated the duplicate menus. I’m glad it’s been cleaned up now!
1 Like
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.