Home Assistant Blueprints Explained: How to Use Them
A Home Assistant blueprint is a reusable automation template: someone writes the logic once, exposes the parts you need to customize as simple dropdown fields, and shares it. You import the blueprint, pick your devices and options in a form, and Home Assistant generates a working automation for you—no YAML editing required. In short, blueprints let you skip writing an automation from scratch and instead fill in the blanks of a proven one. This guide explains how blueprints work, how to import and configure them, and when they're the right tool.
What a blueprint actually is
Under the hood, a Home Assistant automation is a piece of YAML describing triggers (what starts it), conditions (whether it should run), and actions (what happens). Most automations are highly specific: this motion sensor turns on that light. That specificity makes them hard to reuse—if a friend shares their motion-light automation, you'd have to hunt through the YAML and swap in your own entity IDs.
A blueprint solves this by pulling out the parts that change from the parts that stay the same. The author defines inputs—labeled placeholders like "Motion sensor," "Light to control," and "Wait time"—and writes the automation logic to reference those inputs instead of hard-coded devices. When you use the blueprint, Home Assistant reads those input definitions and renders a form. You fill it in, and it substitutes your choices into the template.
The result is that a single, well-written blueprint can generate dozens of different automations across many people's homes, each configured differently, all sharing the same underlying logic. It's the same idea behind reusable code anywhere: write once, configure many times.
Blueprints vs. writing an automation yourself
Blueprints aren't a replacement for regular automations—they're a different starting point. Here's how the two compare for a typical task.
- Fastest for common, well-solved patterns (motion lights, notifications)
- No YAML knowledge needed—just fill in a form
- Benefits from community testing and refinement
- Full control over every trigger, condition, and action
- Better for logic unique to your home that no template covers
- Nothing hidden—every line is visible and editable
A good rule of thumb: reach for a blueprint when your need is common and someone has almost certainly solved it already. Write your own when the logic is specific to your setup, or when you're learning and want to understand exactly how each piece fits together. If you're new to automations in general, our beginner's guide to Home Assistant automations is a good companion to this article.
How to import and use a blueprint
Most blueprints are shared as a link—often to a post on the Home Assistant Community Forum, where the blueprint format was first popularized. Importing one is straightforward.
- 1In Home Assistant, go to Settings → Automations & Scenes → Blueprints and choose to import a blueprint
- 2Paste the blueprint’s URL and confirm the import—it’s now saved to your instance
- 3Choose to create a new automation from that blueprint, fill in the form (devices, timings, options), and save
After you import a blueprint, it lives in your instance and can be reused as many times as you like. Creating an automation from it opens the input form; each field maps to one of the author's defined inputs. Once you save, Home Assistant creates a normal automation entry that's linked back to the blueprint. You'll see it in your automations list like any other, and you can enable, disable, or trace it the same way.
A few practical notes on sourcing blueprints:
- Community Forum: The official forum has a dedicated blueprints category and a one-click "Import Blueprint" button that pre-fills the URL for you.
- GitHub: Many authors host blueprints in repositories; you import the raw file URL the same way.
- HACS: Some blueprint collections are distributed through the Home Assistant Community Store. If you haven't set that up, see our guide on what HACS is and how to install it.
Configuring inputs the right way
The form you fill in is where a blueprint earns its keep, so it helps to understand the common input types you'll encounter:
- Entity or device selectors—pick the actual sensor, light, or switch involved. These are usually the required fields.
- Targets—some blueprints let you choose a whole area or multiple entities at once, so one automation can cover a room.
- Options and toggles—things like "only run after sunset," brightness levels, or wait times, often with sensible defaults already set.
- Actions—advanced blueprints may let you plug in your own action, such as which notification to send. If you're wiring up phone alerts, our guide to getting phone notifications from Home Assistant pairs well here.
Fields left blank fall back to the author's defaults. If a blueprint behaves unexpectedly, the first thing to check is whether an optional input you assumed was set is actually empty.
Updating and the shared-logic tradeoff
The biggest strength of blueprints is also the thing to understand before you lean on them: automations are linked to the blueprint they came from. If the author releases an improved version and you re-import it, every automation built from that blueprint picks up the change at once. That's wonderful when it's a bug fix, and disruptive if the update alters behavior you were relying on.
Because of that shared link, you generally can't edit a blueprint-based automation's core logic directly in the UI editor—only its inputs. If you need to change the underlying behavior, you either edit the blueprint file itself (which affects all automations using it) or detach by recreating the automation as a standalone one. Before importing an updated blueprint over an existing one, it's worth having a current backup; see our Home Assistant backup and restore guide.
Frequently asked questions
Do I need to know YAML to use blueprints?
No. Importing and configuring a blueprint is entirely form-based—you paste a URL and fill in dropdowns. You'd only touch YAML if you decide to write or modify a blueprint yourself, which is optional and separate from simply using one.
Where do I find good blueprints?
The Home Assistant Community Forum has a dedicated blueprints category and is the most established source, with an import button that streamlines the process. GitHub repositories and some HACS collections are also common. Favor blueprints with active discussion and recent updates, since those tend to be the most reliable.
Can I change what a blueprint does?
You can freely change its inputs—the devices, timings, and options in the form. Changing its core logic means editing the blueprint file itself (which affects every automation built from it) or recreating the automation as a standalone, unlinked one. For home-specific behavior no template covers, writing your own automation is often cleaner.
Will updating a blueprint break my automations?
It can change them. Because automations are linked to their blueprint, re-importing a newer version applies the author's changes to every automation using it. Usually that's an improvement, but review release notes and keep a backup before updating one you depend on.
