Reported issues for ha-mcp

Pod holds 8 of 8 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to ha-mcp.

Most discussed

[BUG] Writes fail with ClientDisconnect while reading request body (addon + mcp-proxy, no TLS)

💬 What Happened?

When creating or editing dashboards, automations, helpers etc., writes intermittently time out (4 minute client timeout). Sometimes after 4 writes, sometimes on the very first one. Reads always return instantly. Sometimes the writes go through anyway despite the timeout. Restarting the client or the addon helps temporarily. I tested a different network connection and downgraded the addon — same picture.

Digging into the addon log we found the server logging…

Read the thread · 2026-09-04 · open · external user · 38 comments

Known issue: Claude Desktop and other mcp-proxy clients fail to connect after the MCP SDK 2.0.0 release — add --with "mcp<2.0.0" to your config

If your working setup broke on or after 28 July 2026 and your client config runs mcp-proxy, this may be the cause. Please try this fix first before filing a new issue.

Fix

Recommended: switch to fastmcp-remote. As of #2101, the Setup Wizard generates this instead of a pinned mcp-proxy config. fastmcp-remote is the FastMCP project's own stdio bridge and pins its SDK dependency to a bounded range (mcp<2.0,>=1.24.0 as…

Read the thread · 2026-07-30 · open · 4 comments

[BUG] ha_config_set_automation reusing a single fixed placeholder slot

💬 What Happened?

While using the MCP to edit some automations, I also created a new one. When I click on that automation (for manual editing, it opens /config/automation/edit/new. Also when trying to read traces, it doesnt load any and the url says /config/automation/trace/new. The automation has a full description, and even works / fires.

When trying to create another automation it keeps overwriting this one, even flagged by Claude that he notices the old one is overwritten.…

Read the thread · 2026-09-08 · closed · external user · 3 comments

[FEATURE] Emit SSE shutdown advisory (event: shutdown + retry:) on SIGTERM before closing stream

💬 What's the Feature?

Emit a final SSE frame advising clients of a planned shutdown before closing the stream on SIGTERM (or any orderly stop). Something like:

event: shutdown
data: {"reason":"planned_restart","eta_seconds":90,"source":"sigterm"}
retry: 90000

then drain in-flight requests and close cleanly.

🎯 Why it matters

Today an SSE client cannot distinguish three very different shutdown modes:

Planned homeassistant.restart (come back in ~60-120 s).
Add-on…

Read the thread · 2026-09-07 · closed · external user · 3 comments

[BUG] Identical concurrent calls share one approval with remember_minutes=0

What happened

While checking the meaning of “require approval every time”, we reproduced two identical concurrent static tool calls executing after one approval with remember_minutes=0.

This was reproduced offline, using the real FastMCP server, PolicyMiddleware and approval queue, with a fake terminal action that only appends to a Python list. No Home Assistant connection, household device operation or live Settings UI approval was used. This report was prepared by Hermes at the…

Read the thread · 2026-09-07 · closed · external user · 3 comments

[BUG] ha-mcp@latest (8.4.x) prints startup banner to stdout, breaking stdio JSON-RPC transport

Bug

ha-mcp@latest (currently resolving to 8.4.3) prints a FastMCP ASCII-art startup banner and a "settings UI sidecar spawned" notice to stdout, not stderr. When run as a stdio MCP server (uvx ha-mcp@latest directly, no mcp-proxy/fastmcp-remote bridge involved), this corrupts the stdio JSON-RPC transport: the client never sees a valid initialize response before its connection timeout and the connection fails.

ha-mcp==8.3.0 does not have this problem — stdout stays clean…

Read the thread · 2026-09-05 · open · external user · 3 comments

[BUG] Read Only Mode does not block ha_call_service writes

💬 What Happened?

I have used the read-only-mode to give Claude read-only permissions. But Claude had write permission while read-only was activated. I have deactivated, restarted the add on (app) and disconnected the the claude connector different times - no change.

📋 Copy-Paste from Conversation

**User prompt (paraphrased):** "Please test the connection" / "Try a real write" — verifying whether Read Only Mode actually blocks write operations from an AI client.

**Tool…

[Read the thread](https://github.com/homeassistant-ai/ha-mcp/issues/2410) · 2026-09-08 · closed · external user · 2 comments

### [FEATURE] Enable/disable an automation or script without ha_call_service

### What would you like to see?

`ha_config_set_automation` and `ha_config_set_script` should accept an `enabled: bool | None` parameter that enables or disables the automation/script, routed internally to the appropriate service call rather than written into the stored config.

Right now there is no way to enable or disable an automation or a script through the automation/script tool surface. Every route is closed except `ha_call_service`:

| Tool | Result |
|---|---|
|…

[Read the thread](https://github.com/homeassistant-ai/ha-mcp/issues/2404) · 2026-09-07 · open · 2 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/homeassistant-ai/ha-mcp.git/issues).