Problem statement
Discovering and using blueprints is inaccessible to non-technical users. The current GitHub gist-based method is opaque and hard to navigate. First-time use of a blueprint lacks guidance, and managing automations created from blueprints, such as knowing which blueprint they came from or whether an update is available, is not supported. Blueprints are an incredibly approachable way to get started with Home Assistant and to learn about its capabilities, but if Blueprints themselves are not approachable enough, that hurts our overall goals.
Scope & Boundaries
In scope
- Improved blueprint discovery surface
- First-time blueprint usage flow with clear input guidance
- Management UI for blueprint-based automations (source blueprint, update availability)
Not in scope
- Improved UI around creating and using blueprints themselves
Foreseen solution
A blueprints section in the HA UI with browsable and searchable community blueprints (essentially a "blueprints store"). A guided setup flow when creating an automation from a blueprint. Blueprint-sourced automations show their origin and whether an update is available.
Community signals
- GitHub gist import is a barrier for non-technical users (sources needed)
Risks & open questions
- Trust and safety: community blueprints can contain arbitrary actions; how do we communicate risk to users and deal with moderation-challenges?
Appetite
Very large — likely to be more than 2 cycles.
Execution issues
No response
Decision log
Problem statement
Discovering and using blueprints is inaccessible to non-technical users. The current GitHub gist-based method is opaque and hard to navigate. First-time use of a blueprint lacks guidance, and managing automations created from blueprints, such as knowing which blueprint they came from or whether an update is available, is not supported. Blueprints are an incredibly approachable way to get started with Home Assistant and to learn about its capabilities, but if Blueprints themselves are not approachable enough, that hurts our overall goals.
Scope & Boundaries
In scope
Not in scope
Foreseen solution
A blueprints section in the HA UI with browsable and searchable community blueprints (essentially a "blueprints store"). A guided setup flow when creating an automation from a blueprint. Blueprint-sourced automations show their origin and whether an update is available.
Community signals
Risks & open questions
Appetite
Very large — likely to be more than 2 cycles.
Execution issues
No response
Decision log