🔘

Button Actions

Blueprints for button press actions and controls

94 blueprints found

🔘
Button Actions
complex
17 inputs

Send a mobile notification when add-on update is available

Send a mobile notification when add-on update is available

Send a notification to the provided mobile devices whenever an update for the given Home Assistant add-on is available. Supports full notification customization, notification groups, auto-dismissal when the add-on is updated and button for starting the update directly from your notification tray, with optional notification after the update completed succesfully. 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2021.10.26
addon
text
entity
+2
1.2K1.6K2.5K
🔘
Button Actions
complex
37 inputs

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller automation for executing any kind of action triggered by the provided IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K9.2K702
🔘
Button Actions
complex
19 inputs

Controller - IKEA E1743 TRÅDFRI On/Off Switch & Dimmer

Controller - IKEA E1743 TRÅDFRI On/Off Switch & Dimmer

Controller automation for executing any kind of action triggered by the provided IKEA E1743 TRÅDFRI On/Off Switch & Dimmer. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K1.7K786
🔘
Button Actions
complex
15 inputs

Controller - IKEA E1744 SYMFONISK Rotary Remote

Controller - IKEA E1744 SYMFONISK Rotary Remote

Controller automation for executing any kind of action triggered by the provided IKEA E1744 SYMFONISK Rotary Remote. Allows to optionally loop a custom action during controller rotation. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K6.0K4.8K
🔘
Button Actions
complex
13 inputs

Controller - IKEA E1766 TRÅDFRI Open/Close Remote

Controller - IKEA E1766 TRÅDFRI Open/Close Remote

Controller automation for executing any kind of action triggered by the provided IKEA E1766 TRÅDFRI Open/Close Remote. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K10.6K4.0K
🔘
Button Actions
complex
6 inputs

Controller - IKEA E1812 TRÅDFRI Shortcut button

Controller - IKEA E1812 TRÅDFRI Shortcut button

Controller automation for executing any kind of action triggered by the provided IKEA E1812 TRÅDFRI Shortcut button. Allows to optionally loop an action on a button long press. The blueprint handles double button press events natively as it is supported by the controller device itself. Supports Zigbee2MQTT, ZHA, deCONZ. 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.

More Info

ℹ️ Version 2025.04.12 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
action
1.2K9.8K1.6K
🔘
Button Actions
complex
33 inputs

Controller - IKEA E2001/E2002 STYRBAR Remote control

Controller - IKEA E2001/E2002 STYRBAR Remote control

Controller automation for executing any kind of action triggered by the provided IKEA E2001/E2002 STYRBAR Remote control. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K8.9K4.8K
🔘
Button Actions
complex
18 inputs

Controller - IKEA E2123 SYMFONISK sound remote, gen 2

Controller - IKEA E2123 SYMFONISK sound remote, gen 2

Controller automation for executing any kind of action triggered by the provided IKEA E2123 SYMFONISK sound remote, gen 2. Supports Zigbee2MQTT, ZHA, deCONZ. The blueprint handles double button press events natively for the dots1/dots2 buttons as it is supported by the controller device itself. Long and Double press events can be enabled/disabled for each of the dots1/dots2 buttons to get extra speed in recognizing single press events. 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 lights, covers, media players, and potentially more. See the list of Hooks available for this controller for additional details. This blueprint is only compatible with firmwares 1.0.32 (20221219) and 1.0.35 (20230308) of the IKEA E2123 SYMFONISK sound remote, gen 2. A small note, avoid using both custom actions and Hooks in the same blueprint, otherwise strange things may occur.

More Info

ℹ️ Version 2025.03.28 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
action
1.2K10.4K1.6K
🔘
Button Actions
complex
11 inputs

Controller - IKEA E2201 RODRET Dimmer

Controller - IKEA E2201 RODRET Dimmer

Controller automation for executing any kind of action triggered by the provided IKEA E2201 RODRET Dimmer. Allows to optionally loop an action on a button long press. Allows for Virtual Double Presses. Needs to be enabled in blueprint. Supports Zigbee2MQTT, ZHA, deCONZ. 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 lights, covers, media players, and potentially more. See the list of Hooks available for this controller for additional details.

More Info

ℹ️ Version 2025.03.20c 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
action
1.2K6.8K843
🔘
Button Actions
complex
10 inputs

Controller - IKEA E2213 SOMRIG shortcut button

Controller - IKEA E2213 SOMRIG shortcut button

Controller automation for executing any kind of action triggered by the provided IKEA E2213 SOMRIG shortcut button. Allows to optionally loop an action on a button long press. The blueprint handles double button press events natively as it is supported by the controller device itself. Supports Zigbee2MQTT, ZHA, deCONZ. 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 lights, covers, media players, and potentially more. See the list of Hooks available for this controller for additional details. A small note, avoid using both custom actions and Hooks in the same blueprint, otherwise strange things may occur.

More Info

ℹ️ Version 2025.03.26 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
action
1.2K8.3K4.6K
🔘
Button Actions
complex
12 inputs

Controller - IKEA ICTC-G-1 TRÅDFRI wireless dimmer

Controller - IKEA ICTC-G-1 TRÅDFRI wireless dimmer

Controller automation for executing any kind of action triggered by the provided IKEA ICTC-G-1 TRÅDFRI wireless dimmer. Allows to optionally loop a custom action during controller rotation. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K7.1K5.0K
🔘
Button Actions
complex
26 inputs

Controller - OSRAM AC025XX00NJ SMART+ Switch Mini

Controller - OSRAM AC025XX00NJ SMART+ Switch Mini

Controller automation for executing any kind of action triggered by the provided OSRAM AC025XX00NJ SMART+ Switch Mini. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K9.1K3.3K
🔘
Button Actions
complex
33 inputs

Controller - Philips 324131092621 Hue Dimmer switch

Controller - Philips 324131092621 Hue Dimmer switch

Controller automation for executing any kind of action triggered by the provided Philips 324131092621 Hue Dimmer switch. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K9.8K1.9K
🔘
Button Actions
complex
12 inputs

Controller - Philips 8718699693985 Hue Smart Button

Controller - Philips 8718699693985 Hue Smart Button

Controller automation for executing any kind of action triggered by the provided Philips 8718699693985 Hue Smart Button. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K5.2K992
🔘
Button Actions
complex
33 inputs

Controller - Philips 929002398602 Hue Dimmer switch v2

Controller - Philips 929002398602 Hue Dimmer switch v2

Controller automation for executing any kind of action triggered by the provided Philips 929002398602 Hue Dimmer switch v2. Allows to optionally loop an action on a button long press. Supports ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K3.4K1.8K
🔘
Button Actions
complex
7 inputs

Controller - SONOFF SNZB-01 Wireless Switch

Controller - SONOFF SNZB-01 Wireless Switch

Controller automation for executing any kind of action triggered by the provided SONOFF SNZB-01 Wireless Switch. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+2
1.2K7.2K3.1K
🔘
Button Actions
complex
10 inputs

Controller - Tuya ERS-10TZBVK-AA Smart knob

Controller - Tuya ERS-10TZBVK-AA Smart knob

Controller automation for executing any kind of action triggered by the provided Tuya ERS-10TZBVK-AA Smart knob. Allows to optionally loop an action on a button long press. The blueprint also adds support for virtual double button press events, which are not exposed by the controller device itself. However, It needs to be enabled in the blueprint. Supports Zigbee2MQTT, ZHA. 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 lights, covers, media players, and potentially more. See the list of Hooks available for this controller for additional details. A small note, avoid using both custom actions and Hooks in the same blueprint, otherwise strange things may occur.

More Info

ℹ️ Version 2025.03.29 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
action
1.2K7.9K5.0K
🔘
Button Actions
complex
18 inputs

Controller - Xiaomi WXCJKG11LM Aqara Opple 2 button remote

Controller - Xiaomi WXCJKG11LM Aqara Opple 2 button remote

Controller automation for executing any kind of action triggered by the provided Xiaomi WXCJKG11LM Aqara Opple 2 button remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K7.0K2.2K
🔘
Button Actions
complex
32 inputs

Controller - Xiaomi WXCJKG12LM Aqara Opple 4 button remote

Controller - Xiaomi WXCJKG12LM Aqara Opple 4 button remote

Controller automation for executing any kind of action triggered by the provided Xiaomi WXCJKG12LM Aqara Opple 4 button remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K2.1K2.8K
🔘
Button Actions
complex
46 inputs

Controller - Xiaomi WXCJKG13LM Aqara Opple 6 button remote

Controller - Xiaomi WXCJKG13LM Aqara Opple 6 button remote

Controller automation for executing any kind of action triggered by the provided Xiaomi WXCJKG13LM Aqara Opple 6 button remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04.19 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K4.1K4.9K
🔘
Button Actions
complex
10 inputs

Controller - Aqara WXKG11LM Wireless Mini Switch / Xiaomi WXKG01LM Mi Wireless Switch

Controller - Aqara WXKG11LM Wireless Mini Switch / Xiaomi WXKG01LM Mi Wireless Switch

Controller automation for executing any kind of action triggered by the provided Aqara WXKG11LM Wireless Mini Switch / Xiaomi WXKG01LM Mi Wireless Switch. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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.

More Info

ℹ️ Version 2025.04,16 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
select
device
entity
+3
1.2K3.6K3.1K
🔘
Button Actions
medium
3 inputs

Hook - Cover

Hook - Cover

Hook automation which allows to control a cover. Supports opening, closing and tilting the cover. Features may vary depending on the selected cover. Features may vary depending on the selected Controller. An automation created with this blueprint must be linked to a Controller automation. Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They expose an abstract interface used by Hooks to create controller-based automations. A list of controllers supported by this hook is available here.

More Info

ℹ️ Version 2025.03.28 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
select
entity
1.2K4.7K3.0K
🔘
Button Actions
complex
13 inputs

Hook - Light

Hook - Light

Hook automation which allows to control a light. Supports brightness and color control both for white temperature and rgb lights. Features may vary depending on the selected Controller. An automation created with this blueprint must be linked to a Controller automation. Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They expose an abstract interface used by Hooks to create controller-based automations. A list of controllers supported by this hook is available here.

More Info

ℹ️ Version 2025.03.29 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
select
entity
+2
1.2K5.7K2.6K
🔘
Button Actions
medium
5 inputs

Hook - Media Player

Hook - Media Player

Hook automation which allows to control a media player. Supports volume setting, play/pause and track selection. Features may vary depending on the selected Controller. An automation created with this blueprint must be linked to a Controller automation. Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They expose an abstract interface used by Hooks to create controller-based automations. A list of controllers supported by this hook is available here.

More Info

ℹ️ Version 2025.03.29 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟
device
select
entity
+1
1.2K5.8K2.8K
🔘
Button Actions
medium
2 inputs

Octoprint_Additional_Buttons_Helper- 2024-06-08

This is Blueprint is provided as a helper for people using the Octoprint Plugin called OctoPrint-HomeAssistant. What this does is add 8 buttons, 4 of which you as the user can set your own G-Codes to for customizing. Also adds safe shutdown and presentation functions along with Change Filament and Load Filament. The first thing to remember is ANYTIME you make ANY changes to this Blueprint, you MUST restart the server so that the button entities can rebuild in the configuration you have selected. If you don't restart OctoPrint, the change may not be seen and you will wonder why and what is happening. To use this you will need the OctoPrint-MQTT plug-in installed along with the OctoPrint-HomeAssistant plugin. You will also need to be connected to an MQTT Broker that your Home Assistant instance is also connected to. Set-up for all that is covered within those packages. This also a Safe Shutdown to your setup that will stop the OctoPrint server then shut down the PI & power off your devices safely and cleanly. This works either by manually pressing a Home Assistant Button manually or it can be triggered as the temperature of the hot end ramps down with adjustable trigger points. This feature requires you to have mains power switch(s) to control power to the printer and peripherals. There is also a Presentation button that raises the Z and moves the print out for better access. Caution, this button assumes that the printer knows where home is and moves to an absolute position. The intention is to use it after a print has happened and you want access to get the item off the platter. If pressed when HOME is unknown it might bump into the end of the Y axis. Also if the Z is very high, it blindly moves the Z up 40 mm so make sure it looks like there is room. These values can be adjusted by editing the Blueprint itself if needed. Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2002.1K352
🔘
Button Actions
complex
16 inputs

Aqara Magic Cube ZHA - 2024-06-04

This Blueprint uses a Z2M Event Sensor to sort out the 38(+54) unique actions available from the Xiaomi Magic Cube Remote. (Some unique actions are available thru templating only. See the related document.) The split out of functions gives you the ability to assign local scripts or functions to do the things you want the remote to do. Functions that are left empty will simply do nothing.

🍎 There is a set of 36 event functions that will trigger on specific actions on specific sides that are listed as Group 1 actions 🍎.

🍒 There is a set of 6 event functions that will trigger on specific actions on ANY side that are listed as Group 2 sctions 🍒.

🍐 There is a set of 30 event functions that will trigger on cube flips to & froma specific sides that are listed as Group 3 sctions 🍐.

🍕 There are 2 actions (shake and drop) that only occur once and are OK to be combined with any other group. Listed as Group 4 sections 🍕.

Please be aware that ALL actions except the 2 listed above, 🍕 will trigger an action in ALL 3 groups at the same time every time. Therefore I suggest if you just have a couple of things you want this remote to do that you choose the ANY / Group 2 / 🍒 events. If you want more than a few events, you should select actions in Group 1 / 🍎 OR Group 3 / 🍐. With careful selection you can use mixed groups, but you run the risk of a single cube action triggering more than 1 Home Assistant action and making a mess of things 🍱.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

There is sample code to make the template sensor in the help file on GitHib named Zigbee2MQTT - Xiaomi Cube Controller.md & in the community page related to this. Within this blueprint there is an event handler that will latch the last action that the blueprint finds and sends that to the event buss. From there a simple Template sensor can grab it and show you the last action sent. Thie will help when setting up new functions and to troubleshoot strange behaviours. _________________________
This was "forked" from >> Aqara Cube ZHA - Simplified face-based device control > Project authored by EdwardTFN (Edward Firmo) and he based on on several other giants that came up with most of the base code. >> >> ZHA - Aqara Magic Cube (57 actions) >> >> Aqara Magic Cube ZHA (51 actions) >> >> ZHA - Aqara Magic Cube (24 actions) > >I sincerely thank Them for their work. I wanted to support a version that was virtually the same as my Z2M version, and leverage all the documentation and code samples there but still port it to ZHA. I also had a better idea for troubleshooting info. _________________________
Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2009.8K3.7K
🔘
Button Actions
complex
30 inputs

Aqara-Magic-Cube-T1-Pro-(CTP-R01) - 2024-06-04

This Blueprint uses a Zigbee2MQTT built sensor to sort out the 58+ unique commands (118+ total) available from the Xiaomi Magic Cube Remote. (Some unique commands listed as + are not counted & available thru templating only. See the related document.) NOTE: This blueprint is for the PRO cube version ONLY and is not fully compatible with the original version of the cube. Links for those are in my GIT repository. This cube has an 'Action' mode (Shown below with this graphic: 🫳 ACTION MODE ONLY 🫳 ) and a 'Scene' mode (Shown below with this graphic: 👀 SCENE MODE ONLY 👀 ). Make sure the cube is in the mode you think it is in when triggering it. The functions are separate. IE 'Action - slide' will do something different from 'Scene - slide'. The split out of functions gives you the ability to assign local scripts or functions to do the things you want the remote to do. Functions that are left empty will simply do nothing.

🍎 There is a set of 36 + 18 actions that will trigger on specific actions on specific sides that are listed as Group 1 🍎

🍒 There is a set of 6 + 3 actions that will trigger on specific actions on ANY side that are listed as Group 2 🍒

🍐 There is a set of 30 + 30 event functions that will trigger on cube flips to & from specific sides that are listed as Group 3 🍐

🍕 There are 5 actions (shake & throw for each mode & hold in scene mode) that only occur once in each mode & are OK to be combined with any other group in that mode. Listed as Group 4 sections 🍕.

Please be aware that ALL actions except the 4 listed above, 🍕 will trigger an action in ALL 3 groups in the matching mode at the same time every time. Therefore I suggest if you just have a couple of things you want this remote to do that you choose the ANY / Group 2 / 🍒 events. Action events and Scene events are separate from each other. If you want more than a few events, you should select actions in Group 1 / 🍎 OR Group 3 / 🍐. With careful selection you can use mixed groups, but you run the risk of a single cube action triggering more than 1 Home Assistant action and making a mess of things 🍱.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

This blueprint has been known to freak out when there are spaces or odd characters in the MQTT Topic. Make sure there are no spaces, ONLY a single word, and ONLY A thru Z, a thru z, and 0 thru 9 in the topic. ( / is ok between device and topic) If there are, you will need to change the name of the cube to remove those characters.

IF YOU SEE --> TemplateError: Must provide a device or entity ID

If you get an error like that, The friendly_name in Z2M likely does not match the friendly_name on HA. To fix go into the Z2M Open web UI and set the friendly_name there. Setting this in just HA or in Z2M without ticking the update HA box will cause this. See the blueprint documentation page for details. There is sample code to make the template sensor in the help file on GitHib named Zigbee2MQTT - Xiaomi Cube Controller MQTT Triggered.md & in the community page related to this. Within this blueprint there is an event handler that will latch the last command that the blueprint finds and sends that to the event buss. From there a simple Template sensor can grab it and show you the last action sent. Thie will help when setting up new functions and to troubleshoot strange behaviours.
This was forked from https://community.home-assistant.io/t/z2m-xiaomi-cube-controller/263006 1.2 project authored by luckypoppy and the friends he pulled together to create the base. I sincerely thank Him (Them) for their work. I felt there needed to be more documentation for rookie users to properly set this up. I had quite a few questions and when I saw a few questions in that chat from people struggling, I wanted to help. I also had a better idea for troubleshooting info.
Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2001.0K3.8K
🔘
Button Actions
complex
16 inputs

Aqara Magic Cube Zigbee2MQTT MQTT Triggered - 2024-06-02

This Blueprint uses a Zigbee2MQTT built sensor to sort out the 38(+54) unique commands available from the Xiaomi Magic Cube Remote. (Some unique commands are available thru templating only. See the related document.) The split out of functions gives you the ability to assign local scripts or functions to do the things you want the remote to do. Functions that are left empty will simply do nothing.

🍎 There is a set of 36 event functions that will trigger on specific actions on specific sides that are listed as Group 1 actions 🍎.

🍒 There is a set of 6 event functions that will trigger on specific actions on ANY side that are listed as Group 2 actions 🍒.

🍐 There is a set of 30 event functions that will trigger on cube flips to & from specific sides that are listed as Group 3 actions 🍐.

🍕 There are 2 actions (shake and drop) that only occur once and are OK to be combined with any other group. Listed as Group 4 sections 🍕.

Please be aware that ALL actions except the Group 4 actions 🍕 will trigger an action in ALL 3 groups at the same time every time. Therefore I suggest if you just have a couple of things you want this remote to do that you choose the ANY / Group 2 / 🍒 events. If you want more than a few events, you should select actions in Group 1 / 🍎 OR Group 3 / 🍐. Group 4 actions 🍕 will not affect others. With careful selection you can use mixed groups, but you run the risk of a single cube action triggering more than 1 Home Assistant action and making a mess of things 🍱.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

There is sample code to make the template sensor in the help file on GitHib named Zigbee2MQTT - Xiaomi Cube Controller MQTT Triggered.md & in the community page related to this. Within this blueprint there is an event handler that will latch the last command that the blueprint finds and sends that to the event buss. From there a simple Template sensor can grab it and show you the last action sent. Thie will help when setting up new functions and to troubleshoot strange behaviours.
This was forked from https://community.home-assistant.io/t/z2m-xiaomi-cube-controller/263006 1.2 project authored by luckypoppy and the friends he pulled together to create the base. I sincerely thank Him (Them) for their work. I felt there needed to be more documentation for rookie users to properly set this up. I had quite a few questions and when I saw a few questions in that chat from people struggling, I wanted to help. I also had a better idea for troubleshooting info.
Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
20010.8K3.0K
🔘
Button Actions
complex
8 inputs

Zigbee2MQTT - ZemiSmart ZM-RM02 Controller - 2024-06-04

This Blueprint uses a Zigbee2MQTT built sensor to sort out the 18 commands from the ZemiSmart ZM-RM02 Remote. The split out of functions gives you the ability to assign local scripts or functions to do the things you want the remote to do. Functions that are left empty will simply do nothing. There is sample code to make the template sensor in the help file on GitHib named Zigbee2MQTT - ZemiSmart ZM-RM02 Controller.md & in the community page related to this. Within this blueprint there is an event handler that will latch the last command that the blueprint finds and sends that to the event buss. From there a simple Template sensor can grab it and show you the last action sent. Thie will help when setting up new functions and to troubleshoot strange behaviours. Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2007.0K3.1K
🔘
Button Actions
medium
3 inputs

Keypad 5 button cypher to turn on something - 2024-06-08

This will accept any 5 button presses or Binary Sensor detections and use them to preform an action. RE open a lock, or whatever. Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2004.6K2.4K
🔘
Button Actions
complex
75 inputs

Deprecated - Aqara Magic Cube Zigbee2MQTT - 2022-12-12

THIS BLUEPRINT IS DEPRECATED & IS NO LONGER SUPPORTED. ### FOR REPLACEMENT SEE: https://github.com/SirGoodenough/HA_Blueprints/blob/master/Automations/Zigbee2MQTT%20-%20Xiaomi%20Cube%20Controller%20MQTT%20Triggered.yaml

entity
action
2004.6K4.7K
🔘
Button Actions
medium
5 inputs

Tasmota EZ-Button for Update and Restart All 2023-08-07

🧿 This will create 3 buttons to help you. 🧿

1:

Press a button to restart ALL Tasmota Devices (Also to use during Home Assistant Restart to get all current State and Sensor readings)

2:

Press a button to update a couple of Tasmota devices to test that the new version will not break something, (Think of these units as your canary's in the coal mine.)

3:

Press a button to update ALL Tasmota devices to the latest version.

🧿 There are 5 Requirements to allow this to work. 🧿

A: ✔️

You need the Home Assistant Tasmota Integration to be functional on your system and HA needs to be able to see and interact with the devices. This Blueprint does not do that for you.

B: ✔️

This script makes the assumption that the default GroupTopic of 'Tasmotas' is available on all your Tasmota Devices. If you have devices that have been upgraded from pre V7 or so, they may be missing this GroupTiopic. If this is the case you will have to add the GroupTopic 'Tasmotas' to your device. 'https://tasmota.github.io/docs/Commands/#control'

C: ✔️

Your Home Assistant Instance needs to be or be communicating with an MQTT Broker. But this is easy because in order to have A: running, MQTT is a requirement for A:.

D: ✔️

Tasmota Devices firmware default MQTT topic is set to: %prefix%/%topic%/ If you did not change the topic in your Tasmota Devices then leave it as the default here as well. The other option available to you is to flip them as I do in my Home Assistant personally.

E: ✔️

Your Tasmota devices need to be updated to the same 'breaking change' generation as the Released version of Tasmota for this to be able to update. Again this is easy because in order to have A: running, Tasmota V9.2 minimum is a requirement for A:. Tasmota has had breaking changes in it's history. Therefore you should never stray from the upgrade path listed in the Tasmota Docs when upgrading. To upgrade your Tasmota firmware, you need to follow the path, or risk bad things happening: v1.0.11 🔀 v3.9.22 🔀 v4.2.0 🔀 v5.14.0 🔀 v6.7.1 🔀 v7.2.0 🔀 v8.5.1 🔀 v9.1 🔀 Current release. That means you currently need to manually update your firmware to v9.1 minimum for these buttons to work going forward. Community link for this blueprint

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
text
select
20010.6K3.8K
🔘
Button Actions
medium
1 inputs

color_control_for_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because I saw others struggling with how so convert cube rotation to light dimming in other places. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code. This script has 1 input to select the relationship between the rotation amount and the speed of the color change. This requires you call this script wth 3 data values. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The second data point is the entity of the light or light group that you are trying to control. The third is to tell the BP id you are controlling the red, the blue, or the green part of the color. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it. Sample call / use of this script with ZHA: yaml - service: script.cube_color_control data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' light: light.grp_studio t_color: red Sample call / use of this script with Z2M: yaml - service: script.cube_color_control data: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' light: light.kitchensink t_color: red

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
number
2005.0K3.4K
🔘
Button Actions
medium
3 inputs

dimmer_control_4_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because I saw others struggling with how so convert cube rotation to light dimming in other places. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code. This script has 2 inputs in the Blueprint screen to set the sensitivity of the rotation action and the minimum bbrightness level for your lights. If the rotation is too sensitive the lights will change from dim to bright in too short of a rotation so make it less sensitive. If the lights flicker at low brightness, raise the minimum brightness level to stop it. The data is sent to the generated script to control the action live at each use. You only need to ececute this blueprint generator script if you wish to change in input values or create another dimmer script. This requires you call this script wth 2 data values. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The other data point is the entity of the light or light group that you are trying to control. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it.

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere. Sample call / use of this script for ZHA:
    - service: script.cube_dimmer_control_bp
      data:
        angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}'
        light: light.grp_studio
    
    Sample call / use of this script for Z2M:
    - service: script.cube_dimmer_control_bp
      data:
        angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}'
        light: light.grp_kitch
    
number
2004.7K1.3K
🔘
Button Actions
simple
0 inputs

long_short_toggle_4_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because I saw others struggling with how so convert cube rotation to actions in other places. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code. This script has no inputs in the Blueprint screen because all the data is added to control the action live at each use. This requires you call this script with a couple of data values. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The other data point is the entity of the device(s) that you are trying o control. Only 1 of the short_entity or long_entity is required 4 this Blueprint to work. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it. Sample call / use of this script with ZHA: yaml - service: script.cube_long_short_toggle data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' short_entity: light.kitchen_down_lights long_entity: light.kitchensink Sample call / use of this script with Z2M: yaml - service: script.cube_long_short_toggle data: angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' short_entity: light.kitchen_down_lights long_entity: light.kitchensink

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2005.1K961
🔘
Button Actions
simple
1 inputs

volume_control_4_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because because of requests to extend the function of my BP's with how to convert cube rotation to volume in other places. Research found me this Post from Petro which had a very elegant solution to the problem, It was very easy decision to adopt it here. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code and provide action data. This script has one !input in the Blueprint screen to set the sensitivity of the rotation to volume changes. 30 seemed about right, but adjust as needed. Because all the data is added to control the action live at each use this is the only !input. This requires you call this generated script wth 2 data values when you want it to run. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The other data point is the entity of the media_player that you are trying to control. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it. Sample call / use of this script for ZHA: yaml - service: script.cube_dimmer_control_bp data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' mp: media_player.farg Sample call / use of this script for Z2M: yaml - service: script.cube_dimmer_control_bp data: angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' mp: media_player.farg

🗿Notice👮🏿‍♂️:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
number
2007.3K964
🔘
Button Actions
complex
18 inputs

🔥 Advanced Heating Control V5

🔥 room based heating / ❄ based on
👥 people presence 🗓️ multiple schedulers 🚶 presence sensor ↔️ proximity aka geo fencing
🥶 frost protection 😡 adjustable aggressive mode 🌤️ activation based on weather, temperature or boolean entities 🎛️ granular schedule adjustments 🪟 multiple window open detection 🎈 party mode 🤝 guest mode ⚔️ liming protection 📍 dynamic valve positioning 🧭 thermostat calibration for the most common devices (Tado, Aqara, Popp / Danfoss / Hive, Tuya) ⚙️ several tweaks for fixing your thermostat issues 🎬 custom action 🤫 calm & 💪 reliable Version: 5.3.4 Help & FAQ: Advanced Heating Control Documentation: panhans.github.io/HomeAssistant/ ko-fi
1353.2K3.3K
🔘
Button Actions
complex
17 inputs

🔥 Advanced Heating Control Dev

🔥 heating / ❄ based on
👥 people presence 🗓️ multiple schedulers 🚶 presence sensor ↔️ proximity aka geo fencing
🥶 frost protection 😡 adjustable aggressive mode 🌤️ activation based on weather, temperature or boolean entities 🎛️ granular schedule adjustments 🪟 multiple window open detection 🎈 party mode 🤝 guest mode ⚔️ liming protection 🧭 thermostat calibration for the most common devices (Tado, Aqara, Popp / Danfoss / Hive, Tuya) ⚙️ several tweaks for fixing your thermostat issues 🎬 custom action 🤫 calm & 💪 reliable Version: 5.0.rc2_2411110937 Help & FAQ: Advanced Heating Control Documentation: work in progress ko-fi
1355.6K4.6K
🔘
Button Actions
complex
11 inputs

Binary Sensor Notification

Send a notification or trigger a custom action depending on the state switch of a binary_sensor
entity
select
number
+3
1351.7K979
🔘
Button Actions
complex
7 inputs

💬 Entity State Notification

💥 New In Version 3

🔃 support for multiple states or nummeric comarision (above/below) 🤯 new logic for better troubleshooting and further development 📱 multiple groups and devices for notifications possible 💥 custom notification action ⏸️ stoppable and pausable periodic notifications

🤙 Features

🎯 monitor entities for a specific state and trigger a notification 📝 modify message, title, icon, color, channel, group etc 🧷 persistent notification until entity leaves specified state 🔄 periodic notification with stop functionality 🎬 custom actions ✅ custom conditions ℹ️ Hints If you want to test this automation, you need to change the state of an observed entity. You can do this in the developer options. Simply filter for your entity, select it and change the state to the trigger state manually. 📖 Documentation: panhans.github.io/HomeAssistant/ ⛑️ Help & FAQ: Entity State Notification 💿 Version: 3.2.3 ko-fi
1354.5K1.9K
🔘
Button Actions
complex
7 inputs

🎬 Scene Based Theatre Mode

Features 🎬 activates scenes depending on media player states and content types 🔁 automatic caching and restoring of the states of the entities of the Playing Scene 🌇 transition time for switching scenes Help & FAQ: Scene based theatre mode Version: 2.1 If you like my work and support feel free to support me. ko-fi
entity
select
number
+1
1355.9K2.9K
🔘
Button Actions
complex
27 inputs

Zone Notification Extended

✉️ notification when a person enters / leaves a zone 🎬 custom action when a person enters /leaves a zone 🎛️ modify your notifications in color, channel, group, ect. 📴 enable / disable notifications easily ❌ custom condition for blocking / allowing notifications 🌎 notification button support to open a url, e.g. shopping list

Hints

If you want to test this automation, you need to change the state of an observed person. you can do this, in the developer options. Simply filter for your person entity, click on it and change the state to a zone used by this automation. Version: 3.5.3 Help & FAQ: Zone Notification Extended If you like my work and support feel free to support me. ko-fi
entity
duration
device
+5
1353.3K4.3K
🔘
Button Actions
medium
6 inputs

Scene Toggle

Features

  • toggle through scenes by order or last activated timestamp
  • define a transition time
  • select scenes by area and/or include/exclude specific scenes
  • timeout for beginning at start if using static order
Help & FAQ: Simple Scene Toggle Version: 3.2 If you like my work and support feel free to support me. ko-fi
area
entity
number
+1
1356.9K2.0K
🔘
Button Actions
complex
38 inputs

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller automation for executing any kind of action triggered by the provided IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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 regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2021.10.26
select
device
entity
+3
1245.7K3.2K
🔘
Button Actions
complex
7 inputs

Inovelli Notification LED (Switch or Dimmer)

An automation which displays a colored pattern on the LED strip on your in-wall Inovelli Switch, Dimmer, or Fan/Switch combo.
entity
text
select
12410.9K2.3K
🔘
Button Actions
complex
14 inputs

Inovelli Red Series LZW31-SN Dimmer (ZWave-JS)

Create automations for the Inovelli Red Series LZW31-SN Dimmer using the ZWave-JS integration.
device
action
1245.4K3.1K
🔘
Button Actions
complex
8 inputs

Zigbee2MQTT - Mijia Wireless Remote Switch (WXKG01LM) actions

Define actions your Xiaomi Mijia Wireless Round Remote Switch using Zigbee2MQTT. For your button entity, choose the right sensor with your button name and the entity id which ends with "_action", e.g. "sensor.kitchen.button_action"
entity
action
12410.6K1.0K
🔘
Button Actions
medium
3 inputs

GE Switch Double Taps

Create automations to react to double taps from supporting GE switches.
device
action
12410.0K2.6K
🔘
Button Actions
complex
25 inputs

Z2M - Aqara Opple switch 3 bands

Aqara Opple switch 3 bands (WXCJKG13LM).
entity
action
1244.3K4.6K
🔘
Button Actions
medium
4 inputs

Aqara Wireless Switch (single, double, hold)

Control anything using Aqara Wireless Switch. Customizable actions for each press. This version of the blueprint is for buttons supporting single, double and hold actions.
entity
action
1242.4K1.2K
🔘
Button Actions
medium
5 inputs

Inovelli LED notification script

A script that displays a notification on an Inovelli dimmer, switch, or fan combo switch.
entity
select
number
1249.1K509
🔘
Button Actions
simple
2 inputs

Voice - Set Reminders - Full LLM script

Image More detailed information can be found here

Set reminders

Prerequisites

  • Createa a ToDo entity to store the reminders in. You can use the button below to start the config flow Open your Home Assistant instance and start setting up a new integration.

Blueprint setup

Required

  • Set a todo entity to be used to store the reminders

Optional

  • Change the prompt settings for the LLM
  • Change or translate the settings for the response given by Assist

Note:

  • Give the script a clear description. This will be used by the LLM to understand it should use this script for the todo list items.
  • Make sure to expose the script to Assist after the script has been saved

Example for script description:

Tool to set reminders based on voice commands. In case not recipient is provided ask for it, in case no clear date and time is provided ask for it, in case no recipient is provided ask for it

Usage

You can request for a reminder to be set. The LLM will ask you for missing data.

Examples

Set a reminder to take out the trash
Remind me to buy flowers for my partner
Make sure I do not forget to buy a gift for Mothers day
831.4K3.8K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 1 Button Remote - Custom Actions

This automation simulates the use of the IKEA TRADFRI SHORTCUT Button connected through ZHA.
device
action
612.4K2.7K
🔘
Button Actions
simple
2 inputs

ZHA - IKEA TRADFRI - 1 Button Remote - OnOff

This automation simulates the use of the IKEA TRADFRI SHORTCUT Button connected through ZHA.
device
entity
618.0K572
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 1 Button Remote - Color Preset

This automation simulates the use of the IKEA TRADFRI SHORTCUT Button connected through ZHA.
device
entity
611.1K2.6K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 1 Button Remote - Scenes

This automation simulates the use of the IKEA TRADFRI SHORTCUT Button connected through ZHA.
device
entity
6110.3K3.7K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 2 Button Remote - OnOff and Brightness

This automation simulates the use of the IKEA TRADFRI on/off switch connected through ZHA.
device
entity
number
611.3K244
🔘
Button Actions
medium
5 inputs

ZHA - IKEA TRADFRI - 2 Button Remote - Custom Actions

This automation simulates the use of the IKEA TRADFRI on/off switch connected through ZHA.
device
action
613.9K1.7K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 2 Button Remote - OnOff and Temperature

This automation simulates the use of the IKEA TRADFRI on/off switch connected through ZHA.
device
entity
number
6110.1K378
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Color Lights

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
entity
number
612.3K4.6K
🔘
Button Actions
complex
11 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Custom Actions

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
action
614.2K966
🔘
Button Actions
medium
4 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Custom Preset

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
entity
number
6110.5K5.0K
🔘
Button Actions
medium
4 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Preset Colors

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
entity
number
611.7K3.8K
🔘
Button Actions
medium
4 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Preset Color Temperature

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
entity
number
613.8K1.2K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 5 Button Remote - Warm White Lights

This automation simulates the use of the IKEA TRADFRI remote control connected through ZHA.
device
entity
number
613.7K427
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - STYRBAR - Color Lights

This automation simulates the use of the IKEA TRADFRI STYRBAR remote control connected through ZHA.
device
entity
number
6110.5K2.9K
🔘
Button Actions
medium
4 inputs

ZHA - IKEA TRADFRI - STYRBAR - Custom Preset

This automation simulates the use of the IKEA TRADFRI STYRBAR remote control connected through ZHA.
device
entity
number
613.5K3.5K
🔘
Button Actions
medium
4 inputs

ZHA - IKEA TRADFRI - STYRBAR - Preset Colors

This automation simulates the use of the IKEA TRADFRI STYRBAR remote control connected through ZHA.
device
entity
number
611.2K4.8K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - STYRBAR - Warm White Lights

This automation simulates the use of the IKEA TRADFRI STYRBAR remote control connected through ZHA.
device
entity
number
618.8K2.8K
🔘
Button Actions
simple
2 inputs

ZHA - Aqara Vibration - Set Sensitivity

Set the sensitivity for the Aqara Vibration sensor. Press the button on the sensor immediately after you run the script, to make sure the sensor is awake, to receive the command.
device
select
615.5K4.4K
🔘
Button Actions
complex
13 inputs

Appliance Notifications & Actions

📳 Appliance Notifications & Actions

Version: 3.7 🤔 Watts your appliance up to, you're always in the know from start to finish! 🛎️🔌💸 If you like my blueprints, and would like to show your support or just say thank you? Click Here 🙂 <details> <summary><b>The Automation Process:</b> 👈</summary>
  • Appliance Trigger:
    • Enter the power sensor entity that measures the live current draw of the appliance. Common devices with these sensors include smart plugs, energy meters, etc.
    • The automation is triggered when the appliance's current draw exceeds a set wattage.
    • The automation ends when the appliance's current draw falls below a set value.
  • Notification Options:
    • Send notification messages to one or multiple devices when the appliance starts, finishes or the watchdog is triggered.
    • Your end message can also include estimates of total power consumption and cost.
    • Include duration tracking in your end message to track the appliance's operational time for the task or cycle.
    • Opt to sends a repeated notifications to remind you when the appliance cycle is complete.
    • Limit when notifications can be sent by using Notify Time Restrictions - helpful for avoiding alerts while you're asleep.
    • Notifications are compatible with both Apple iOS and Android devices, ensuring universal accessibility.
  • Run Status:
    • Display your appliance's run status on your dashboard.
  • Notify Time Restrictions:
    • Restrict notifications to the specified start and end times on the selected days. Notifications outside this time range will be skipped.
  • Energy Tracking:
    • Use energy tracking to estimate the total energy usage (kWh) for each completed cycle. You can also choose to include the estimated cost of that cycle in the end notification.
    • Or simply update the start and end helpers without including any energy information in the end notification - useful for your own custom actions or other Home Assistant logic.
    ⚠️ Disclaimer - These values are estimates and should only be used as a guide. Please avoid relying solely on these estimates for accuracy and use them at your own risk. We cannot be held responsible for any inaccuracies or resulting losses, damages, inconvenience, or anything else that may occur.
  • Time Tracking:
    • Runtime Tracking - Records the total runtime of your appliance by updating a text helper each time it completes a full cycle.
    • Duration Tracking - Tracks how long the appliance was running during each individual cycle and includes this duration in the end notification message.
  • Cycle Counter:
    • Use the cycle counter to track the total number of cycles completed by your appliance. You can also choose to include this information in your end message.
  • Service Reminders:
    • Service reminders help you track appliance usage and perform timely maintenance.
    • Cycle-Based Reminder - Notifies you when a service is due based on the number of cycles completed.
    • Time-Based Reminder - Notifies you when a service is due based on the total time the appliance has been in use since the last service.
  • Watchdog:
    • The watchdog option monitors an appliance cycle completion.
    • It sends a notification if a cycle completion fails within the specified time frame.
  • Device Tracker:
    • You can choose to use the device tracker for Start, End, and Watchdog notifications.
    • When enabled, only selected devices currently inside the chosen zone will receive those notifications.
  • Custom Actions:
    • Tailor custom actions to suit your preferences and needs, enhancing the automation's functionality.
    • Configure actions such as triggering announcements on platforms like The Voice (HA), Google, Alexa, etc., to keep you informed about appliance events.
  • Custom Conditions:
    • Enter any custom conditions to further customize the automation process.
</details> Need help? Required = *
233.8K4.5K
🔘
Button Actions
complex
9 inputs

Bathroom Humidity Exhaust Fan

🚿 Bathroom Humidity Exhaust Fan

Version: 2.6 Step into the future of freshness - customize it your way and experience the convenience of automated humidity control! 🌿🚿 If you like my blueprints, and would like to show your support or just say thank you? Click Here 🙂 <details> <summary><b>The Automation Process:</b> 👈</summary>
  • Auto Trigger:
    • When the derivative percentage rises above a set value, the fan turns ON
    • When the derivative percentage falls below a set value, the automation waits for a time delay and then turns the fan OFF.
    • Optional - Set a maximum humidity percentage to trigger the fan ON. This is useful when having back-to-back showers.
    Note: You must have a humidity sensor in the bathroom and set up a 'Derivative Helper' for this automation to work.
  • Manual Trigger Option:
    • This feature allows you to manually trigger the automation.
  • Multi-Speed Fan Control Option:
    • You have the option to use fan speeds to control the staging of your fan.
    • You can choose to stage your fan in your preferred configuration, such as High/Off, High/Low, High/Low/Off, High/Med/Low, etc.
  • Winter Mode Option:
    • You have the option to use 'Winter Mode.' This mode allows for different settings to be applied, accommodating the typically higher humidity levels experienced in winter compared to summer.
  • Light Control Option:
    • Use the "Light Control" option to turn ON lights, adjusting brightness levels, colour temperatures, and transition times.
    • This feature is commonly utilized with LED lights in a shower niche.
    • For expanded lighting options, consider integrating my 💡Sensor Light blueprint, which utilizes the automation link feature.
  • Manual Control Option:
    • Use a manual fan switch to toggle the fan ON/OFF.
    • Opt to use the auto-OFF option for timer-like functionality.
    • This is particularly useful for removing unwanted fumes from deodorant, hairspray, or the toilet.
  • Automation Link Option:
    • This feature simplifies the process of automatically disabling your other automations by providing an automation linking mechanism.
  • Bypass Functionality Option:
    • This allows you to bypass the automation, offering manual control and additional customization capabilities.
  • Safety Measures:
    • Set a maximum runtime safeguard for the fan to prevent continuous operation.
    • Benefit from built-in safeguards to ensure smooth operation and reliability, even if Home Assistant restarts.
  • Blueprint Add-On Integration:
    • Sensor Light: Control your lights in the bathroom. Click Here to learn more.
    • Toilet Exhaust Fan: Integrate with a toilet in the bathroom. Click Here to learn more.
</details> Need help? Required = *
232.5K2.0K
🔘
Button Actions
complex
13 inputs

Sensor Light

💡 Sensor Light

Version: 8.0 Your lighting experience, your way - take control and customize it to perfection! 💡✨ If you like my blueprints, and would like to show your support or just say thank you? Click Here 🙂 <details> <summary><b>The Automation Process:</b> 👈</summary>
  • Trigger:
    • You can choose any binary sensors or schedules to trigger the automation.
    • A trigger sensor, such as a Motion Sensor, will activate lights, switches, scenes, and scripts when the automation is triggered.
    • A time delay begins the turning OFF process after all triggers are clear. See grouping sensors for more information.
    • If triggers are activated again before the time delay ends, the automation resets for continuous lighting.
  • Scene and Script Integration:
    • Scenes or scripts offer additional customization for your spaces.
  • Light Control Options:
    • Utilize "Light Control" to adjust brightness, colour temperature, colour, and transition times.
  • Dynamic Lighting Options:
    • Opt for 'Dynamic Lighting' to automatically adjust brightness based on lux values, and/or adjust brightness and colour temperature according to the sun's position or the time of day.
    • Opt to use the 'State Control Option,' allowing you to toggle between dynamic lighting and normal lighting based on the entity's activation state.
  • Manual Override:
    • Use "Bypass Options" for manual bypassing of trigger sensors, providing manual control and additional customization.
  • Sun Elevation Options:
    • Implement "Sun Elevation" to restrict automation to darker conditions aligned with the sun's position.
  • Ambient Light Sensing Options:
    • Set up an Ambient Light Sensor for activation in low-light conditions, customizable with specified LUX values.
  • Time-Based Options:
    • Specify precise start and end times along with weekday selections to define when the automation should run.
  • Device Tracker Options:
    • Utilize "Device Tracker" to activate automation when home or within specified zones, preventing unnecessary activations. This feature is particularly useful to prevent unnecessary lighting activations when pets trigger sensors while no one is home.
  • Night Lights Mode:
    • Enable "Night Lights" for softer illumination during night time activities, automatically enabled based on conditions.
    • Opt to use "Night Glow". This feature activates a low-level light when no trigger is detected, creating a subtle ambient glow perfect for nighttime use.
  • HA Restart Safeguards:
    • Benefit from built-in safeguards for Home Assistant restarts.
  • Blueprint Add-On Integration:
    • Sensor Light Add-On - Enhances media control automation. Click Here to learn more.
    • Bathroom Humidity Exhaust Fan - Keeps the lights ON when showering. Click Here to learn more.
</details> Need help? Required = *
2310.0K3.4K
🔘
Button Actions
complex
38 inputs

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

Controller automation for executing any kind of action triggered by the provided IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote. Allows to optionally loop an action on a button long press. Supports deCONZ, ZHA, Zigbee2MQTT. 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 regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2025.01.03
select
device
entity
+3
236.4K4.5K
🔘
Button Actions
complex
15 inputs

Zooz ZEN27

Automations helper for the Zooz ZEN27 S2 Dimmer Switch using the Zwave JS integration.
device
action
2310.4K3.6K
🔘
Button Actions
complex
8 inputs

Automatic Gate

Automatic Gate ⛩️

Description 📝

Modular and secure gate automation that opens your gate upon leaving or arriving Makes managing your gate while driving easier : don't ever touch your screen or remote again Have your gate greet you when you arrive home and be ready for you Customize the options to tailor the system to your exact needs

Key Features 🌟

  • Automatic Opening: Your gate will open automatically when you drive home. No need to press any buttons ! 🏠
  • Smart Navigation: Directly open the gate when leaving home, or launch an itinerary when starting from outside 🚀
  • Multi-User Support: Manages up to 10 drivers simultaneously 🚗
  • Collision Prevention: Ensures the gate doesn't close on anyone arriving or leaving at the same time 🚧
  • Security & Reliability:
    • Precise Waze and ETA calculations to have your gate fully open exactly when you arrive home 🎯
    • Real-time position tracking to adjust timing for traffic or if you pass by without entering 📍
    • Car status monitoring to cancel everything if you leave your car ✋
    • Built-in timeouts in case of an internet loss ⏳
    • Maximum entry and leaving time before auto-closing ⌛
    • Notification alerts at each decision of the automation 🚨
    • Manual actions prioritized over the automation, letting you control your gate even while the automation is running ✍️
  • Customizable Settings:
    • Auto-close with iBeacon 📡
    • Adjustable notifications 💬
    • Customizable security options 🔒
    • Customizable gate operation timings 🛠️
    • Customizable travel time refresh rate 🔁
    • Multiple gates supported by reusing the blueprint ♻️

More info ℹ️

232.0K1.6K
🔘
Button Actions
medium
4 inputs

Itinerary tracker notification

Itinerary tracker notification 📍

Description 📝

A blueprint that notifies all selected users when another one is driving home

Key Features 🌟

  • Companion app notifications 🔔
  • Travel time and ETA notification updates 🔁
  • On notification tap custom link 👆
  • Speakers TTS support 🔊
  • Adjustable notifications 💬

More info ℹ️

238.6K1.2K
🔘
Button Actions
complex
16 inputs

Inovelli Red Series LZW30-SN Switch (ZWave-JS)

Create automations for the Inovelli Red Series LZW30-SN Switch using the ZWave-JS integration.
device
action
238.0K4.0K
🔘
Button Actions
complex
22 inputs

Z2M - Inovelli 2-in-1 switch + dimmer Scene Controls

For Inovelli Blue Series 2-in-1 switch + dimmer, model VZM31-SN Allows setting a few different actions such as 2,3,4,5 clicking the up/down and config buttons.
entity
action
236.6K3.7K
🔘
Button Actions
medium
1 inputs

Inovelli Blue LED (Zigbee2MQTT)

Set LED effects for Inovelli Blue Series Switches using Zigbee2MQTT. ℹ️ Version: 2025.8.0 To update this blueprint, read Re-importing a blueprint ✨ Features:
  • Select one or multiple devices, entities, floors, labels, or areas with Inovelli switches
  • Selectors for LED Number, Color, Brightness Level, Effect, and Duration
  • LED Number, Color, Effect, and Duration can accept direct values or the “friendly name” listed in the dropdown
  • Debug info to diagnose issues
    • Warning: Debug mode will create a persistent message for every entity called in the script plus 1
✅ Supported Models:
  • Inovelli Blue Series On/Off Switch (VZM30-SN)
  • Inovelli 2-in-1 switch + dimmer (VZM31-SN)
  • Inovelli mmWave Zigbee Dimmer (VZM32-SN)
  • Inovelli Fan Controller (VZM35-SN)
💬 Forum: https://community.home-assistant.io/t/z2m-inovelli-blue-series-switch-led-notification-script-vzm31-sn-vzm35-sn/489620 📜 GitHub: https://github.com/zanix/home-assistant-blueprints

Using this Blueprint

See Using the Script in the forum topic.
The main idea is you set the LED values when you call the script, the inputs below are for default values.
235.4K604
🔘
Button Actions
complex
9 inputs

Contextual Pico Media Remote

This blueprint creates an automation allowing a Lutron Caseta 5 button Pico remote to contextually control music or an Xbox. It assumes Sonos speakers are being used, and the same speakers are used for both music and the Xbox. In my configuration I have an Xbox attached to a TV that has Sonos speakers attached via an HDMI Arc/eArc channel. <br> <br> When the Xbox is on, the remote's on (top) and off (bottom) buttons map to the Xbox A and B buttons respectively. This is great, particularly in media apps, since A is used to select, play or pause while B is used to stop or go back. <br> <br> When the Xbox is not powered, on (top) is mapped to playing / pausing music and off (bottom) is mapped to going to the next music track. <br> <br> For both Xbox and music playback the raise (up arrow) button increases speaker volume and lower (down arrow) button decreases speaker volume. While favourite / stop (round middle) button is configurable.
device
entity
target
+5
2110.6K4.7K
🔘
Button Actions
complex
13 inputs

Sonos Sleep / Alarm Handler

This blueprint creates an automation that listens for a button press on a Lutron Caseta Pico remote and depending on the time of day does different things. If pressed during the Wake Phase it will disable the current or upcoming alarm on a Sonos speaker disable, and execute an optional action. If pressed during the Sleep Phase, it executes an optional action, annouce when the next alarm is set to run, and ends with some optional sleep music.
entity
device
text
+4
215.7K1.0K
🔘
Button Actions
simple
2 inputs

Automatic Timed Turn Off

This simple blueprint is used to create an automation that will automatically turn off the specified switch after a given time period whenever the specified switch is turned on.
entity
duration
218.4K4.1K
🔘
Button Actions
complex
14 inputs

Send actionable notifications for Android

Send actionable notifications to an Android device For each action, you can open an URL, an application on the device or load a lovelace view/dashboard. If you plan to use a lovelace view the format would be /lovelace/test where test is replaced by your defined path in the defined view. If you plan to use a lovelace dashboard the format would be /lovelace-dashboard/view where /lovelace-dashboard/ is replaced by your defined dashboard URL and view is replaced by the defined path within that dashboard. To pick the application to open, prefix app:// to the the package name. If the device does not have the application installed then the Home Assistant application will open to the default page. If you define an action and an URI for a button, URI will take precedence over action.
device
entity
boolean
+1
176.2K1.7K
🔘
Button Actions
medium
4 inputs

Aqara Zigbee Button

Setup actions for three functions of the Aqara Zigbee button with Press, Double Press, and Hold.
device
action
173.3K407
🔘
Button Actions
complex
11 inputs

Turn on based on motion

Turn on a light, switch, scene, script or group based on motion detection, and low light level. Required entities:
  • Motion sensor (single sensor or group)
  • Target entity (light, switch, scene or script)
Optional features:
  • You can set a cutoff entity of which the value determines whether the illuminance level is low and the automation needs to trigger.
  • You can define a blocking entity, which blocks the automation from running when this entity's state is on.
  • You van define a turn-off blocking entity, which blocks the entity from turning off after the set delay.
  • Time limits can also be defined to limit the time before and after the automation should trigger.
  • If you want the entity to turn off after a certain amount of seconds, you can use the Wait Time input.
  • If you want another entity than the target_entity to turn off after the delay, you can define a separate Turn-off entity.
  • If you do not enable the optional entities the automation will skip these conditions.
entity
number
action
178.6K4.8K
🔘
Button Actions
complex
7 inputs

Philips Tap Dial Switch

Control lights with a Philips Hue Tap Switch. Use the four buttons to control up to four light(s) with an on/off toggle. The dial can be used to dim the most recently used light.
device
target
entity
+1
177.7K4.9K
🔘
Button Actions
complex
9 inputs

Philips Dimmer Remote

Control lights with a Philips Hue Dimmer Switch. The top "on" button will turn the lights on to the last set brightness (unless the force brightness is toggled on in the blueprint). Dim up/down buttons will change the brightness smoothly and can be pressed and hold until the brightness is satisfactory. The bottom "off" button will turn the lights off. If defined it will optionally control up to 5 different sets of lights using the double through quintuple press options. Whichever light was turned on last will be controlled by the dimmer buttons.
device
target
boolean
+2
174.1K3.4K
🔘
Button Actions
medium
5 inputs

Sonoff Zigbee Button

Setup actions for three functions of the SONOFF Zigbee button with Press, Double Press, and Hold.
device
select
action
177.1K2.5K
🔘
Button Actions
medium
1 inputs

Inovelli Blue LED (Zigbee2MQTT)

Set LED effects for Inovelli Blue Series Switches using Zigbee2MQTT. ℹ️ Version: 2025.8.0 To update this blueprint, read Re-importing a blueprint ✨ Features:
  • Select one or multiple devices, entities, floors, labels, or areas with Inovelli switches
  • Selectors for LED Number, Color, Brightness Level, Effect, and Duration
  • LED Number, Color, Effect, and Duration can accept direct values or the “friendly name” listed in the dropdown
  • Debug info to diagnose issues
    • Warning: Debug mode will create a persistent message for every entity called in the script plus 1
✅ Supported Models:
  • Inovelli Blue Series On/Off Switch (VZM30-SN)
  • Inovelli 2-in-1 switch + dimmer (VZM31-SN)
  • Inovelli mmWave Zigbee Dimmer (VZM32-SN)
  • Inovelli Fan Controller (VZM35-SN)
💬 Forum: https://community.home-assistant.io/t/z2m-inovelli-blue-series-switch-led-notification-script-vzm31-sn-vzm35-sn/489620 📜 GitHub: https://github.com/zanix/home-assistant-blueprints

Using this Blueprint

See Using the Script in the forum topic.
The main idea is you set the LED values when you call the script, the inputs below are for default values.
1010.9K4.6K
🔘
Button Actions
medium
2 inputs

Always On

Always keep on a switch. If it is turned off, then turn it back on.
entity
duration
25.1K2.1K
🔘
Button Actions
medium
3 inputs

ZHA - IKEA TRADFRI - 2 Button Remote - On/Off and Brightness

Simulate IKEA TRADFRI 2 button remote connected through ZHA.
device
entity
number
22.8K1.1K
🔘
Button Actions
complex
8 inputs

Calendar Notifications & Actions

📅 Calendar Notifications & Actions

Version: 1.9 Transform Your Calendar: Turn Events Into Notifications and Actions! 📅🔔⚙️ If you like my blueprints, and would like to show your support or just say thank you? Click Here 🙂 <details> <summary><b>The Automation Process:</b> 👈</summary>
  • Calendar Event Triggering:
    • Trigger based on a keyword in a calendar event or on all events in a selected calendar.
    • Choose to trigger at the start or end of a calendar event with time offsets.
  • Notification Options:
    • Option to send notifications to one or multiple devices when triggered.
    • Action Buttons (Optional):
      • Notifications can include up to 3 action buttons.
      • Each action button is linked to a designated custom action group.
      • Option to send a confirmation message when an action button is pressed.
      • The automation will continue after a specified time delay if an action button is not pressed.
    • Compatible with Apple iOS and Android devices.
  • Custom Actions:
    • Option to define up to 3 different action groups when triggered.
    • Each action group can contain as many actions as desired.
    • Each action group can be linked to a notification action button or executed automatically when the automation is triggered.
</details> Need help? Required = *
010.5K1.1K
🔘
Button Actions
complex
35 inputs

AWTRIX Weather ⛈️ + Forecast + 🌕️ (Service Calls)

This is somewhat of a mega-weather blueprint with moon phase support. However for it work correctly you will need a variety of different things setup. It was initially designed to use in partnership with a personal weather station however it seems to work fine with OpenWeather as well or any other provider that offers an hourly forecast. AWTRIX Weather ⛈️ + Forecast + 🌕️ (Service Calls) screenshot AWTRIX Weather ⛈️ + Forecast + 🌕️ (Service Calls) screenshot This blueprint will publish to two separate topics. jeef_weather for the weather report and jeef_weather_sun if its near sunrise/set

⚠️ REQUIREMENTS ⚠️

For this blueprint to work you MUST have a few things pre-setup.

Moon Integration 🌕️

 .------.
( I MOON )    ..
 `------'   .' /
      O    /  ;
        o i  OO
         C    `-.  Make sure you've
         |    <-'      enabled
         (  ,--.   the MOON Sensor
          V  \_)
           \  :
            `._\.
The moon integration is required. You can add it via the moon page or just by clicking here

Moon Rise/Set Sensor 🌕️ ⏲️

      M
     (X)
    // \\   Lets use a GeoLocation to find
   //   \\     out the Moon Rise / Set
  //     \\       TIMES
 //       \\
/           \
As Home Assistant doesn't currently provide moon rise/set times you will need to get this from some api. You can use the ipgeolocation API. To do so you will need to create an account and extract your API_KEY. Additionally you need your LAT and LON. Then you can add a REST sensor to your configuraiton.yaml file like the one here:
resource: https://api.ipgeolocation.io/astronomy?lat=<LAT>&long=<LON>&apiKey=<API_KEY>
name: ip_geo_location
scan_interval: 300
value_template: "OK"
json_attributes:
  - moonrise
  - moonset
  - moon_altitude

Icons

You can call my custom script which will prompt you for an Awtrix device and then upload the required icons: (If you have windows I don't know if this will work)
bash -c "$(curl -fsSL https://raw.githubusercontent.com/jeeftor/HomeAssistant/master/icons/upload_icon.sh)"
This blueprint ~will~ may be updated as new features AWTRIX Weather ⛈️ + Forecast + 🌕️ (Service Calls) screenshot https://raw.githubusercontent.com/jeeftor/HomeAssistant/master/blueprints/automation/awtrix_weatherflow.yaml
device
entity
number
+3
07.4K1.2K