ha-blueprint-create

Create Home Assistant Blueprint

Convert an existing Home Assistant automation into a reusable blueprint: $ARGUMENTS

Your Task

Transform the specified automation into a parameterizable blueprint by analyzing its structure and identifying which values should become inputs with appropriate selectors.

Step 1: Analyze the Automation

Location: The argument can be:

• An automation file path (e.g., /path/to/automation.yaml)
• An automation ID from automations.yaml (we'll help you locate it)
• A direct YAML automation configuration

Analysis checklist:

1. Identify all hardcoded values (entity IDs, timeouts, thresholds, scenes, etc.)

2. Determine which values should be parameterized (user-configurable inputs)

3. Recognize selector types appropriate for each input:

   • entity: Single entity ID (default device/area/domain filtering)
   • device: Device selection with driver support
   • area: Home Assistant area selection
   • number: Numeric input with min/max/unit_of_measurement
   • text: Free-form text input (domain, name, label)
   • boolean: True/false toggle
   • select: Predefined list of options
   • object: Complex structured data
   • template: Jinja2 template as input

4. Document automation structure:

   • Trigger type(s) (state, numeric_state, time, time_pattern, sun, event, mqtt, device, etc.)
   • Condition(s) if present (state, numeric_state, time, template, etc.)
   • Action(s) (service call, script, automation trigger, etc.)
   • Mode (single, restart, queued, parallel)

Step 2: Design Blueprint Schema

Create the blueprint's input section with appropriate selector types:

Principles:

• Use most specific selector (entity > object)
• Entity inputs should filter by domain when possible (light:, climate:, etc.)
• Numeric inputs should include min, max, step, unit_of_measurement
• Text inputs should have maxlength and placeholder hints
• Boolean inputs should have clear icon/description labels