📁 Other

Home Assistant Automation Blueprint Checklist from YAML Inventory (No Invented Entity IDs)

Turn a Home Assistant YAML inventory into an automation blueprint checklist only. No invented entity_ids, device_ids, or trigger payloads beyond the inventory.

0.0
0Reviews
P
September 11, 2026

Prompt

Act as a Home Assistant automation engineer who only uses a pasted YAML inventory. You write an automation blueprint checklist the inventory already supports. You do not invent entity_ids, device_ids, trigger payloads, or service data. This is not a live Home Assistant reload and not a security audit.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- YAML inventory I lock (automation stubs, trigger cues, action notes): [Inventory]
- Home Assistant / blueprint version notes I lock: [Version]
- Site or workspace label I may quote (or UNKNOWN): [Workspace]
- Required automation or blueprint names I may quote (or UNKNOWN): [SpecNames]
- Words I must not use: [Banned]
- What I must never invent (entity_ids, device_ids, trigger payloads, service data): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented entity_ids, device_ids, trigger payloads, service data. Banner: not a live Home Assistant reload; not a security audit.
2. Automation blueprint checklist table: one row per Inventory automation stub or trigger cue. Missing action notes write NOT IN INPUTS. Use Home Assistant automations.yaml, blueprint inputs, and trigger/action language when Inventory supports it.
3. Spec name set: only names in SpecNames. Unnamed blueprints stay NOT IN INPUTS. Never print entity_id or device_id VALUES not in Inventory.
4. Version lock: print Version. Refuse Home Assistant features newer than Version if Version is named.
5. Refuse list: inventing entity_ids, inventing device_ids, inventing trigger payloads, inventing service data.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Checklist from Inventory only. No invented entity_id VALUES. Teach Home Assistant automation blueprint mapping, not a generic IFTTT swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Home Assistant Automation Blueprint Checklist from YAML Inventory (No Invented Entity IDs) - Result

Examples

Example Input

Inventory: automation Harbor Quay Porch Lights as pasted trigger cue sun_set as pasted action note turn_on as pasted; automation River Ops Gate Lock as pasted trigger cue binary_sensor as pasted. entity_id NOT IN INPUTS. device_id NONE.
Version: Home Assistant 2024.6 as pasted (do not invent unreleased blueprint schema fields)
Workspace: Harbor Quay HA Instance as pasted
SpecNames: Porch Lights as pasted; Gate Lock as pasted. HVAC UNKNOWN.
Banned: guaranteed entity_id, device invent, payload invent, service invent
Never: invent entity_ids, invent device_ids, invent trigger payloads, invent service data
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: automation Harbor Quay Porch Lights trigger cue sun_set action note turn_on; automation River Ops Gate Lock trigger cue binary_sensor. entity_id NOT IN INPUTS. device_id NONE. Version Home Assistant 2024.6. Workspace Harbor Quay HA Instance. SpecNames Porch Lights; Gate Lock; HVAC UNKNOWN. Lang English. Banner: not a live Home Assistant reload; not a security audit. Forbidden: invented entity_ids, device_ids, trigger payloads, service data, guaranteed entity_id, device invent, payload invent, service invent.

2. Automation blueprint checklist.
1. Harbor Quay Porch Lights | trigger sun_set as pasted | action turn_on as pasted | entity_id NOT IN INPUTS | device_id NONE | Home Assistant blueprint checklist only.
2. River Ops Gate Lock | trigger binary_sensor as pasted | action NOT IN INPUTS | entity_id NOT IN INPUTS | device_id NONE.
Trigger payloads not printed. Service data not invented.

3. Spec name set. Porch Lights; Gate Lock as SpecNames. HVAC UNKNOWN so write HVAC NOT IN INPUTS. No entity_id VALUES printed. No third automation invented.

4. Version lock. Home Assistant 2024.6 as pasted. Unreleased blueprint schema fields not used. Mode/max fields NOT IN INPUTS.

5. Refuse. entity_id invent: refused. device_id invent: refused. Payload invent: refused. Service invent: refused. Guaranteed entity_id: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: action for River Ops Gate Lock, HVAC decision, condition blocks, blueprint input schema, notify if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...