As of now I’ve got a 2-1 switch and a fan switch in my bedroom and 5 2-1 switches in my master bathroom/wc and I decided to have some fun. I set up a Home Assistant script that when I quad press the config button on any of these switches I run a “red alert” script which sets the LED animation on all 7 devices to medium falling bright red on all 7 devices. Then if I single press the config button it clears the effect on all. Yeah I’m a geek but so are you.
The only thing that would make it any more perfect is if the LED effect was in sync on all the devices which it currently isn’t I’m sure because MQTT the script is sending mqtt commands to each switch individually which is going out as a zigbee message, but it also seems like maybe even with the same settings that the effect on the 2-1 switches might not be the same speed as the fan switch which is possible since they have different firmware and probable software timing loops.
So I’m wondering what other “it just had to happen” little easter eggs other people have implemented, or does anyone have an improvement to how to make the animations sync better across devices that might be next to each other?
Quick video here: https://youtu.be/iMHd25-mzZk
1 Like
Care to share your script and let the rest of us add to the fun?
Hopefully this will get you there. I installed this blueprint: https://github.com/kschlichter/Home-Assistant-Inovelli-Effects-and-Colors and used it to create the following script (you’ll have to change the entities):
alias: Start Red Alert Effect
use_blueprint:
path: kschlichter/inovelli_led_blueprint.yaml
input:
color: Red
effect: Fall Medium
LEDnumber_effect: All
duration: Forever
domain:
brightness: 10
entity:
- light.mbath_ceiling_light
- light.mbath_shower_light
- light.mbath_sink_light
- light.mbath_tub_light
- light.mbath_wc_light
- fan.mbed_fan
- light.mbed_fan_light
description: “”
to turn on the effect and a very similar one to clear the effect.
The I created an automation where quad pressing the config button on any of those switches would run the script:
alias: Red Alert
description: “”
triggers:
- domain: mqtt
device_id: 9ad2a9e2df8f2e8190c499355877a4d2
type: action
subtype: config_quadruple
trigger: device
alias: mbed_fan_light_config_quadruple
- domain: mqtt
device_id: 7f1dd34ada71c96a3f3aa6fde2f976ce
type: action
subtype: config_quadruple
trigger: device
alias: mbed_fan_config_quadruple
- domain: mqtt
device_id: b2bca37f5f51a4c7e38084ad8bb45d42
type: action
subtype: config_quadruple
trigger: device
alias: mbath_ceiling_light_config_quadruple
- domain: mqtt
device_id: cbd35b79ff3fc1ebcf4c7f5c7fa0b825
type: action
subtype: config_quadruple
trigger: device
alias: mbath_sink_light_config_quadruple
- domain: mqtt
device_id: 2f1a0106f5bc48056742c9ab5f0a62ce
type: action
subtype: config_quadruple
trigger: device
alias: mbath_shower_light_config_quadruple
- domain: mqtt
device_id: e75093a5d93b57df014a90fd74ecda14
type: action
subtype: config_quadruple
trigger: device
alias: mbath_tub_light_config_quadruple
- domain: mqtt
device_id: 693f03c08adc5c71582c2013c213488e
type: action
subtype: config_quadruple
trigger: device
alias: mbath_wc_light_config_quadruple
conditions:
actions:
- action: script.red_alert
metadata: {}
data: {}
mode: single
I have a similar automation that when the config button is single pressed on any of the devices it runs the clear red alert script.
There’s a minor extra step I have in mine because for one fan switch I have the parameter set to only use a single LED to indicate on and when this is set the LED effect setting seems to do nothing, so I have an extra step that disables single LED mode before starting red alert and enabling it when red alert is disabled.
If you need more of the pieces I’ll be happy to provide, I’m just trying to avoid repeating minor versions of things above.