. In the not so distant past, there was an ability to set which LED was on, it’s color and whether or not that LED would blink.
I am trying to figure out, what (and if it exists) is the command to send and the arguments to include. in the ST App, the LEDs are all on the settings tab, so i am (hoping) sure that there is a command that is being sent under the hood to make that work, but can i do that from a Rule?
The only way to change things on the Settings tab of the app is through the Settings tab of the app.
The way to do this is to modify the driver… Remove the LED parameter from the Settings tab and use a custom capability to control it instead, which will allow it to be controlled through the Details tab or automations.
@Mariano_Colmenarejo : i want to be able to SET the LED color and status (blink or not) when something else happens. if a door unlocks, set the LED red, if locked, set it green.
these switches have a number of LED (for the HS-WS200 there are 7). i plan that LED 1 = Front Door status, LED2 is Garage Door status, etc,
i have 4 of these throughout my house, so at a glance i can see if there are any open doors, unlocked doors, who is home, lights on in the garage, etc.
with WebCore i had a whole piston to manage that and was hoping to replicate the functionality in a Rule, but as @philh30 pointed out, the Edge driver, as it is now, won’t allow for it as the led colors are implemented as a setting and there is no command provided to actually call from a Rule.
there needs to be a command to set NORMAL MODE (which would show the level of the dimmer) or STATUS Mode (which allows for the setting the color and mode of each LED individually)
example (i used the app to set the colors manually, i want to do this with an automation (rule, but a scene would be cool too)
OK, I took a quick look at the original Groovy DTH for the dimmer, written by the always impressive @krlaframboise , and while I am limited in my understanding because I use a screen reader, it looks like that was created with a whole bunch of child devices which handled the setting of the individual colors and blink rates for the indicator LEDs.
The original edge Driver architecture didn’t use a parent/child construct but they did add one later because they couldn’t get voice control of the individual components without it.
So my guess is you could use exactly the same approach in an edge driver and build on the work that @krlaframboise did for the groovy version as long as there’s not some new limit on the number of child devices.
So I would suggest going to the author of the new edge driver and making that suggestion to them.
Here’s the link to the Groovy DTH for the dimmer so you can see what I mean
Once you have those child devices, turning them on and off from a regular routine should be very straightforward. They’ll just look like another RGBW smart bulb.