šŸŽ›ļø

Device Control

Blueprints for controlling various devices

41 blueprints found

šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
82.5K1.3K2.7K
by home-assistanthome-assistant/core
šŸŽ›ļø
Device Control
medium
3 inputs

Example Automation Blueprint

A description for the blueprint Version: yyyy.mm.dd
entity
device
1.2K3.1K3.2K
šŸŽ›ļø
Device Control
medium
5 inputs

On-Off schedule with state persistence

On-Off schedule with state persistence

A simple on-off schedule, with the addition of state persistence across disruptive events, making sure the target device is always in the expected state. šŸ“• Full documentation regarding this blueprint is available here. šŸš€ This blueprint is part of the Awesome HA Blueprints project. ā„¹ļø Version 2021.10.26
target
time
text
+1
1.2K10.4K1.5K
šŸŽ›ļø
Device Control
complex
15 inputs

Simple Safe Scheduler

Simple Safe Scheduler

Scheduling a periodic action in Home Assistant might be trickier than what it looks at first glance. Not only the available automation triggers are limited to only time-based schedules (requiring the user to either use template triggers or install additional integrations for more complex scheduling options), but they also do not guarantee that the automation is executed at the provided time. As an example, let's assume automation A is scheduled to run at 12:00. If the Home Assistant server goes down at 11:59 due to a disruptive event (e.g. power outage, planned maintenance, hardware failure etc.) and comes back up at 12:01, the A automation run scheduled for 12:00 would simply be skipped, without any warning to the user. The Simple Safe Scheduler blueprint tries to mitigate scheduling limitations in Home Assistant by providing an easy interface to configure periodic actions, with built-in safety checks to ensure the action actually runs even in case of a disruptive event. The configured automation acts as a simple scheduler, allowing to flexibly program any kind of action based on the following parameters:
  • Time of the day (dynamically provided as an input_datetime entity);
  • Day of the week (multiple days can be selected);
  • Week frequency (allowing to schedule the action to run i.e. every 2 weeks).
In addition, the blueprint implements useful checks to make sure that, in case of a disruptive event (e.g power outage, Home Assistant server outage etc.) happening at the scheduled automation run time, the action is executed as soon as the system restores its state. These checks can be configured to be performed both when Home Assistant boots up and when a custom event is fired (e.g. from another automation or integration). Such safety checks might be particularly important for critical automations, which need to run as close as possible to the scheduled time (e.g. watering plants, configuring an alarm system, etc.). šŸ“• Full documentation regarding this blueprint is available here. šŸš€ This blueprint is part of the Awesome HA Blueprints project. ā„¹ļø Version 2021.10.22
action
entity
number
+2
1.2K10.7K1.3K
šŸŽ›ļø
Device Control
medium
5 inputs

Wake-up light alarm with sunrise effect

A wake-up light alarm with a brightness and color temperature sunrise effect using an existing timestamp sensor as source. Requires date_time_iso sensor in configuration!
entity
number
action
5277.3K1.8K
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
5279.6K3.5K
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
2733.0K4.7K
šŸŽ›ļø
Device Control
medium
3 inputs

Auto_Fan_Temperature_Control_for_3-Speed_Fan_HA_fan-2024-06-04

This sets the fan speed for a 3 speed fan (such as an IFAN03/IFAN04) based on a room temperature. In fact any fan with 3 speeds that is connected to the HA Fan Integration will work with this blueprint. NOTE: See the Sister Blueprint if you want to create an automation using MQTT. if you want to control this fan using the Home Assistant Fan Integration instead. There are action selectors for both the cycle loop and the shutdown loop for adding control of heating / cooling sources, or anything else you want Home Assistant to do for you. 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.9K1.6K
šŸŽ›ļø
Device Control
medium
3 inputs

Auto_Fan_Temperature_Control_for_3-Speed_Fan_MQTT-2024-06-04

This sets the fan speed for a 3 speed fan (such as an IFAN03/IFAN04) based on a room temperature. In fact any fan with 3 speeds designated in MQTT [as 0,1,2,3) will work with this blueprint. NOTE: See the Sister Blueprint if you want to create a blueprint using the Home AssistantFan Entity. There are action selectors for both the cycle loop and the shutdown loop for adding control of heating / cooling sources, or anything else you want Home Assistant to do for you. 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.
2003.0K954
šŸŽ›ļø
Device Control
complex
13 inputs

Octoprint_Discovery_Helper - 2023-03-14

This is Blueprint is provided as a helper for people using the Octoprint Plugin called OctoPrint-HomeAssistant. Within that Plugin there are several suggested Home Assistant Scripts & automations, and this will build them all for you. šŸ“© There is not an official version control system for Blueprints. However I have found something that comes pretty close. It is not perfect, but for MOST Blueprints, it does just fine. I encourage you to check this script out and use it to easily check if I have updated this blueprint. šŸ”— koter84 Blueprint Update Script Community link for this blueprint
text
entity
2009.9K1.7K
šŸŽ›ļø
Device Control
medium
3 inputs

Throttle-your-water-flow-tasmota-2024-06-08

This sets the amount of water sent to your Humidifier. You provide a minimum time and maximum time you want the water to run and this will send a time to the tasmota device controlling the water flow proportional to the ratio of the current humidity VS the target humidity. HA is using the Generic Hygrostat integration. My hardware is a Tasmota Sonoff SV sending the 24v to my humidifier water valve.

Tasmota Rules:

rule1 on Time#Minute|2 do var1 %var2% endon rule2 on system#boot do backlog power2 0; var2 20 endon on POWER2#state=0 do backlog power1 0; rule1 0 endon on POWER2#state=1 do rule1 1 endon rule3 on var1#state>110 do backlog power1 on;delay 1200;power1 off break on var1#state>100 do backlog power1 on;delay 1100;power1 off break on var1#state>90 do backlog power1 on;delay 1000;power1 off break on var1#state>80 do backlog power1 on;delay 900;power1 off break on var1#state>70 do backlog power1 on;delay 800;power1 off break on var1#state>60 do backlog power1 on;delay 700;power1 off break on var1#state>50 do backlog power1 on;delay 600;power1 off break on var1#state>40 do backlog power1 on;delay 500;power1 off break on var1#state>30 do backlog power1 on;delay 400;power1 off break on var1#state>20 do backlog power1 on;delay 300;power1 off break on var1#state<=20 do backlog power1 on;delay 200;power1 off endon 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.5K117
šŸŽ›ļø
Device Control
medium
3 inputs

State 1 temperature ramp control-2024-06-08

This ramps up the thermostat just enough at a time to keep your stage 2 (or emergency) heat from activating. This is meant to be run for instance in the morning when the system is recovering from overnight thermostat set-back, and you don't want it to kick in the stage 2 expensive heat source. There is an optional facility to disable this based on zone occupancy. Also there is a roll-your-own condition statement for things I haven't thought of. 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.
2003.5K2.2K
šŸŽ›ļø
Device Control
medium
3 inputs

Door open tts.cloud_say and Piper announcer (Uses Piper Addon OR Nabu-Casa Cloud) - 2024-06-08

This uses tts.cloud_say from Nabu-Casa or Wyoming with the Piper Addon to tell you a door is open too long and a door has been closed. 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.
2008.0K3.2K
šŸŽ›ļø
Device Control
medium
8 inputs

Broadlink_ON_script_2023-08-07

A script that gets my TV on and Reciever set-up to correct mode. 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.
entity
number
2006.3K137
šŸŽ›ļø
Device Control
simple
3 inputs

Media Player Script Blueprint 2023-12-09

This provides a way to play canned media files with the big long list of YAML entries but keep the main script or automation clean. All that is required there would be a simple line like:
'- service: script.media_player_doorbell_sound'
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.
entity
text
2006.7K2.7K
šŸŽ›ļø
Device Control
complex
11 inputs

TTS_say_Message-2024-06-08

šŸ“£ This is a script that can use any of the 11 integrated TTS Platforms in Home Assistant to send a message to a media player. Some will require Google Type Speakers, some will require Non-Google type speakers. These integrations are listed here. Please refer to these pages for care and feeding of the *tts_say method you choose. ⛓ https://www.home-assistant.io/integrations/#text-to-speech This blueprint WILL NOT set-up TTS for you. You will be given the opportunity to add the incorrect options that will NOT allow your TTS to function. Your best road to success will be to add a TTS session with UI, and only after that is successfully talking to you should you take the languages and options that work there and apply them in this Blueprint. The safest thing to do other than that is to start with the basic sonfiguration for the TTS_say integration that you are using and add options one at a time. The very basic requirements are for you to provide the *tts_say method that you have installed and tested, the entity that you want to send it to, and the message you want to send. Beyond that likely involves trial and error that may best be done in the Developer Tools Services area here: Open your Home Assistant instance and show your service developer tools. I have added an action statement both before and after the main TTS call. You can choose to ignore these, or you can use them to change volume, add a media player to play a doorbell, turn on a light, add a delay, whatever you want to do. The Scripts produced by this blueprint can be called from an automation & variable values for the message and the media_player can be sent on the fly. For details check out the instructions here.

āš ļø This Blueprint makes the assumption that you already have a tested & proven TTS integration installed and you know how it works and how to use it āš ļø

You will need to verify that the name you have given to the TTS integration in your system configuration is the Default name or you need to change this blueprint to use the custom name you have set in the tts: section of configuration.yaml. This will be a way to streamline your automations and scripts. It provides specific services that can be called with a single line service call. This is contrasted to the multiline service calls of repeating values spread throughout your configuration. In addition it puts all your TTS specific code in 1 spot, the blueprint, and that allows it to be called over and over. Plus it gives you one place, the blueprint, to repair issues should they arrise. šŸ”š 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.2K3.0K
šŸŽ›ļø
Device Control
complex
10 inputs

Intelligent Vacuum Cleaning

This script starts a cleaning process of a vacuum cleaner robot depending on a device and its status. For this, the device must remain in a defined status for a certain time. Furthermore, a time period can be defined in which the process can start and the status must be fulfilled. In addition, an air cleaner can be defined for the cleaning process.
entity
number
boolean
1355.1K2.9K
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
1241.5K1.3K
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
812.4K2.5K
šŸŽ›ļø
Device Control
simple
2 inputs

Sync a light with a binary sensor

This automation keeps a light in sync with a binary sensor.
entity
619.4K1.3K
šŸŽ›ļø
Device Control
simple
2 inputs

Toggle a light with a binary sensor

This automation takes a binary_sensor to toggle a light.
entity
616.5K414
šŸŽ›ļø
Device Control
simple
3 inputs

Turn off lights on no motion

This automation turns off the lights after a certain period of motion inactivity.
target
entity
number
614.8K2.1K
šŸŽ›ļø
Device Control
medium
4 inputs

Lightsaver

Turn off the lights in a room when unnecessary. Requires the sun integration.
entity
number
614.1K2.3K
šŸŽ›ļø
Device Control
medium
2 inputs

Set a volume limit for any Media Player entity.

This automation lowers the volume if it exceeds the allowed limit.
entity
number
6110.2K5.0K
šŸŽ›ļø
Device Control
medium
3 inputs

Party Lights!

Party Lights!
entity
number
618.6K2.9K
šŸŽ›ļø
Device Control
simple
0 inputs

Announce Sonos Alarm

This blueprint is used to add a script that will announce when the next alarm is set on the specified Sonos speaker. If the alarm is less than two hours away it will indicate how long until it rings. Otherwise the alarm will indicate the time when the alarm is set using a 12 hour format (e.g. 1 AM vs 1 PM). If it cannot find an alarm it will indicate that as well. The script will gracefully handle when speakers are in groups, and restore playing music after it announces the alarm. This is helpful as part of an automation when going to bed so you don't need to use a phone app to see when/if an alarm is set. I recommend setting the mode to parallel if you will use this script on more than one speaker.
218.5K2.4K
šŸŽ›ļø
Device Control
simple
0 inputs

Play Media

This blueprint is used to add a script for playing media. The script plays the media specified and provides shuffle, repeat and volume options. If you have a multi-room setup (e.g. Sonos) additional media players can be specified. The players will be grouped together with the primary media player.
216.0K4.4K
šŸŽ›ļø
Device Control
simple
0 inputs

Play Random Media

This blueprint is used to add a script for playing media. The script randomly chooses which media to use from the list given and provides shuffle, repeat and volume options. If you have a multi-room setup (e.g. Sonos) additional media players can be specified. The players will be grouped together with the primary media player.
2110.0K4.0K
šŸŽ›ļø
Device Control
simple
0 inputs

Stop Sonos Alarm

This blueprint is used to add a script that stops current audio on the specified Sonos speaker but if nothing is playing the script checks if an alarm is coming soon and if so, prevents it from going off by disabling the alarm and then re-enabling after it would have gone off. Only one alarm is impacted. This is perfect for when you wake up earlier than your alarm and don't want the alarm to wake others. I recommend setting the mode to parallel if you will use this script on more than one speaker.
219.3K578
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
206.1K738
šŸŽ›ļø
Device Control
medium
4 inputs

Charge phone

Charges phone until a percentage and then turns off until percentage drops below a defined point.
entity
target
number
176.2K2.5K
šŸŽ›ļø
Device Control
medium
2 inputs

Pause Playing Media During Calls

Automatically pause the playing media when you get a call! Currently this only works with the Home Assistant Companion app for Android.
entity
target
67.0K4.2K
šŸŽ›ļø
Device Control
complex
12 inputs

AWTRIX show entity

Show entity
text
entity
object
+3
03.4K3.3K
šŸŽ›ļø
Device Control
complex
17 inputs

Zigbee2MQTT - ERS-10TZBVK-AA

Zigbee Smart knob
entity
action
06.0K2.0K
šŸŽ›ļø
Device Control
complex
10 inputs

Awtrix current playing song

Shows the title and artist of your current playing song on Awtrix.
device
entity
text
+3
02.2K3.0K
šŸŽ›ļø
Device Control
complex
6 inputs

Wake-up light alarm with sunrise effect

A wake-up light alarm with a brightness and color temperature sunrise effect using an existing timestamp sensor as source. Requires date_time_iso sensor in configuration!
entity
time
number
+1
06.1K1.4K
šŸŽ›ļø
Device Control
complex
18 inputs

AWTRIX Night Clock

AWTRIX Night Clock

This blueprint provides a night clock mode for AWTRIX Light. It allows you to personalize various aspects of the clockface to suit your preferences.

Screenshot

Screenshot of AWTRIX Night Clock blueprint

Features

  • This blueprint features a night clock mode, which displays a customized color, and you have the possibility to disable app transitions, automatic brightness, and the color of the night clock.

Prerequisites

AWTRIX v0.72
device
time
boolean
+3
010.1K3.8K
šŸŽ›ļø
Device Control
complex
8 inputs

AWTRIX Solar Energy Monitor

This blueprint will show the current solar energy received. It uses a icons 54156 (solar-green), 50557 (solar-white-dyn), 50546 (solar-static) that you need to install.
device
entity
number
+2
010.8K2.0K
šŸŽ›ļø
Device Control
medium
2 inputs

AWTRIX playing now

Show the current playing track
entity
device
05.0K4.5K
šŸŽ›ļø
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
02.3K985
šŸŽ›ļø
Device Control
simple
1 inputs

LLM Helper script for fetching weather forecasts

Creates a script which will allow an LLM to fetch weather forecasts
entity
08.2K329