Audit and fix a Home Assistant setup
The writer had Claude audit their Home Assistant config, using the Chrome connector to click through the dashboard and paste config blocks into editors when the MCP couldn't edit directly. Task: Suggested implementation: Run a local MCP proxy on a Mac authenticated with a Long-Lived Access Token and link it to Claude Desktop. Use Claude to audit the Home Assistant device registry. Since the Home Assistant MCP cannot write configuration, instruct Claude to use the Chrome connector to paste YAML into editors, employing JavaScript injection if typing causes text garbling. The human role involves supervising the automation and verifying changes.; tools: Claude in Chrome. Human role: The original post does not say how a person stayed involved.; limitations: Browser automation via Chrome connector is slow and fragile, potentially breaking with Home Assistant UI updates. If the required changes are already known, manual editing is faster. Human supervision is mandatory to prevent unintended configuration errors. Source reliability is low due to the 403 error; this workflow is proposed based on the case description only..
Tools
Published on Agent Work Atlas:
Overview
The writer had Claude audit their Home Assistant config, using the Chrome connector to click through the dashboard and paste config blocks into editors when the MCP couldn't edit directly.
Workflow
Suggested implementation: Run a local MCP proxy on a Mac authenticated with a Long-Lived Access Token and link it to Claude Desktop. Use Claude to audit the Home Assistant device registry. Since the Home Assistant MCP cannot write configuration, instruct Claude to use the Chrome connector to paste YAML into editors, employing JavaScript injection if typing causes text garbling. The human role involves supervising the automation and verifying changes.
Reported result
Actual outcomes are unknown as the source is unavailable (HTTP 403). Proposed acceptance check: Verify that the audit identifies duplicate entities, ghost duplicates, unassigned lights, or misclassified devices (e.g., fans as switches). Confirm that a toggle automation is successfully created and bugs fixed within a reasonable timeframe compared to manual UI navigation.
Human role
The original post does not say how a person stayed involved.
Limitations
Browser automation via Chrome connector is slow and fragile, potentially breaking with Home Assistant UI updates. If the required changes are already known, manual editing is faster. Human supervision is mandatory to prevent unintended configuration errors. Source reliability is low due to the 403 error; this workflow is proposed based on the case description only.
Try it
Act as a Home Assistant configuration assistant. I have a Mac running a local MCP proxy linked to Claude Desktop via a Long-Lived Access Token. My Home Assistant instance is accessible via Chrome. 1. Audit my device registry for duplicates, ghost entities, unassigned lights, and misclassified devices (e.g., fans registered as switches). 2. If the Home Assistant MCP cannot write configs, use the Chrome connector to navigate to the YAML editor. 3. Paste the necessary YAML configuration blocks. If typing results in garbled text, use JavaScript injection to insert the code. 4. Create a toggle automation for [replaceable: specific device or scene] and fix any immediate bugs. Constraints: Do not execute any changes without my explicit confirmation. If the UI structure has changed and automation fails, stop and report the error. Deliverables: A list of identified issues, the proposed YAML code, and a confirmation of successful automation creation. Quality Check: Ensure no duplicate entities remain and the automation functions correctly. First, perform a dry run on a test device or read-only mode to verify the connection and audit logic before attempting any writes. Ask me for the specific device IDs or names if the registry is too large to process automatically.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.