Integrate OpenClaw AI assistant with Home Assistant to control smart home devices via natural language.
┌─ HomePod / Siri ──▶ HomeKit ──▶ Aqara M3 ──▶ Aqara Switches ──▶ Lights
│ (existing, untouched)
│
└─ OpenClaw ──▶ Home Assistant ──Matter──▶ Aqara M3 ──▶ Aqara Switches ──▶ Lights
(new, independent)
| Device | Role |
|---|---|
| Yeelight Smart Lights | Light fixtures (controlled via Aqara switches) |
| Aqara Smart Wall Switches | Physical on/off control of lights |
| Aqara Hub M3 (方舟智慧中枢) | Zigbee gateway, HomeKit & Matter bridge |
| HomePod | Apple HomeKit hub, Siri voice control |
- Non-invasive: The existing HomeKit chain (HomePod → M3 → Switches) remains completely untouched
- Independent paths: HA connects to M3 via Matter protocol, a separate channel from HomeKit
- Graceful degradation: If HA goes down, HomeKit continues working; since OpenClaw and HA are co-located, if HA is down, the AI is down too — no orphaned state
- Evolution path: Start as an "additional layer", gradually migrate to HA as the central hub
| Integration | Protocol | Purpose |
|---|---|---|
| HA ↔ Aqara M3 | Matter | Control Aqara switches |
| HA ↔ Yeelight | LAN (future) | Direct light control (Phase 2) |
| OpenClaw ↔ HA | MCP Server | AI agent tool calling |
| HA → Apple Home | HomeKit Bridge (future) | Maintain Siri control after full migration |
| Document | Description |
|---|---|
| docs/01-ha-docker-deployment.md | Home Assistant Docker deployment guide |
| docs/02-aqara-m3-matter-setup.md | Aqara M3 Matter bridge setup for HA |
| docs/03-ha-mcp-server.md | HA MCP Server configuration |
| docs/04-openclaw-mcp-client.md | OpenClaw MCP client connection |
| docs/05-implementation-plan.md | Step-by-step implementation plan |
| docs/06-evolution-roadmap.md | Roadmap: from additional layer to central hub |
See docs/05-implementation-plan.md for the full step-by-step guide.
MIT