Home Assistant Blueprints: Use, Edit, and Update Safely

Use the blueprint as a starting point

Home Assistant blueprints are reusable configurations with blanks for your household’s choices. For an automation blueprint, those choices might be a motion sensor, a lamp and a waiting time. Importing the blueprint makes it available; creating and saving an automation with those inputs gives you a routine that can run.

Choose a blueprint when its advertised behavior and options match your goal. If you only need to select another lamp or change a duration, keep the connection to the blueprint. If you need an extra rule that it does not offer, choose a better-fitting blueprint or convert your configured automation with Take control.

One definition can supply several separately configured automations. Changing one routine’s lamp input does not change the others, but replacing their common definition can. Home Assistant’s blueprint introduction explains this inheritance.

Researched from Home Assistant documentation and the 2026.10.1 motion-light blueprint source on October 12, 2026. The walkthrough is an illustrative configuration and expected-behavior exercise, not a Tara hardware test. Menu wording and installed blueprint versions can differ. The cover is an AI-generated editorial illustration.

1. Check what the blueprint requires

Before importing, read its description, required Home Assistant version and recent change notes. Check the exact device model and connection method when those are specified. A remote-control blueprint written for Zigbee2MQTT is not automatically suitable for the same remote connected through ZHA.

An entity is one named control or reading inside Home Assistant. A blueprint’s selection fields can filter entities by type, device class or integration. An absent device in a picker is a reason to check those requirements before re-pairing anything. The schema reference describes minimum versions and inputs; the selector reference explains the filters.

Blueprint support is built in. The example below needs no HACS download, extra app or paid license. A particular community blueprint may require additional integrations or helpers; those are separate prerequisites. See HACS versus Apps and integrations if its installation instructions mix these terms.

Read the actions before enabling a community routine. For a first exercise, exclude locks, alarms, heaters, water valves and essential lighting. A friendly configuration form is not a guarantee that the underlying actions are appropriate for your home.

2. Import once, then create the routine

1. Open Settings → Automations & scenes → Blueprints.
2. For a community blueprint, choose Import Blueprint, paste its supported forum, GitHub or GitHub Gist URL, then select Preview. Check the displayed identity before completing the import.
3. Choose Create automation for the blueprint, fill its inputs, give the routine a specific name and save.

If Motion-activated Light is already listed, use it directly for the exercise below. If absent, the official importing instructions provide a practice link. That link uses Home Assistant’s development branch, so compare its requirements with your installed release before importing.

3. Work through one lamp before adding rooms

Suppose a desk lamp should turn on when the study sensor detects someone, then turn off after the sensor clears plus a short delay. Use a lamp that is already exposed as a light. entity and responds to its normal Home Assistant control. Keep another light available so the test cannot leave someone in darkness.

First watch the sensor change between clear and detected, and operate the lamp manually. If either check fails, fix that connection before adding the blueprint. Temporarily pause only other nonessential routines that control this lamp, noting which ones to restore.

On a phone, swipe the table sideways.

The 2026.10.1 implementation accepts motion or occupancy binary sensors and light targets. It starts on a clear-to-detected change, turns on the lamp, waits for the sensor to clear, waits the selected seconds, then turns the lamp off.

Time from the reported clear state. If, in a hypothetical run, detection starts at 10:00:00 and the sensor clears at 10:00:45, a 30-second setting makes the turn-off command due around 10:01:15, assuming no new detection or interruption. Those timestamps are a worked example, not measured response times.

This basic version has no daylight restriction, brightness setting or manual-override input. It can turn off a lamp that somebody had already switched on. Use it to learn the workflow; for a finished room routine, decide how lighting should respond only when it is dark and how manual choices should pause automation.

4. Verify the trigger and the ending

Enable the practice routine when it is safe to change the lamp. Start with the sensor clear, then walk into its detection area. Use the following expectations to check more than whether the light briefly comes on.

On a phone, swipe the table sideways to reach the checks in the last column.

The repeated-detection behavior follows this blueprint’s restart mode. Other blueprints can behave differently; automation modes govern overlapping runs.

Open the automation’s Traces view to see which step ran or waited. Run actions skips the normal triggers and top-level conditions, so it does not establish that real motion starts the routine. Home Assistant’s testing guide explains that distinction.

A Home Assistant restart interrupts an in-progress wait or delay; this example does not restore its countdown. Keep the ordinary lamp control usable. For a routine that needs a deadline to survive restarts, use the separate timer recovery guide. See the official troubleshooting guide for disabled routines and failed actions.

5. Choose inputs or Take control

For a longer wait or a different lamp, reopen the saved automation and change its inputs. Give a second room its own automation from the same blueprint. Select that room’s sensor and lamp explicitly; do not assume a duplicated name changed the targets.

For behavior the form cannot express, open the configured automation’s menu and choose Take control. Review the preview before confirming. This turns that routine into an ordinary editable automation; it no longer inherits blueprint changes. There is no automatic conversion back. The editing instructions describe the conversion.

For example, one study needs a special exception but five other rooms use the original behavior. Detaching just the study routine keeps that exception separate. Editing the shared blueprint file would instead change the definition used by the remaining rooms. Keep a note of the exception so future maintenance does not erase its purpose.

6. Update the shared definition deliberately

A normal imported blueprint is a local copy; do not assume it follows every change published by its author. The built-in Re-import blueprint command downloads a replacement. Home Assistant introduced that workflow in 2023.12, and the current usage documentation warns that incompatible changes can break dependent automations.

1. List the affected routines. Record their inputs and retain the known-good blueprint file before replacing it. A record of inputs alone does not preserve the old instructions. In the automation’s menu, Edit in YAML opens its text configuration. The path entry under use_blueprint identifies its file beneath blueprints/automation/ in your configuration directory. Use your existing configuration-file access to copy it somewhere safe. If you cannot preserve that file, defer the replacement.
2. Read what changed. Check renamed or newly required inputs, minimum versions, altered defaults and changed actions. For an essential routine, postpone the update until you have a safe maintenance plan.
3. Choose a quiet maintenance period. Disable affected nonessential routines while checking the replacement. Updating the shared definition is not an isolated test of one room.
4. Re-import from the blueprint’s menu. Inspect each dependent automation, correct its inputs if necessary, then re-enable and repeat its harmless acceptance test one at a time.

If a lighting routine fails after the update, leave it disabled and check the reported error against the changed input requirements. To undo this file replacement, restore your saved blueprint at the same path, restore recorded inputs if you changed them, reload automations and repeat the lamp check. The blueprint tutorial explains file locations and references.

Dependent automations pick up the changed definition when reloaded. If you edited the file manually, reload automations as described in the official introduction. Disabling one routine does not give it a private version of the blueprint. A detached automation, by contrast, needs its own fixes because it no longer receives the shared changes.

Common questions

Does a blueprint make a cloud device local?

No. It defines a routine, not a new connection to the device. Check the integration used by each sensor and action. Downloading instructions locally does not remove a vendor login or cloud dependency.

Why is my lamp missing from the Light picker?

Check its entity type. This example selects lights; a plug may appear as a switch instead. Do not choose an unrelated entity just to complete the form. Confirm the blueprint’s accepted inputs and use a suitable lamp target.

Should I use a blueprint for a very simple rule?

Only if it makes the rule easier to understand and maintain. A small automation you can explain is a reasonable choice. Choose reuse when several rooms really share the same behavior, rather than adding options you do not need.

If you want help assembling and handing over understandable routines, Tara’s configured Home Assistant setup is the relevant service path. Start with a clear description of what each room should do and what a person’s manual adjustment should mean.