This repository contains some blueprints for Home Assistant.
Home Assistant is an amazing home automation software that gives you full control over all your smart devices and allows you to integrate different platforms. To learn more about it check the Home Assistant Website .
Blueprints are used, in Home Assistant, as templates for building automation quickly. If you want to learn more about it and start writing your own automation check the Creating blueprints page.
This is a template for creating an automation that will check all battery class sensors in your Home Assistant installation for a low-battery condition, and then execute one or more actions, e.g. send a message with every sensor that has a low-battery condition to your phone.
The following types of battery sensors are supported:
- The regular percentage-type battery sensor (e.g. sensor.low_battery with a value representing the battery status in percentages)
- A binary sensor that indicates a low-battery condition when its state is 'on' (e.g. sensor_low_battery with a value of either 'on' or 'off', with 'on' representing a low-battery status)
- A regular sensor that uses fixed values to represent the battery status (e.g. sensor_low_battery with a value of 'high', 'medium', 'low' or some other values with one of them representing a low-battery state). The latter is commonly used by Tuya-type devices.
Note that only battery sensors with the device class 'battery' will be checked. It's pretty common for Tuya-type battery sensors not to set the device class to 'battery', for such sensors you can use customize to set the device class to the correct type.
customize:
sensor.my_tuya_device_battery_state
device_class: battery
The blueprint will let you set a threshold value for when percentage-type battery sensors should be considered to be in a low-battery state. It will also let you enable support for fixed-value type battery sensors, and to customize the string that represent a low-battery state for such sensors (e.g. 'low'). There are no further options for binary-type battery sensors, such sensors will automatically be checked if they exist.
You can also set the time of the day and days of the week when the automation should be executed.
You can use {{sensors}} in your actions, this will be substituted with a string that is a comma-separated list of all sensors with a low-battery status and their values.
You can also exclude one or more sensors from being checked, that is useful to exclude for instance phones, tablets, and similar devices.
Notice: There is a bug in Home Assistant that causes boolean selectors not to be saved properly when an automation based on a blueprint is later being edited in the GUI, so any changes to your automation(s) based on this blueprint that involves changing the on/off selectors in the blueprint will not be saved. Their states will be saved correctly when you first create the automation, but for subsequent changes their states will not be saved/updated correctly. This bug is still present in Home Aassistant version 2022.10.5, and a description of the bug can be found here.
There are two possible workarounds:
- Delete and re-create the automation.
- Manually edit automations.yaml (remember to reload your automations, you can call the service automation.reload to do this).
This blueprint is based on work by @sbyx and @gmlupatelli.
Just click on IMPORT BLUEPRINT above to add this blueprint to your Home Assistant installation.
After installing this blueprint you will find it in your Home Assistant installation under Settings -> Automations & Scenes -> Blueprints. Just click on CREATE AUTOMATION and follow the instructions in the blueprint and in the description above to create your automation.
This is a template for creating an automation that will check all entities in your Home Assistant installation for a unavailable status, and then execute one or more actions, e.g. send a message with every entity that is currently unavailable to your phone.
The blueprint will let you set the time of the day and days of the week when the automation should be executed.
You can use {{entities}} in your actions, this will be substituted with a string that is a comma-separated list of all entities with status unavailable.
You can also exclude one or more entities from being checked, that is useful to exclude for instance phones, tablets, and similar devices.
Notice: There is a bug in Home Assistant that causes boolean selectors not to be saved properly when an automation based on a blueprint is later being edited in the GUI, so any changes to your automation(s) based on this blueprint that involves changing the on/off selectors in the blueprint will not be saved. Their states will be saved correctly when you first create the automation, but for subsequent changes their states will not be saved/updated correctly. This bug is still present in Home Aassistant version 2022.10.5, and a description of the bug can be found here.
There are two possible workarounds:
- Delete and re-create the automation.
- Manually edit automations.yaml (remember to reload your automations, you can call the service automation.reload to do this).
This blueprint is based on work by @gmlupatelli.
Just click on IMPORT BLUEPRINT above to add this blueprint to your Home Assistant installation.
After installing this blueprint you will find it in your Home Assistant installation under Settings -> Automations & Scenes -> Blueprints. Just click on CREATE AUTOMATION and follow the instructions in the blueprint and in the description above to create your automation.
This is a template for creating an automation that will pause an [climate](https://www.home-assistant.io/integrations/climate/ entity in your Home Assistant installation if a door or window has been opened, and then resume the previous state once the door(s)/window(s) has been closed.
The [Climate Device](https://www.home-assistant.io/integrations/climate/ has to be a single entity (eg not a group), and the door/window sensor has to be a group, even if that group would have only one door/window sensor.
You can specify the {{Pause Delay}}, eg the time a door/window needs to be open before the [climate](https://www.home-assistant.io/integrations/climate/ entity will pause. You can also specity the {{Resume Delay}}, eg the how soon after the previously opened door/window the [climate](https://www.home-assistant.io/integrations/climate/ entity will resume its previous state.
You can also, optionally, add an action to be performed then the [climate](https://www.home-assistant.io/integrations/climate/ entity is being passed, and another actionto be performed then the [climate](https://www.home-assistant.io/integrations/climate/ entity resumes its previous state.
This blueprint is based on work by @raffy-ops.
Just click on IMPORT BLUEPRINT above to add this blueprint to your Home Assistant installation.
After installing this blueprint you will find it in your Home Assistant installation under Settings -> Automations & Scenes -> Blueprints. Just click on CREATE AUTOMATION and follow the instructions in the blueprint and in the description above to create your automation.
This is a template for creating an automation with a simple repeating weekly schedule, with actions to be executed twice each day, on one or more days each week in a repeating pattern. This can be used to start/turn on and to stop/turn off one or more entities in your Home Assistant installation, e.g. a light or a switch, at fixed times or alternatively at sunrise and/or sunset. This could for example be used to turn on your outdoor lights at sunset, and then turn them off again the next morning at sunrise.
But this is just an example of a simple use-case. Any number of the actions available in Home Assistant can be scheduled to execute two times each day, either at a specific time or at sunrise or sunset. This can be two different sets of actions, and you can select on which day(s) of the week the selected action(s) should be executed.
Notice: There is a bug in Home Assistant that causes boolean selectors not to be saved properly when an automation based on a blueprint is later being edited in the GUI, so any changes to your automation(s) based on this blueprint that involves changing the on/off selectors in the blueprint will not be saved. Their states will be saved correctly when you first create the automation, but for subsequent changes their states will not be saved/updated correctly. This bug is still present in Home Aassistant version 2022.10.5, and a description of the bug can be found here.
There are two possible workarounds:
- Delete and re-create the automation.
- Manually edit automations.yaml (remember to reload your automations, you can call the service automation.reload to do this).
This blueprint is based on work by @gmlupatelli.
Just click on IMPORT BLUEPRINT above to add this blueprint to your Home Assistant installation.
After installing this blueprint you will find it in your Home Assistant installation under Settings -> Automations & Scenes -> Blueprints. Just click on CREATE AUTOMATION and follow the instructions in the blueprint and in the description above to create your automation.