Life Admin & HomeDone with OpenClaw
Control lights and fix automations in Home Assistant via OpenClaw
Dan Malone runs OpenClaw as an always-on Claude agent connected to Home Assistant through ha-mcp, controlling his lights and fixing his automations.
- What They Did
- Dan runs OpenClaw in its own LXC container on his Proxmox server, next to Home Assistant, and connects it through ha-mcp. He chats with it over Telegram. When his landing motion lights failed, the agent found two dead Hue bulbs. It couldn't edit the blueprint automation, so it deleted it and rebuilt it as a native one. Dan then asked for weekend nap schedules.
- How It Went
- The fix took about five minutes of typing in Telegram. Dan estimates the Home Assistant UI would have taken at least an hour. The agent also updated his dashboard to show the new automation.
- Worth Knowing
- Costs add up on per-token API billing, because debugging automations burns a lot of context. Dan rides on his roughly $200/month Claude Max plan, and he runs the agent sandboxed in an isolated container.
Try it yourself with OpenClaw
Connect to my Home Assistant at [address] and review my automations. Find any that are broken, failing or never triggering, explain what is wrong, and propose fixes. Show me each proposed change and wait for my approval before saving it, then test the ones that are fixed and report the results.
Do this with a skill.
These SkillShop playbooks do this exact job.