Aurora Smart Home

Describe what you want to build. Get back automations, firmware, integrations, and dashboards that already passed validation.

Aurora is a Claude Code plugin with 21 smart home specialists backed by verified reference data. Home Assistant automations and dashboards, ESPHome firmware, HACS-ready Python integrations, Node-RED flows: every request is routed to the right specialist, and every pin, entity ID, I2C address, and API pattern is checked before code is generated. Ask for something that cannot work, a reserved GPIO or an automation triggering on an entity that does not exist, and Aurora refuses, shows you why, and hands you the fix instead of code that fails silently.

---

⚠️ Use at your own risk. Aurora generates code and recommendations for educational purposes. Smart home projects involve mains electricity, batteries, and devices that control locks, water, heating, and gas. AI-generated configs can be plausible but wrong. The maintainers, contributors, and Anthropic accept no liability for property damage, personal injury, data loss, or any other harm. See DISCLAIMER.md for full terms.

---

Aurora in 10 seconds

/plugin marketplace add tonylofgren/aurora-smart-home
/plugin install aurora@aurora-smart-home
/aurora:aurora

Then just describe it. One request is enough for a complete build: Aurora delivers the ESPHome firmware, the Home Assistant automation, and the dashboard as one coherent project, wired together end to end so the entity the firmware creates is the entity the automation triggers on and the dashboard shows.

You: motion light for the hallway: sensor on ESP32, automation in Home Assistant, a tile on the dashboard

Aurora: plans three specialists working from one shared snapshot:

Volt (firmware)    validates board + pins before writing YAML,
                   creates  binary_sensor.hallway_motion
Sage (automation)  triggers on binary_sensor.hallway_motion,
                   modern triggers:/actions: syntax
Iris (dashboard)   places the same entity on the room view

Anything impossible is refused with a concrete fix instead of generated:

❌ Problem:  GPIO 19/20 are reserved for USB on the ESP32-S3 DevKit.
🔧 Fix:      Use GPIO 8 (SDA) and GPIO 9 (SCL), the board's default
             I2C pins.

If Sage's automation references an entity Volt never creates, Aurora raises the conflict to you instead of shipping broken YAML. Delivery is a project folder on disk, not a paste in chat:

hallway-motion/
├── README.md              ← BOM with prices, wiring table + diagram,
│                            install steps, troubleshooting, recovery
├── hallway-motion.yaml    ← ESPHome firmware (Volt)
├── automations.yaml       ← HA automation (Sage)
├── dashboard.yaml         ← Lovelace view (Iris)
└── secrets.yaml.example   ← WiFi + API key template

No hardware involved? Aurora works the same for pure software requests:

You: lights on at sunset, off at midnight

Aurora: a Home Assistant automation in modern triggers: / actions: syntax, where every entity it references is verified to exist.

You: Python integration for the Acme cloud API, HACS ready

Aurora: the full custom_components/ structure with config flow, coordinator, and the async pitfalls (datetime.now(), blocking I/O) already caught.