While I think we can also achieve a “turn off the LED” by setting the LED mode, to “2 - LED always off “ in just about every device I’ve checked anyhow, that’s messing with behaviors of the LED mode which drives the relay/switch status.
Can we introduce an enhancement request that we support a mode “3 – off(0%)” for the LED Indicator Parameter?
My use case here is that I want to basically turn off the LED at night in bedrooms and on to one of the percentage levels during the day. Strictly a “BRIGHTNESS” function, without screwing with the “LED MODE” functionality. So, at “day” I can set the level to a percentage, and at night, I set to off. This allows me to still control what a LED does based on switch/relay action in standalone device moments, or as part of a paired hub operation.
Thanks!
(BTW, this is particularly desired as the LED brightness between units or models isn’t always noticeably dimming, and units side-by-side are visibly different at the different levels too. One at 30% at night is great, but the one next to it still screams at ya from bed at the same percentage! With the case of scene controllers zen32/zen35, being able to turn off all but the button you want to find in the dark would be nice. I doubt there’s a way to calebrate brightness as its probably more a parts issue, but if there were, that’d be a great enhancement to make as well)
It’s a bit of a different requirement but do I understand correctly if you’d like to have full-spectrum control of the LED indicator’s brightness level vs just 3 levels to choose from?
Noted! We’ll check how these settings can be expanded. If anyone else would like to chime in with suggestions or add to demand, please leave a note. This will help us prioritize the request
+1
Please add my vote. Low is unfortunately way too bright for me in most cases, especially on the ZEN32 and ZEN35 for some reason. I’d almost like a setting that is about 1/2 or 1/4 the brightness of low. Thank you!
I’d be amicable to depricating the existing parameter in leu of 0%→100% vs the original request. Just as long as we have an “off” value exposed someplace.
If you are planning on leaving it, I’d suggest adding 3 for 0% and in the firmware map the legacy parameter into the new % parameter for backward compatibility. (The drawback is getting a new parameter in various drivers… But, maybe you can have your SmartThings developer also do that for Hubitat this time around…)
My 2 cents would be to add an Off and 1/2 Low to the brightness enumeration. Exposing a 0-100 range might get people thinking about flooding CCs to get fancy animations working.
But if you want to be super cool and explode the amount of possibilities for people to use the LED in their scenes… add an onboard animation controller. Let us pick from a list of available animations and adjust an Animation Duration parameter:
Off (default behavior; LED does not animate)
Ramp Up (LED goes from 0 to brightness_setting in anim_duration seconds, then resets to 0 and repeat)
Blink (LED is off for anim_duration, then turns on for ~500ms, then back off and repeat)
Pulse (LED ramps up from 0 to brightness, then ramps down back to 0, all in anim_duration seconds, repeating)
Now I can make my light switch pulse bright red when I have unread email. I’m sure others could think of better ways to use that.
I agree. The current dim levels are too bright for a darkly lit room. If the only option is blinding bright or off that seems too restrictive. Since the brightness is achieved via PWM of the LED it would seem pretty simple to allow that duty cycle to be selectable.
I’m sure others could think of better ways to use that.