Audit and fix a Home Assistant setup
Real-world thread: the writer ran a local MCP proxy on a Mac, authenticated with a Long-Lived Access Token, and linked it to Claude Desktop. Because the Home Assistant MCP can't write config, Claude drove the Chrome connector to paste YAML into the editors, and used JavaScript injection when typing garbled the text. The audit located triplicate TV entities, ghost duplicates, unassigned lights, and a fan registered as a plain switch.
- Agent or tool
- Claude
- Topic
- Personal Assistant
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
This is the classic promise of AI agents: a helper that handles errands and reminders on your behalf. Real cases like this show how close that promise is today. It is one of 50 sightings filed under Personal Assistant on Agent Sightings (number 50 by interest), and one of 91 involving Claude.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Claude or any similar agent and adjust the details to your situation.
Assistant mode: audit and fix a Home Assistant setup. Log every action, prefer reversible steps, and ask before emailing, paying, or deleting.
Tip: Start small: run it once on a low-stakes example, read what the agent did, and only then let it run on real work.
Source
Read the original first-hand account on Blog: https://www.androidauthority.com/using-claude-fix-home-assistant-smart-home-367…. Our summary is a paraphrase; details are in the source.