This blueprint provides universal support for running any custom action when a button is pressed on the provided OSRAM AC025XX00NJ SMART+ Switch Mini. Supports controllers integrated with deCONZ, ZHA, Zigbee2MQTT. Just specify the integration used to connect the remote to Home Assistant when setting up the automation, and the blueprint will take care of all the rest.
In addition of being able to provide custom actions for every kind of button press supported by the remote, the blueprint allows to loop the long press actions while the corresponding button is being held. Once released, the loop stops. This is useful when holding down a button should result in a continuous action (such as lowering the volume of a media player, or controlling a light brightness).
The blueprint also adds support for virtual double button press events, which are not exposed by the controller itself.
Automations created with this blueprint can be connected with one or more Hooks supported by this controller.
Hooks allow to easily create controller-based automations for interacting with media players, lights, covers and more. See the list of Hooks available for this controller for additional details.
Full Documentation
Full documentation regarding requirements, inputs and more is available here.
Docs provide all the information you need to properly configure this blueprint on your instance.
Available Hooks
Light
This Hook blueprint allows to build a controller-based automation to control a light. Supports brightness and color control both for white temperature and rgb lights.
I want to use it. But when I want to use it, my entire automation crashes. I can’t understand why. I use HA version:
Version
core-2021.5.5
Installationstyp
Home Assistant OS
Entwicklung
false
Supervisor
true
Docker
true
Virtuelle Umgebung
false
Python-Version
3.8.9
Betriebssystemfamilie
Linux
Betriebssystem-Version
5.10.37
CPU-Architektur
x86_64
I wanted to use it to control a roller shutter that is controlled with a Tuya switch. I would want to take the Osram switch with me on the terrace. So that if I forget to stop the automation in the evening, I can still stop or open the shutters. I know there are other ways to solve this, but that is the way my dear wife understands.
I’m sorry to hear that this blueprint is causing issues with your entire automation system. Could you please provide the YAML configuration for this Controller blueprint?
Moreover, do you notice any entries in the Home Assistant Logs related to this blueprint?
Hi @epmatt , thank you so much for creating this and i think the blueprint archive you are working on is a really great idea! While I just made it as a total noob to get a few lightify products to simply turn off and on based on a very simple automation, I imported your blueprint above and also the hook to it. I cannot get it do run yet, but am looking into a lot of tutorials and how tos on how to work with YAML here.
I am lacking the basic understanding on how to connect the blueprint and the hook, any resource you could point me to for the basics? Thanks a lot and keep up the great work, thank you! Jens
The article explains in detail how the full ecosystem works and provides YAML examples for common use-cases. It also describes different configurations which can be achieved by combining controllers and hooks in different ways.
Just for being clear, I’d like to note that “connecting a blueprint with a hook” is not a generic Home Assistant concept: you can think about it as an abstraction layer which Controllers and Hooks blueprints take advantage of to implement the desired functionality, in a modular and flexible way.
In fact, Hooks and Controllers are no more than common blueprints, but with “superpowers” built-in.
More generally, the Awesome Ha Blueprints docs website includes all the info to correctly setup your automations. Every blueprint is listed and documented in a separate page. You’ll find that, if not for advanced use-cases, you can pretty much avoid using YAML to setup your automations - just import the desired blueprint and configure automations from the Home Assistant UI.
If you still have any doubts or need additional guidance on how to set up your blueprints, you can reach out to me here. I’m always happy to help as I can.
The entire automation was stopped and could not be started again after I had created an automation with your blueprint.
I had to edit the automation.yaml and remove the part of the blueprint and then restart HA. Then the automations worked again.I couldn’t read anything from the log files.
I deleted your blueprint because it didn’t work for me.
I’ll try again later tonight and I’ll share more information if I can.
I got it to work mate, thanks a lot!!!
Works really super cool, especially with the color change option!
For anybody else that is having issues:
Create an automation by using the controller blueprint and test 2 actions, e.g. light.turn_on and light.turn_off to see if the general connection works. If yes, go ahead, if no, check the deConz integration again and if all devices have been properly found in Phoscon.
Then leave every parameter blank in the automation regarding the button assignment and save.
Go for blueprints again and create another automation based on the controller hook blueprint.
Use the correct settings for your device and save.
Also make sure to create the helper input text file!
Have both activated for a single device in automation.
Tadaaa! Awesome @epmatt !! Really cool stuff! Thanks a lot again!!!
Best regards,
Jens
thank you for your feedback.
I’m sorry for what you’re experiencing with this blueprint. If you’ll have a chance to import the blueprint again on your system and somehow obtain the Home Assistant logs while the automation is enabled, we’ll take a look at this issue. Moreover, the YAML configuration for the automation that is provoking the halt might be useful in this case.
If you have any issues or doubts on how to setup this blueprint I’ll be glad to help.
thank you so much for your nice feedback! I’m really happy to hear that this blueprint is useful for you.
Go for blueprints again and create another automation based on the controller blueprint.
Just a little note here: I guess in this sentence you’re referring to “the Light Hook blueprint”, not the controller one (you’ll need a Controller Automation + Light Hook automation to implement the functionality you described).
Get Started
Blueprint URL
Description
Full Documentation
Available Hooks
Light
Media Player
Changelog
