Just used it to turn on and off the indicator lights on the ZEN32 5 button switch.
Recently utilized the ZEN32 Scene Controller blueprint to use the small Scene buttons to control other devices. However, using that you do not want the indicator LED lights to just follow the button presses on the ZEN32, what you really want is for the indicator lights to follow the state of the other device being controlled.
Your blueprint makes that easy.
How To: Set one of the entities in this blueprint automation to one of the “XXX Button Y indication - Binary” entries where
XXX is your ZEN32 device name
Y is the button that you want the LED light to be synced
where 1 = the big button, 2 is top left little button, 3 is top right, 4 is bottom left, 5 is bottom right. NOTE: This is NOT the same as the scene name numbers where Scene 005 is the big button.
Thanks Chris. For more than a year I had a custom automation based on groups, but it was difficult to maintain (I had 20 groups with 20 automations). The main use-case was Sonoff TX3 light switches. I use them to control lights and relays, but often I need to manage a single light or relay from several rooms.
Lately I used it to link the pool lights, that are managed through a Shelly relay, with the internal relay of my new Hayward Aquarite salt chlorinator, which also has internal relays for lights, etc. So instead of rewiring the lights and connect them to the Aquarite light relay, I simply linked the Shelly with the Aquarite relay entity. So a “virtual” connection, and it works perfectly. Now when I use the Aquarite to turn on the lights, when I turn its relay ON, the Shelly goes ON and the lights are turned ON.
It’s really a simple thing, and I think that the HA Group entity should offer this kind of functionality natively. But since it doesn’t, I created this simple Blueprint.
Please paste the link in the browser and show me the first lines…
It’s a caching issue, or you were trying before I fixed it. You should these 4 lines at the beginning of the file, and with my name without @, that was the cause of the problem.
Glad it worked. Please let me also know if the automation works, if there’s something in the logs, etc. Unfortunately I’m the only one who tested it extensively, and I want to be 99% sure everything’s ok.
Hi Alex, thank you for building this Blueprint! It is so simple and it works very well.
I have created a pull request to add a few enhancements for your consideration:
- Changed the action to a "Choose" building block to support fan (and future) attributes
- Added support for linked fan speeds
- Added support for linked light brightness and light color temperature
Great idea. Thanks a lot for your contribution. I can only test the lights, I have no fans. Did you test it 100%? No issues? If so, I will merge it, please let me know.
I’m a firm believer that the best things are the simple ones. Less is more…
I’ve had issues with similar blieprints if I accidently press the switch twice in a row very fast, both switches end up in an infinite loop with no ability to stop toggling
i tried with a swith and dimmable smart led bulb’s group. It really can enter an endless loop if you change the switch state twice in a raw faster than light transition time is
button and click here:
