I actually wrote a set of drivers to do exactly that.
You’ll need the “parent” driver for whichever switch you have (LZW30-SN or LZW31-SN), and optionally the child drivers for the “Default,” “Off,” and “Notification” LEDs. The Default LED device lets you treat the “regular” LED bar (when on or sometimes when off) like a an RGB bulb, adjusting its color and level with standard commands. The “Off” LED is a level-only device (color comes from the default LED, per the way the devices actually work) and allows you to set the level of the LED when off. The “Notification” LED driver lets you treat the notification LED like an RGB bulb, this time adding the little-used Hubitat “LightEffects” capability to allow you to start a notification with almost no custom commands (except setDuration
if you want).
You don’t have to use the child devices (or install the drivers); all of this is also exposed as a custom command on the parent device. In your case, setDefaultLEDColor
is the command I’d probably pay the most attention do. It takes an “Inovelli-scaled” color value 0-255 (scaled either up from Hubitat’s typical 0-100 hue model or down from the standard 0-360 model where both extremes are red). You could create something in RM that sends this custom command to the device whenever the switch turns on/off. You can adjust the level if needed with setDefaultLEDLevel
and setOffLEDLevel
if needed as well; both take values from 0-10 (0 is supposed to be off, though I haven’t tested that). If you use the child devices, you can also just treat these like “standard” devices and use an app like Simple Automation Rules/Simple Lighting to do this instead.
As I said on a Hubitat thread where I announced these drivers, I can’t decide if treating the LED bar (and its various states) as a mostly-standard RGB bulb or dimmer was such a great idea that I’m surprised no one else tried it first or such a crazy idea that someone thought about it and dismissed it.
Personally, I like it.
Here’s the folder where I’m keeping these: