Thanks for checking out the blueprint script! Sorry it took me so long to get back to you; it took me awhile to remember how the White Series devices worked. It’s not straightforward. Also, I found a bug in the code (which you might have been hitting) and published a new release today. Be sure to pull the latest blueprint before running any of the commands below.
To change the color of the LED bar that indicates the dim level of the load—light(1)—you would use something like this to permanently change the color:
action: script.inovelli_led
data:
entity:
- light.white_series_smart_2_1_switch_light_1
LEDnumber: All
LEDcolor: Lime
LEDbrightness: 8.1
If you want to indicate an event, you might use light(6) and the effect section for that. In this example it’ll turn pink for 30 seconds and then turn off (showing the LED bar that indicates the dim level of the load), but you could change that to forever. This LED bar only supports the solid effect and nothing else. When something is set and the load changes (e.g. the device is turned off), the effect will turn off, you’ll see the load LED bar dimming, and then the effect will reappear. Play around with it a bit and it should make more sense.
action: script.inovelli_led
data:
entity:
- light.white_series_smart_2_1_switch_light_6
effect: Solid
brightness: 8
color: Pink
duration: 30 Seconds
To clear the effect after forever, you’d just call the script with the effect entity alone:
action: script.inovelli_led
data:
entity:
- light.white_series_smart_2_1_switch_light_6
…or just turn off the light with a light.turn_off action, like you suggested.
Alternatively, you could template the color to reflect the alert:
action: script.inovelli_led
data:
entity:
- light.white_series_smart_2_1_switch_light_1
LEDnumber: All
LEDcolor: "{{ iif(is_state('sensor.front_door','on'),'red','blue') }}"
LEDbrightness: 8.0
In that example, you’d need to trigger on any state change for sensor.front_door and re-call this script. It should turn the light(1) LED bar red when the door is open and blue when it’s closed.
I think there are several ways to do what you’re trying to do, so hopefully that gets you started with some ideas. Both of the method’s you’ve suggested are valid.
… I can just use an automation to trigger on/off action for the second light entity. That’s all I need really.
Or should I be calling the script for to push a color change as an action in an automation and ignore the second light entity?"
