Automation blueprints are pre-made automations that you can easily add to your Home Assistant instance. Each blueprint can be added as many times as you want.
Automations based on a blueprint only need to be configured to be used. What needs to be configured differs on each blueprint.
This will open the automation editor with the blueprint selected. Give it a name and configure the blueprint and click on the blue button “Save Automation” in the bottom right.
Home Assistant can import blueprints from the Home Assistant forums, GitHub and GitHub gists.
To do this, first find a blueprint you want to import. If you just want to practice importing, you can use this URL:
A new dialog will pop-up asking you for the URL. Enter the URL and click on “preview blueprint”.
This will load the blueprint and show a preview in the import dialog. You can change the name and finish the import.
The blueprint can now be used for creating automations.
Blueprints created by the community may go through multiple revisions. Sometimes a user creates a blueprint, the community provides feedback, and new functionality is added.
While there’s no built-in functionality to update a blueprint you’ve already imported, you can manually edit its YAML content to keep it up to date:
- Navigate to the blueprints directory (
blueprints/automation/). The location of this directory depends on the installation method and it’s similar to how you find
- Next, you must find the blueprint to update. The path name of a blueprint consists of:
- The username of the user that created it, which depends from where you imported the blueprint, the forum or GitHub.
- The name of the YAML file. For the forum it’s the title of the topic in the URL, for GitHub it’s the name of the YAML file.
- Open the YAML file with your editor and update its contents.
- Reload the automations for the changes to take effect.
The new changes will appear to your existing automations as well.
The Home Assistant Community forums have a specific tag for blueprints. This tag is used to collect all blueprints.
Using blueprints is nice and easy, but what if you could create that one missing blueprint that our community definitely needs?
Learn more about blueprint by reading our tutorial on creating a blueprint.
When you’re creating automations using blueprints and they don’t appear in the UI, make sure that you add back
automation: !include automations.yaml from the default configuration to your