PyPI - ha-mcp-dev - Versions diffs - 9.1.1.dev3382__tar.gz → 9.1.1.dev3389__tar.gz - Mend

ha-mcp-dev 9.1.1.dev3382tar.gz → 9.1.1.dev3389tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (847) hide show

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/PKG-INFO RENAMED Viewed

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 9.1.1.dev3382
-Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
+Version: 9.1.1.dev3389
+Summary: Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.
 Keywords: mcp,home-assistant,ai,automation,smart-home
 Author: Julien
 Author-email: Julien <github@qc-h.net>
@@ -64,7 +64,7 @@ Description-Content-Type: text/markdown
 <div align="center">
   <img src="https://raw.githubusercontent.com/homeassistant-ai/ha-mcp/master/docs/img/ha-mcp-logo.png" alt="Home Assistant MCP Server Logo" width="300"/>
-  # The Unofficial and Awesome Home Assistant MCP Server
+  # HA-MCP — Manage Home Assistant with AI
   <!-- mcp-name: io.github.homeassistant-ai/ha-mcp -->
@@ -82,8 +82,7 @@ Description-Content-Type: text/markdown
   </p>
   <p align="center">
-    <em>A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with Home Assistant.<br>
-    Using natural language, control smart home devices, query states, execute services and manage your automations.</em>
+    <em>Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.</em>
   </p>
 </div>
@@ -95,7 +94,7 @@ Description-Content-Type: text/markdown
 ## 🚀 Get Started
-The recommended way to run ha-mcp is the **HA-MCP Custom Component**. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server **in-process**, and works on **every** Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
+The recommended way to run ha-mcp is the **HA-MCP integration**. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server **in-process**, and works on **every** Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
 **Add it to Home Assistant via HACS or, on Home Assistant 2026.11+, the Marketplace (the preferred install):**
@@ -105,13 +104,14 @@ The recommended way to run ha-mcp is the **HA-MCP Custom Component**. It install
 > The setup below is for version 9.0.0 (October 28, 2026) and later; earlier versions show a shorter setup form without the administrator account step.
-1. Install the **HA-MCP Custom Component**. On **Home Assistant 2026.10 or older**, from HACS — click the badge above, or in HACS open **Integrations → ⋮ → Custom repositories**, add `https://github.com/homeassistant-ai/ha-mcp` (category: **Integration**), then **Download**.
-   On **Home Assistant 2026.11 or newer**, HACS is built in as the **Marketplace**: open **Settings → Marketplace** and accept its first-run warning, then **Connect GitHub** (a device sign-in). Adding a custom repository needs it, and until HA-MCP is in the Marketplace catalog it is also what makes the Marketplace check HA-MCP for updates in the background; without it, **Refresh information** on HA-MCP's Marketplace page checks by hand. Then click the badge above, or open the **Add from link** tab and add `https://github.com/homeassistant-ai/ha-mcp` as an **Integration**, and **Install**.
-   Already installed from the earlier `homeassistant-ai/ha-mcp-integration` repository? It keeps receiving the same releases; nothing to change.
+1. Install the **HA-MCP integration** (requires **Home Assistant 2026.8.0 or newer**; see [compatibility details](docs/in-process-server.md#requirements)). On **Home Assistant 2026.8–2026.10**, open HACS, search for **HA-MCP**, then **Download**.
+   On **Home Assistant 2026.11 or newer**, open **Settings → Marketplace**, accept its first-run warning, and search for **HA-MCP**, then **Install**. HA-MCP is in the default catalog, so installing it and receiving its updates do not require connecting GitHub or adding a custom repository. The badge above also opens its catalog page.
+   Already installed from the earlier `homeassistant-ai/ha-mcp-integration` repository? It keeps receiving the same releases. On the Marketplace, keep GitHub connected for its background checks on that custom repository.
+   Older installed releases may still appear as **HA-MCP Custom Component**; searching for **HA-MCP** matches both names.
 2. **Restart Home Assistant.**
 3. Decide which administrator account the server acts as. Either create a long-lived access token on your own account (your profile → **Security** → **Long-lived access tokens** → **Create token**; it works from anywhere if it leaks, and the server's changes show under your name), or, safer, create an account just for HA-MCP under **Settings → People → Add person** with **Allow login**, **Local access only** and **Administrator** on. Never use your own login for the second option.
-4. Go to **Settings → Devices & Services → Add Integration**, search for **HA-MCP Custom Component** and choose **HA-MCP Server**. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — **Remote access through Home Assistant** (start with **Secret URL**, the simplest; **Home Assistant sign-in** adds a login) and/or **Network access: Local network** — then click **Submit**. Both start disabled, so a client on another device needs one of them.
-5. Copy the connect URL from the entry's **Configure** screen (**Settings → Devices & Services → HA-MCP Custom Component → HA-MCP Server → Configure**). A notification confirms the server started and points you there.
+4. Go to **Settings → Devices & Services → Add Integration**, search for **HA-MCP** and choose **HA-MCP Server**. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — **Remote access through Home Assistant** (start with **Secret URL**, the simplest; **Home Assistant sign-in** adds a login) and/or **Network access: Local network** — then click **Submit**. Both start disabled, so a client on another device needs one of them.
+5. Copy the connect URL from the entry's **Configure** screen (**Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” → HA-MCP Server → Configure**). A notification confirms the server started and points you there.
 6. Paste that URL into your AI client — done.
 **Connect URL.** The Configure screen gives you a Home Assistant webhook URL for remote clients — `https://<your-ha-domain>/api/webhook/<webhook-id>` through Nabu Casa or any reverse proxy already pointed at Home Assistant (locally, `http://<ha-host>:8123/api/webhook/<webhook-id>`). For clients on the same network, the server is also reachable directly at `http://<ha-ip>:9584/private_<random>`.
@@ -354,7 +354,7 @@ ha-mcp is a standalone server built for **configuring, building, and debugging**
 ## 🔌 Custom Component (ha_mcp_tools) — File & YAML Services
-The **HA-MCP Custom Component** also powers a set of privileged tools that standard Home Assistant APIs can't provide: file system access and YAML config editing. (The same component runs the full server in-process — that's the recommended install in the **Get Started** section at the top.) Its **File & YAML services entry** (**HA-MCP File & YAML Tools**) enables the tools below.
+The **HA-MCP integration** also powers a set of privileged tools that standard Home Assistant APIs can't provide: file system access and YAML config editing. (The same component runs the full server in-process — that's the recommended install in the **Get Started** section at the top.) Its **File & YAML services entry** (**HA-MCP File & YAML Tools**) enables the tools below.
 **Tools that require the component:**
@@ -372,13 +372,13 @@ These tools also require beta feature flags. See **[Beta Features](docs/beta.md)
 ### Install
-Install the **HA-MCP File & YAML Tools** entry from the same **HA-MCP Custom Component**:
+Install the **HA-MCP File & YAML Tools** entry from the same **HA-MCP integration**:
 [![Open your Home Assistant instance and open a repository inside the Home Assistant Community Store.](https://my.home-assistant.io/badges/hacs_repository.svg)](https://my.home-assistant.io/redirect/hacs_repository/?owner=homeassistant-ai&repository=ha-mcp&category=integration)
-To add manually on Home Assistant 2026.10 or older: open **HACS** > **Integrations** > three-dot menu > **Custom repositories** > add `https://github.com/homeassistant-ai/ha-mcp` (category: Integration) > **Download**. On 2026.11 or newer: in **Marketplace**, accept the first-run warning and **Connect GitHub**, then **Add from link** > `https://github.com/homeassistant-ai/ha-mcp` as an **Integration** > **Install**. Or copy `custom_components/ha_mcp_tools/` from this repository into your HA `config/custom_components/` directory.
+Requires **Home Assistant 2026.8.0 or newer** through HACS or the Marketplace; see [compatibility details](docs/in-process-server.md#requirements) for manual installs. On Home Assistant 2026.8–2026.10: open **HACS**, search for **HA-MCP**, and **Download**. On 2026.11 or newer: open **Marketplace**, accept the first-run warning, search for **HA-MCP**, and **Install**. The main repository is in the default catalog for both. Or copy `custom_components/ha_mcp_tools/` from this repository into your HA `config/custom_components/` directory.
-After installing, restart Home Assistant, then open **Settings** > **Devices & Services** > **Add Integration**, search for **HA-MCP Custom Component**, and add the **HA-MCP File & YAML Tools** entry.
+After installing, restart Home Assistant, then open **Settings** > **Devices & Services** > **Add Integration**, search for **HA-MCP**, and add the **HA-MCP File & YAML Tools** entry.
 To run the full ha-mcp server in-process through this same component, see the **Get Started** section at the top and the [full in-process server documentation →](docs/in-process-server.md).

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/README.md RENAMED Viewed

@@ -3,7 +3,7 @@
 <div align="center">
   <img src="https://raw.githubusercontent.com/homeassistant-ai/ha-mcp/master/docs/img/ha-mcp-logo.png" alt="Home Assistant MCP Server Logo" width="300"/>
-  # The Unofficial and Awesome Home Assistant MCP Server
+  # HA-MCP — Manage Home Assistant with AI
   <!-- mcp-name: io.github.homeassistant-ai/ha-mcp -->
@@ -21,8 +21,7 @@
   </p>
   <p align="center">
-    <em>A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with Home Assistant.<br>
-    Using natural language, control smart home devices, query states, execute services and manage your automations.</em>
+    <em>Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.</em>
   </p>
 </div>
@@ -34,7 +33,7 @@
 ## 🚀 Get Started
-The recommended way to run ha-mcp is the **HA-MCP Custom Component**. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server **in-process**, and works on **every** Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
+The recommended way to run ha-mcp is the **HA-MCP integration**. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server **in-process**, and works on **every** Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
 **Add it to Home Assistant via HACS or, on Home Assistant 2026.11+, the Marketplace (the preferred install):**
@@ -44,13 +43,14 @@ The recommended way to run ha-mcp is the **HA-MCP Custom Component**. It install
 > The setup below is for version 9.0.0 (October 28, 2026) and later; earlier versions show a shorter setup form without the administrator account step.
-1. Install the **HA-MCP Custom Component**. On **Home Assistant 2026.10 or older**, from HACS — click the badge above, or in HACS open **Integrations → ⋮ → Custom repositories**, add `https://github.com/homeassistant-ai/ha-mcp` (category: **Integration**), then **Download**.
-   On **Home Assistant 2026.11 or newer**, HACS is built in as the **Marketplace**: open **Settings → Marketplace** and accept its first-run warning, then **Connect GitHub** (a device sign-in). Adding a custom repository needs it, and until HA-MCP is in the Marketplace catalog it is also what makes the Marketplace check HA-MCP for updates in the background; without it, **Refresh information** on HA-MCP's Marketplace page checks by hand. Then click the badge above, or open the **Add from link** tab and add `https://github.com/homeassistant-ai/ha-mcp` as an **Integration**, and **Install**.
-   Already installed from the earlier `homeassistant-ai/ha-mcp-integration` repository? It keeps receiving the same releases; nothing to change.
+1. Install the **HA-MCP integration** (requires **Home Assistant 2026.8.0 or newer**; see [compatibility details](docs/in-process-server.md#requirements)). On **Home Assistant 2026.8–2026.10**, open HACS, search for **HA-MCP**, then **Download**.
+   On **Home Assistant 2026.11 or newer**, open **Settings → Marketplace**, accept its first-run warning, and search for **HA-MCP**, then **Install**. HA-MCP is in the default catalog, so installing it and receiving its updates do not require connecting GitHub or adding a custom repository. The badge above also opens its catalog page.
+   Already installed from the earlier `homeassistant-ai/ha-mcp-integration` repository? It keeps receiving the same releases. On the Marketplace, keep GitHub connected for its background checks on that custom repository.
+   Older installed releases may still appear as **HA-MCP Custom Component**; searching for **HA-MCP** matches both names.
 2. **Restart Home Assistant.**
 3. Decide which administrator account the server acts as. Either create a long-lived access token on your own account (your profile → **Security** → **Long-lived access tokens** → **Create token**; it works from anywhere if it leaks, and the server's changes show under your name), or, safer, create an account just for HA-MCP under **Settings → People → Add person** with **Allow login**, **Local access only** and **Administrator** on. Never use your own login for the second option.
-4. Go to **Settings → Devices & Services → Add Integration**, search for **HA-MCP Custom Component** and choose **HA-MCP Server**. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — **Remote access through Home Assistant** (start with **Secret URL**, the simplest; **Home Assistant sign-in** adds a login) and/or **Network access: Local network** — then click **Submit**. Both start disabled, so a client on another device needs one of them.
-5. Copy the connect URL from the entry's **Configure** screen (**Settings → Devices & Services → HA-MCP Custom Component → HA-MCP Server → Configure**). A notification confirms the server started and points you there.
+4. Go to **Settings → Devices & Services → Add Integration**, search for **HA-MCP** and choose **HA-MCP Server**. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — **Remote access through Home Assistant** (start with **Secret URL**, the simplest; **Home Assistant sign-in** adds a login) and/or **Network access: Local network** — then click **Submit**. Both start disabled, so a client on another device needs one of them.
+5. Copy the connect URL from the entry's **Configure** screen (**Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” → HA-MCP Server → Configure**). A notification confirms the server started and points you there.
 6. Paste that URL into your AI client — done.
 **Connect URL.** The Configure screen gives you a Home Assistant webhook URL for remote clients — `https://<your-ha-domain>/api/webhook/<webhook-id>` through Nabu Casa or any reverse proxy already pointed at Home Assistant (locally, `http://<ha-host>:8123/api/webhook/<webhook-id>`). For clients on the same network, the server is also reachable directly at `http://<ha-ip>:9584/private_<random>`.
@@ -293,7 +293,7 @@ ha-mcp is a standalone server built for **configuring, building, and debugging**
 ## 🔌 Custom Component (ha_mcp_tools) — File & YAML Services
-The **HA-MCP Custom Component** also powers a set of privileged tools that standard Home Assistant APIs can't provide: file system access and YAML config editing. (The same component runs the full server in-process — that's the recommended install in the **Get Started** section at the top.) Its **File & YAML services entry** (**HA-MCP File & YAML Tools**) enables the tools below.
+The **HA-MCP integration** also powers a set of privileged tools that standard Home Assistant APIs can't provide: file system access and YAML config editing. (The same component runs the full server in-process — that's the recommended install in the **Get Started** section at the top.) Its **File & YAML services entry** (**HA-MCP File & YAML Tools**) enables the tools below.
 **Tools that require the component:**
@@ -311,13 +311,13 @@ These tools also require beta feature flags. See **[Beta Features](docs/beta.md)
 ### Install
-Install the **HA-MCP File & YAML Tools** entry from the same **HA-MCP Custom Component**:
+Install the **HA-MCP File & YAML Tools** entry from the same **HA-MCP integration**:
 [![Open your Home Assistant instance and open a repository inside the Home Assistant Community Store.](https://my.home-assistant.io/badges/hacs_repository.svg)](https://my.home-assistant.io/redirect/hacs_repository/?owner=homeassistant-ai&repository=ha-mcp&category=integration)
-To add manually on Home Assistant 2026.10 or older: open **HACS** > **Integrations** > three-dot menu > **Custom repositories** > add `https://github.com/homeassistant-ai/ha-mcp` (category: Integration) > **Download**. On 2026.11 or newer: in **Marketplace**, accept the first-run warning and **Connect GitHub**, then **Add from link** > `https://github.com/homeassistant-ai/ha-mcp` as an **Integration** > **Install**. Or copy `custom_components/ha_mcp_tools/` from this repository into your HA `config/custom_components/` directory.
+Requires **Home Assistant 2026.8.0 or newer** through HACS or the Marketplace; see [compatibility details](docs/in-process-server.md#requirements) for manual installs. On Home Assistant 2026.8–2026.10: open **HACS**, search for **HA-MCP**, and **Download**. On 2026.11 or newer: open **Marketplace**, accept the first-run warning, search for **HA-MCP**, and **Install**. The main repository is in the default catalog for both. Or copy `custom_components/ha_mcp_tools/` from this repository into your HA `config/custom_components/` directory.
-After installing, restart Home Assistant, then open **Settings** > **Devices & Services** > **Add Integration**, search for **HA-MCP Custom Component**, and add the **HA-MCP File & YAML Tools** entry.
+After installing, restart Home Assistant, then open **Settings** > **Devices & Services** > **Add Integration**, search for **HA-MCP**, and add the **HA-MCP File & YAML Tools** entry.
 To run the full ha-mcp server in-process through this same component, see the **Get Started** section at the top and the [full in-process server documentation →](docs/in-process-server.md).

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/pyproject.toml RENAMED Viewed

@@ -4,8 +4,8 @@ build-backend = "uv_build"
 [project]
 name = "ha-mcp-dev"
-version = "9.1.1.dev3382"
-description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
+version = "9.1.1.dev3389"
+description = "Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants."
 readme = "README.md"
 requires-python = ">=3.13,<3.15"
 license = "MIT"

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/pyproject.toml.orig RENAMED Viewed

@@ -4,8 +4,8 @@ build-backend = "uv_build"
 [project]
 name = "ha-mcp-dev"
-version = "9.1.1.dev3382"
-description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
+version = "9.1.1.dev3389"
+description = "Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants."
 readme = "README.md"
 # Upper bound widened to <3.15 so the package installs on Home Assistant's
 # interpreter when run in-process by the ha_mcp_tools component (HA

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/hacs_auto_refresh.py RENAMED Viewed

@@ -1,12 +1,11 @@
 """Ask HACS to surface the paired component update after a server update (opt-in).
-HACS refreshes a *custom* repository's release data from GitHub only about
-every 48 hours, and the Marketplace that replaces it in Home Assistant 2026.11
-only when a GitHub account is connected. The ha_mcp_tools component ships in
-lockstep with each server release, so a component update can go unnoticed for
-days, or for good. This module closes that gap for every install, the embedded
-server included. It goes away once ha-mcp is in the default catalog, which the
-Marketplace refreshes every 6 hours.
+The main repository is already in the HACS and Marketplace default catalog.
+An external server can update before the store's next scheduled metadata
+refresh, leaving its paired integration update undiscovered. This optional
+startup nudge asks for fresh repository information sooner, for installed
+main-repository entries and existing legacy-mirror entries alike. It is not
+required for catalog installation and never installs an update itself.
 On startup, when the server version changed since the last recorded nudge (the
 just-updated case) or a newer release is pending, it sends the store's "Update

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/redaction.py RENAMED Viewed

@@ -11,13 +11,14 @@ surfaces stop returning operator secrets verbatim:
    entry are never touched, and option names are never guessed at. The only
    name-based match is the operator's own ``redact_app_option_keys`` list;
    listed options and PEM private-key values are treated as password fields.
-2. **Integration options** (``ha_get_integration``): fields the
-   options-flow schema marks with a password text selector are replaced the
-   same way, on both the harvested options and the ``include_schema=True``
-   fields (whose current value comes from the form's ``suggested_value``).
-   Stored option values are checked against the flow's first form only,
-   so a password field that only a later form declares is not detected
-   in them.
+2. **Integration options** (``ha_get_integration``): only an options flow's
+   form marks the password fields, and a read opens that flow only for
+   ``include_schema=True`` (#2987). A read without it replaces every option
+   value of an entry that has an options flow with the sentinel. With it,
+   the fields the form marks with a password text selector are replaced the
+   same way, in the options and in the form's ``current`` values. Stored
+   option values are checked against the flow's first form only, so a
+   password field that only a later form declares is not detected in them.
 3. **Every other tool response**: secret values seen while serving 1 and 2
    are remembered in a process-local known-secrets set, and
    :class:`RedactSecretsMiddleware` (registered just outside the

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/settings_ui/locales/en.json RENAMED Viewed

@@ -324,7 +324,7 @@
     "backup.bulk.in_use": "{count} backup(s) are in use. Retry after the active capture or restore finishes.",
     "backup.bulk.unknown": "The deletion result could not be confirmed. Check the backup list before retrying.",
     "filesystem.custom.title": "Custom filesystem paths (advanced)",
-    "filesystem.custom.help": "Extra paths (one per line) that file tools may <strong>read and write</strong>. Config-relative paths, including exact filenames such as <code>sensor.yaml</code>, and paths under <code>/share</code>, <code>/media</code>, and <code>/ssl</code> (read-only on HAOS and Supervised) are supported. Each entry allows that path and anything below it. Entries are matched literally; wildcards such as <code>*</code> are not supported. You can also manage these paths in Home Assistant under Settings → Devices & Services → HA-MCP Custom Component → HA-MCP File & YAML Tools → Configure; both locations edit the same setting and apply changes immediately.",
+    "filesystem.custom.help": "Extra paths (one per line) that file tools may <strong>read and write</strong>. Config-relative paths, including exact filenames such as <code>sensor.yaml</code>, and paths under <code>/share</code>, <code>/media</code>, and <code>/ssl</code> (read-only on HAOS and Supervised) are supported. Each entry allows that path and anything below it. Entries are matched literally; wildcards such as <code>*</code> are not supported. You can also manage these paths in Home Assistant under Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” (“HA-MCP Custom Component” on older installs) → HA-MCP File & YAML Tools → Configure; both locations edit the same setting and apply changes immediately.",
     "filesystem.custom.blocked": "Always blocked: {paths}, path traversal (<code>..</code>), and absolute paths outside allowed HAOS volumes.",
     "filesystem.custom.enable_first": "Enable beta features and filesystem tools above to edit.",
     "filesystem.custom.unavailable": "Custom paths are currently unavailable.",
@@ -476,7 +476,7 @@
     "advanced.enable_history_query_guardrails.label": "History query guardrails",
     "advanced.enable_history_query_guardrails.help": "Reject recorder queries that exceed conservative entity and time-range budgets. Disabled by default.",
     "advanced.hacs_refresh_after_update.label": "Refresh the component in HACS after an update",
-    "advanced.hacs_refresh_after_update.help": "At startup after a server update, ask HACS (the Marketplace on Home Assistant 2026.11+) to re-check the HA-MCP Custom Component repository, so its matching update shows right away instead of at the next 48-hour check. Off by default; installs that already did this keep it on.",
+    "advanced.hacs_refresh_after_update.help": "At startup after a server update, ask HACS (the Marketplace on Home Assistant 2026.11+) to re-check the HA-MCP repository, so its matching update shows right away instead of waiting for the next background check. Off by default; installs that already did this keep it on.",
     "advanced.ha_tool_concurrency.label": "Home Assistant tool concurrency",
     "advanced.ha_tool_concurrency.help": "Optional limit on outer Home Assistant tool calls across all sessions. Internal REST, WebSocket, and per-tool fan-out concurrency is unchanged. 0 keeps unlimited behavior. A call waiting for capacity fails after 60 seconds.",
     "advanced.dashboard_screenshot_engine_url.label": "Dashboard screenshot engine URL",

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/settings_ui/settings_js/04_backups.js RENAMED Viewed

@@ -197,7 +197,7 @@ function renderFsCustomPathsSubForm(parentEl, masterOn, fsOn) {
       : '.storage, secrets.yaml';
   info.innerHTML =
     `<div class="feature-name">${escapeHtml(t('filesystem.custom.title', {}, 'Custom filesystem paths (advanced)'))}</div>` +
-    `<div class="feature-help">${tHtml('filesystem.custom.help', {}, 'Extra paths (one per line) that file tools may <strong>read and write</strong>. Config-relative paths, including exact filenames such as <code>sensor.yaml</code>, and paths under <code>/share</code>, <code>/media</code>, and <code>/ssl</code> (read-only on HAOS and Supervised) are supported. Each entry allows that path and anything below it. Entries are matched literally; wildcards such as <code>*</code> are not supported. You can also manage these paths in Home Assistant under Settings → Devices & Services → HA-MCP Custom Component → HA-MCP File & YAML Tools → Configure; both locations edit the same setting and apply changes immediately.')}</div>` +
+    `<div class="feature-help">${tHtml('filesystem.custom.help', {}, 'Extra paths (one per line) that file tools may <strong>read and write</strong>. Config-relative paths, including exact filenames such as <code>sensor.yaml</code>, and paths under <code>/share</code>, <code>/media</code>, and <code>/ssl</code> (read-only on HAOS and Supervised) are supported. Each entry allows that path and anything below it. Entries are matched literally; wildcards such as <code>*</code> are not supported. You can also manage these paths in Home Assistant under Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” (“HA-MCP Custom Component” on older installs) → HA-MCP File & YAML Tools → Configure; both locations edit the same setting and apply changes immediately.')}</div>` +
     `<div class="feature-help">${tHtml('filesystem.custom.blocked', {paths: `<code>${escapeHtml(denyList)}</code>`}, 'Always blocked: {paths}, path traversal (<code>..</code>), and absolute paths outside allowed HAOS volumes.')}</div>`;
   const control = document.createElement('div');

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/tools/config_entry_flow.py RENAMED Viewed

@@ -738,8 +738,9 @@ COMPONENT_DOMAIN = "ha_mcp_tools"
 COMPONENT_ENTRY_SUGGESTIONS: tuple[str, ...] = (
     "Manage it in the Home Assistant UI: Settings > Devices & services > "
-    + "HA-MCP Custom Component (Configure for options; the entry's menu for "
-    + "enable/disable, delete and debug logging).",
+    + "“HA-MCP — Manage Home Assistant with AI” (listed as “HA-MCP Custom Component” "
+    + "on older installs). Choose Configure for options; use the entry's menu for "
+    + "enable/disable, delete and debug logging.",
     "Server settings and updates: with developer mode on, "
     + "ha_dev_manage_settings / ha_dev_manage_server.",
 )

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/tools/dashboard_card_describe.py RENAMED Viewed

@@ -121,7 +121,7 @@ async def describe_card_response(client: Any, card_type: str | None) -> dict[str
                 "with dashboard card support.",
                 suggestions=[
                     (
-                        "Install or update the HA-MCP Custom Component through "
+                        "Install or update the HA-MCP integration through "
                         "HACS (the Marketplace on Home Assistant 2026.11+)"
                     ),
                     "Restart Home Assistant after the update completes",

{ha_mcp_dev-9.1.1.dev3382 → ha_mcp_dev-9.1.1.dev3389}/src/ha_mcp/tools/helper_flows.py RENAMED Viewed

@@ -2,10 +2,11 @@
 ``flow_handlers?type=helper`` lists Core's own helper flows plus custom
 integrations of ``integration_type: "helper"`` — the list the HA UI offers under
-"Create helper". Cached per client for a few minutes so a tool call does not pay
-a REST round-trip each time; a type missing from a cached copy is re-read once
-before it counts as unlisted (``listed_helper_flows``), so a newly installed helper
-integration is found.
+"Create helper". ``integration/descriptions`` tells Core's own apart from the
+custom ones (``core_helper_domains``). Both are cached per client for a few
+minutes so a tool call does not pay a round-trip each time; a type missing from
+a cached copy is re-read once before it counts as unlisted
+(``listed_helper_flows``), so a newly installed helper integration is found.
 """
 from __future__ import annotations
@@ -16,15 +17,18 @@ from typing import Any, NoReturn
 from ha_mcp._vendor.fastmcp.exceptions import ToolError
-from ..client.rest_client import HomeAssistantConnectionError
+from ..client.rest_client import (
+    HomeAssistantAdminRequiredError,
+    HomeAssistantConnectionError,
+)
 from ..errors import ErrorCode, create_error_response
 from .config_helpers.schemas import SIMPLE_HELPER_TYPES
 from .helpers import exception_to_structured_error, raise_tool_error
 _TTL_SECONDS = 300.0
-_CACHE: weakref.WeakKeyDictionary[Any, tuple[float, frozenset[str]]] = (
-    weakref.WeakKeyDictionary()
-)
+_Cache = weakref.WeakKeyDictionary[Any, tuple[float, frozenset[str]]]
+_CACHE: _Cache = weakref.WeakKeyDictionary()
+_CORE_CACHE: _Cache = weakref.WeakKeyDictionary()
 async def _fetch_helper_flow_types(client: Any) -> frozenset[str]:
@@ -41,9 +45,37 @@ async def _fetch_helper_flow_types(client: Any) -> frozenset[str]:
     return frozenset(str(domain) for domain in domains)
-def _cached(client: Any) -> frozenset[str] | None:
+async def _fetch_core_helper_domains(client: Any) -> frozenset[str]:
+    """Core's own helper flows: the ``core.helper`` domains of
+    ``integration/descriptions``, the frontend's integration catalog.
+    The command is admin-only, and only a REST 401 latches the client's
+    refused-admin-route flag, so the token is checked first: a non-admin
+    token is refused here, which is what tells the search to name the token.
+    """
+    if await client.token_is_admin() is False:
+        raise HomeAssistantAdminRequiredError(
+            "integration/descriptions is admin-only in Home Assistant and this "
+            "token's user is not an administrator"
+        )
+    answer = await client.send_websocket_message({"type": "integration/descriptions"})
+    result = answer.get("result") if isinstance(answer, dict) else None
+    helpers = (
+        (result or {}).get("core", {}).get("helper")
+        if isinstance(result, dict)
+        else None
+    )
+    if not isinstance(helpers, dict):
+        raise HomeAssistantConnectionError(
+            "integration/descriptions returned an unexpected response shape: "
+            f"{answer!r}"[:300]
+        )
+    return frozenset(str(domain) for domain in helpers)
+def _cached(cache: _Cache, client: Any) -> frozenset[str] | None:
     try:
-        cached = _CACHE.get(client)
+        cached = cache.get(client)
     except TypeError:
         return None
     if cached is not None and time.monotonic() - cached[0] < _TTL_SECONDS:
@@ -51,23 +83,34 @@ def _cached(client: Any) -> frozenset[str] | None:
     return None
-async def helper_flow_types(client: Any, *, refresh: bool = False) -> frozenset[str]:
-    """The helper types the connected Home Assistant offers as config flows."""
-    cached = None if refresh else _cached(client)
+async def _read(
+    cache: _Cache, fetch: Any, client: Any, *, refresh: bool
+) -> frozenset[str]:
+    cached = None if refresh else _cached(cache, client)
     if cached is not None:
         return cached
-    types = await _fetch_helper_flow_types(client)
+    domains: frozenset[str] = await fetch(client)
     try:
-        _CACHE[client] = (time.monotonic(), types)
+        cache[client] = (time.monotonic(), domains)
     except TypeError:  # a client that cannot be weakly referenced is not cached
         pass
-    return types
+    return domains
+async def helper_flow_types(client: Any, *, refresh: bool = False) -> frozenset[str]:
+    """The helper types the connected Home Assistant offers as config flows."""
+    return await _read(_CACHE, _fetch_helper_flow_types, client, refresh=refresh)
+async def core_helper_domains(client: Any) -> frozenset[str]:
+    """The helper flows that are Home Assistant's own, not a custom integration's."""
+    return await _read(_CORE_CACHE, _fetch_core_helper_domains, client, refresh=False)
 async def listed_helper_flows(client: Any, name: str) -> frozenset[str]:
     """The helper flow list, re-read once when ``name`` is missing from a cached
     copy (a fresh read is not repeated)."""
-    cached = _cached(client)
+    cached = _cached(_CACHE, client)
     if cached is not None and name in cached:
         return cached
     return await helper_flow_types(client, refresh=cached is not None)

ha-mcp-dev 9.1.1.dev3382__tar.gz → 9.1.1.dev3389__tar.gz

ha-mcp-dev 9.1.1.dev3382tar.gz → 9.1.1.dev3389tar.gz