ha-mcp-dev 7.6.0.dev669__tar.gz → 7.6.0.dev671__tar.gz

{ha_mcp_dev-7.6.0.dev669/src/ha_mcp_dev.egg-info → ha_mcp_dev-7.6.0.dev671}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.6.0.dev669
+Version: 7.6.0.dev671
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT

{ha_mcp_dev-7.6.0.dev669 → ha_mcp_dev-7.6.0.dev671}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "7.6.0.dev669"
+version = "7.6.0.dev671"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 requires-python = ">=3.13,<3.14"

{ha_mcp_dev-7.6.0.dev669 → ha_mcp_dev-7.6.0.dev671}/src/ha_mcp/tools/tools_hacs.py

@@ -704,6 +704,21 @@ HACS_REPO_BACKSTOP_POLL_INTERVAL = 5.0
 # 30 s resolve budget does not apply here.
 HACS_ADD_REGISTRATION_TIMEOUT = 10.0
 
+# Wall-clock budget for ``_resolve_hacs_repo_id`` (the ``owner/repo`` lookup
+# behind read-only ``ha_get_hacs_info(action="info")`` and
+# ``ha_manage_hacs(action="download")``). Unlike ``ha_install_mcp_tools`` —
+# which adds a repo and then waits the full ``HACS_REPO_REGISTRATION_TIMEOUT``
+# for that fresh registration to land — a plain info/download lookup targets a
+# repo that should ALREADY be in HACS's index: default repos always are, and
+# ``add_repository`` blocks until registration is confirmed before returning.
+# So the post-subscribe sample resolves an existing repo instantly, and the
+# dispatch-signal wait only ever burns wall-clock when the repo is genuinely
+# absent. The old 30 s budget made every not-found lookup a 30 s stall (the
+# dominant cost in the HAOS E2E suite per #1515); 10 s still leaves event-driven
+# headroom for the rare mid-registration race while failing a genuinely-missing
+# lookup ~3x faster.
+HACS_RESOLVE_REGISTRATION_TIMEOUT = 10.0
+
 
 async def _find_repo_in_list_by_full_name(
     ws_client: Any, full_name_lower: str
@@ -919,7 +934,9 @@ async def _resolve_hacs_repo_id(ws_client: Any, repository_id: str) -> tuple[str
     if "/" not in repository_id:
         return repository_id, repository_id
 
-    repo = await wait_for_repo_registration(ws_client, repository_id)
+    repo = await wait_for_repo_registration(
+        ws_client, repository_id, timeout=HACS_RESOLVE_REGISTRATION_TIMEOUT
+    )
 
     if repo is not None:
         return str(repo.get("id")), repo.get("name") or repository_id

{ha_mcp_dev-7.6.0.dev669 → ha_mcp_dev-7.6.0.dev671}/src/ha_mcp/tools/tools_service.py

@@ -93,10 +93,16 @@ _STATE_CHANGING_SERVICES = {
     "media_stop",
 }
 
-# Domains where service calls don't produce entity state changes
+# Domains where a service call does not move the TARGET entity's own primary
+# state to a value the verifier can wait for. ``scene`` belongs here with
+# ``automation``/``script``: activating a scene changes the member entities,
+# but the scene entity's own state is a last-activated timestamp that never
+# becomes "on"/"off" — so waiting for ``turn_on`` -> "on" always times out and
+# only appends a spurious "could not be verified" warning (~10s wasted).
 _NON_STATE_CHANGING_DOMAINS = {
     "automation",
     "script",
+    "scene",
     "homeassistant",
     "notify",
     "tts",

{ha_mcp_dev-7.6.0.dev669 → ha_mcp_dev-7.6.0.dev671/src/ha_mcp_dev.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.6.0.dev669
+Version: 7.6.0.dev671
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT