About blueprints

Blueprints are the easiest way to add automations, scripts, or template entities to your Home Assistant. Someone in the community has already done the work of writing the configuration, and you fill in the bits that are specific to your home, like which sensor to watch and which light to control.

You can find a blueprint for almost any common use case in the community blueprint forum: motion-activated lights, low-battery notifications, holiday lighting, presence-based heating, and many more.

This page is a high-level introduction. If you want to create your own blueprint to share, see About the blueprint schema.

What is a blueprint?

A blueprint is a scriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more], automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more], or template entity configuration where some parts have been left blank, ready for you to fill in. That way, the same blueprint can be reused over and over with different devices and settings.

Imagine you want to turn on a light when motion is detected. A blueprint provides the generic automation, while letting you select which motion sensor and which light. You can use that same blueprint twice, once for the hallway and once for the bathroom, and end up with two completely independent automations that each behave the way you configured them.

Automations inherit from the blueprint they were built on, so if the blueprint is updated, all automations using it pick up the change the next time Home Assistant reloads them. To reload manually, go to Settings > Developer tools > YAML and reload the automations.

Blueprints are shared by the community in the blueprint community forum.