PyPI - ha-mcp-dev - Versions diffs - 9.1.0.dev3274__tar.gz → 9.1.0.dev3279__tar.gz - Mend

ha-mcp-dev 9.1.0.dev3274tar.gz → 9.1.0.dev3279tar.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 (827) hide show

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 9.1.0.dev3274
+Version: 9.1.0.dev3279
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Keywords: mcp,home-assistant,ai,automation,smart-home
 Author: Julien

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 [project]
 name = "ha-mcp-dev"
-version = "9.1.0.dev3274"
+version = "9.1.0.dev3279"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 requires-python = ">=3.13,<3.15"

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/pyproject.toml.orig RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 [project]
 name = "ha-mcp-dev"
-version = "9.1.0.dev3274"
+version = "9.1.0.dev3279"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 # Upper bound widened to <3.15 so the package installs on Home Assistant's

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/client/rest_client.py RENAMED Viewed

@@ -1959,8 +1959,8 @@ class HomeAssistantClient:
         for attempt in range(max_retries):
             # Whether the failure happened before a usable connection existed.
             # Failing to obtain one is transport death whatever class the
-            # manager raises, and it raises a bare ``Exception`` when
-            # ``connect()`` returns False, so this cannot be decided by type.
+            # manager raises; an auth failure or the pool-lock guard's bare
+            # ``Exception`` is not a connection error; type cannot decide this.
             acquiring = True
             try:
                 # Use per-client WebSocket keyed to this client's credentials
@@ -1999,10 +1999,10 @@ class HomeAssistantClient:
                     continue
                 # Phase first, type second. Failing before a client exists is
-                # evidence about the transport whatever class was raised, and
-                # the pooled manager raises a bare ``Exception`` when
-                # ``connect()`` returns False, so that case cannot be decided
-                # by type. Past acquisition only the no-answer classes count:
+                # evidence about the transport whatever class was raised; an
+                # auth failure or the pool-lock guard's bare ``Exception`` is not
+                # a no-answer class, so that case cannot be decided by type.
+                # Past acquisition only the no-answer classes count:
                 # ``send_command`` deliberately re-raises the original
                 # ``ConnectionClosed`` / ``ConnectionResetError`` from the send
                 # rather than wrapping it, to keep at-most-once semantics for

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/az.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Uğursuz REST zəngi üçün yenidən cəhd büdcəsi.",
     "advanced.verify_ssl.label": "TLS sertifikatlarını yoxlayın",
     "advanced.verify_ssl.help": "Home Assistant serverinin TLS sertifikatını yoxlayın. Bunu yalnız etibarlı şəbəkədə, özünü imzalayan sertifikat və ya host adı uyğunsuzluğu üçün söndürün: o, nəqliyyat təhlükəsizliyini zəiflədir.",
+    "advanced.ipv6_allowed_networks.label": "İcazə verilən əlavə IPv6 şəbəkələri",
+    "advanced.ipv6_allowed_networks.help": "IPv6 klientləri bu serverin öz portuna yalnız yerli şəbəkədən daxil olur: loopback, link-local, unique local (fc00::/7) və Home Assistant hostunun birbaşa qoşulduğu şəbəkələr. IPv4 təsirlənmir. İcazə vermək üçün digər IPv6 şəbəkələrini vergül və ya yeni sətirlərlə ayıraraq siyahıya daxil edin (məsələn, 2001:db8:5::/48). ::/0 əlavə etmək marşrutlaşdırıcınız daxil olan IPv6 trafikinə icazə verərsə, internetdən gələnlər də daxil olmaqla bütün IPv6 klientlərinə icazə verir.",
     "advanced.fuzzy_threshold.label": "Qeyri-səlis axtarış həddi",
     "advanced.fuzzy_threshold.help": "Aşağı qiymətlər daha sərbəst obyekt uyğunlaşmasına imkan verir.",
     "advanced.automation_config_time_budget.label": "Avtomatlaşdırma konfiqurasiyaları üçün vaxt limiti (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/cs.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Rozpočet na opakování pro každé selhání volání REST.",
     "advanced.verify_ssl.label": "Ověřit certifikáty TLS",
     "advanced.verify_ssl.help": "Ověřit certifikát TLS serveru Home Assistant. Vypněte tuto možnost pouze v důvěryhodné síti pro autorsky podepsaný certifikát nebo neshodu názvů hostitelů: oslabuje to zabezpečení přenosu.",
+    "advanced.ipv6_allowed_networks.label": "Další povolené sítě IPv6",
+    "advanced.ipv6_allowed_networks.help": "Klienti IPv6 přistupují k vlastnímu portu tohoto serveru pouze z lokální sítě: loopback, link-local, unique local (fc00::/7) a sítí, ke kterým je hostitel Home Assistant přímo připojen. IPv4 to neovlivňuje. Uveďte další sítě IPv6, které chcete povolit, oddělené čárkami nebo novými řádky (například 2001:db8:5::/48). Přidáním ::/0 povolíte všechny klienty IPv6, včetně přístupu z internetu, pokud váš router propouští příchozí provoz IPv6.",
     "advanced.fuzzy_threshold.label": "Prahová hodnota fuzzy vyhledávání",
     "advanced.fuzzy_threshold.help": "Nižší hodnoty umožňují volnější shodu entit.",
     "advanced.automation_config_time_budget.label": "Časový rozpočet konfigurace automatizace (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/de.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Wiederholungsbudget pro fehlgeschlagenem REST-Aufruf.",
     "advanced.verify_ssl.label": "TLS-Zertifikate überprüfen",
     "advanced.verify_ssl.help": "Überprüfe das TLS-Zertifikat des Home Assistant-Servers. Deaktiviere dies nur in einem vertrauenswürdigen Netzwerk, für ein selbstsigniertes Zertifikat oder bei einer Hostnamen-Abweichung: Dies schwächt die Transportsicherheit.",
+    "advanced.ipv6_allowed_networks.label": "Zusätzliche erlaubte IPv6-Netzwerke",
+    "advanced.ipv6_allowed_networks.help": "IPv6-Clients erreichen den Port dieses Servers nur aus dem lokalen Netzwerk: Loopback, Link-Local, Unique Local (fc00::/7) und die Netzwerke, mit denen der Home Assistant-Host direkt verbunden ist. IPv4 ist nicht betroffen. Liste weitere erlaubte IPv6-Netzwerke auf, getrennt durch Kommas oder neue Zeilen (zum Beispiel 2001:db8:5::/48). Das Hinzufügen von ::/0 erlaubt jeden IPv6-Client, einschließlich aus dem Internet, wenn dein Router eingehenden IPv6-Verkehr durchlässt.",
     "advanced.fuzzy_threshold.label": "Fuzzy-Such-Schwellenwert",
     "advanced.fuzzy_threshold.help": "Niedrigere Werte erlauben einen großzügigeren Entitätsabgleich.",
     "advanced.automation_config_time_budget.label": "Automatisierungskonfigurations-Zeitbudget (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/eo.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Buĝeto de reprovoj po malsukcesa REST-voko.",
     "advanced.verify_ssl.label": "Konfirmi TLS-atestilojn",
     "advanced.verify_ssl.help": "Konfirmi la TLS-atestilon de la servilo de Home Assistant. Malŝaltu ĉi tion nur ĉe fidinda reto, por memsubskribita atestilo aŭ mita gastnomo: ĝi malfortigas transportan sekurecon.",
+    "advanced.ipv6_allowed_networks.label": "Kromaj permesitaj retoj IPv6",
+    "advanced.ipv6_allowed_networks.help": "Klientoj IPv6 atingas la propran pordon de ĉi tiu servilo nur el la loka reto: loka buko, liglokala, unika loka (fc00::/7) kaj la retoj al kiuj la gastiganto de Home Assistant estas rekte konektita. IPv4 ne estas tuŝita. Listigu aliajn retojn IPv6 por permesi, apartigite per komoj aŭ novaj linioj (ekzemple 2001:db8:5::/48). Aldono de ::/0 permesas ĉiun klienton IPv6, inkluzive de tiu el la interreto se via enkursigilo tralasas envenantajn IPv6.",
     "advanced.fuzzy_threshold.label": "Sojlo de neklara serĉo",
     "advanced.fuzzy_threshold.help": "Pli malaltaj valoroj permesas pli malstriktan entan kongruon.",
     "advanced.automation_config_time_budget.label": "Tempa buĝeto por aŭtomatiga agordo (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/es.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Presupuesto de reintentos por cada llamada REST fallida.",
     "advanced.verify_ssl.label": "Verificar certificados TLS",
     "advanced.verify_ssl.help": "Verificar el certificado TLS del servidor de Home Assistant. Desactiva esto solo en una red de confianza, para un certificado autofirmado o un desajuste de nombre de host: esto debilita la seguridad del transporte.",
+    "advanced.ipv6_allowed_networks.label": "Redes IPv6 adicionales permitidas",
+    "advanced.ipv6_allowed_networks.help": "Los clientes IPv6 llegan al puerto propio de este servidor solo desde la red local: bucle local (loopback), enlace local (link-local), locales únicas (fc00::/7) y las redes a las que el host de Home Assistant está conectado directamente. IPv4 no se ve afectado. Lista otras redes IPv6 para permitir, separadas por comas o saltos de línea (por ejemplo, 2001:db8:5::/48). Agregar ::/0 permite a cualquier cliente IPv6, incluso desde internet si tu router permite tráfico IPv6 entrante.",
     "advanced.fuzzy_threshold.label": "Umbral de la búsqueda difusa",
     "advanced.fuzzy_threshold.help": "Los valores más bajos permiten una coincidencia de entidades más flexible.",
     "advanced.automation_config_time_budget.label": "Presupuesto de tiempo para la configuración de automatizaciones (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/fr.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Budget de nouvelles tentatives par appel REST échoué.",
     "advanced.verify_ssl.label": "Vérifier les certificats TLS",
     "advanced.verify_ssl.help": "Vérifie le certificat TLS du serveur Home Assistant. Ne désactivez cette option que sur un réseau de confiance, pour un certificat auto-signé ou une non-correspondance de nom d'hôte : cela affaiblit la sécurité du transport.",
+    "advanced.ipv6_allowed_networks.label": "Réseaux IPv6 supplémentaires autorisés",
+    "advanced.ipv6_allowed_networks.help": "Les clients IPv6 atteignent le port propre de ce serveur uniquement depuis le réseau local : bouclage (loopback), lien local (link-local), unique local (fc00::/7) et les réseaux auxquels l'hôte Home Assistant est directement connecté. L'IPv4 n'est pas affectée. Listez les autres réseaux IPv6 à autoriser, séparés par des virgules ou des retours à la ligne (par exemple 2001:db8:5::/48). Ajouter ::/0 autorise tous les clients IPv6, y compris depuis Internet si votre routeur laisse passer le trafic IPv6 entrant.",
     "advanced.fuzzy_threshold.label": "Seuil de recherche floue",
     "advanced.fuzzy_threshold.help": "Des valeurs plus faibles permettent une correspondance d'entités plus souple.",
     "advanced.automation_config_time_budget.label": "Budget de temps de configuration d'automatisation (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/it.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Budget di tentativi per chiamata REST non riuscita.",
     "advanced.verify_ssl.label": "Verifica i certificati TLS",
     "advanced.verify_ssl.help": "Verifica il certificato TLS del server Home Assistant. Disattiva questa opzione solo su una rete affidabile, per un certificato autofirmato o una mancata corrispondenza del nome host: indebolisce la sicurezza del trasporto.",
+    "advanced.ipv6_allowed_networks.label": "Reti IPv6 extra consentite",
+    "advanced.ipv6_allowed_networks.help": "I client IPv6 raggiungono la porta di questo server solo dalla rete locale: loopback, link-local, unique local (fc00::/7) e le reti a cui l'host di Home Assistant è direttamente connesso. L'IPv4 non è interessato. Elenca altre reti IPv6 da consentire, separate da virgole o nuove righe (ad esempio 2001:db8:5::/48). L'aggiunta di ::/0 consente qualsiasi client IPv6, anche da Internet se il tuo router lascia passare il traffico IPv6 in ingresso.",
     "advanced.fuzzy_threshold.label": "Soglia della ricerca approssimata",
     "advanced.fuzzy_threshold.help": "Valori più bassi consentono una corrispondenza delle entità meno rigida.",
     "advanced.automation_config_time_budget.label": "Tempo massimo per le configurazioni delle automazioni (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/ko.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "실패한 REST 호출당 재시도 예산.",
     "advanced.verify_ssl.label": "TLS 인증서 확인",
     "advanced.verify_ssl.help": "Home Assistant 서버의 TLS 인증서를 확인합니다. 자체 서명된 인증서나 호스트 이름 불일치의 경우에만 신뢰할 수 있는 네트워크에서 이 기능을 끄십시오. 전송 보안이 약화됩니다.",
+    "advanced.ipv6_allowed_networks.label": "허용할 추가 IPv6 네트워크",
+    "advanced.ipv6_allowed_networks.help": "IPv6 클라이언트는 루프백, 링크 로컬, 고유 로컬(fc00::/7) 및 Home Assistant 호스트가 직접 연결된 네트워크와 같은 로컬 네트워크에서만 이 서버의 자체 포트에 접근할 수 있습니다. IPv4는 영향을 받지 않습니다. 쉼표나 줄바꿈으로 구분하여 허용할 다른 IPv6 네트워크를 나열하세요(예: 2001:db8:5::/48). ::/0을 추가하면 라우터가 인바운드 IPv6를 허용하는 경우 인터넷을 포함한 모든 IPv6 클라이언트가 허용됩니다.",
     "advanced.fuzzy_threshold.label": "유사 검색 임계값",
     "advanced.fuzzy_threshold.help": "낮은 값을 설정할수록 더 느슨한 엔티티 일치가 허용됩니다.",
     "advanced.automation_config_time_budget.label": "자동화 설정 조회 시간 예산(초)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/nl.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Pogingenbudget per mislukte REST-aanroep.",
     "advanced.verify_ssl.label": "TLS-certificaten verifiëren",
     "advanced.verify_ssl.help": "Verifieer het TLS-certificaat van de Home Assistant-server. Schakel dit alleen uit op een vertrouwd netwerk, voor een zelfondertekend certificaat of een hostnaamafwijking: dit verzwakt de transportbeveiliging.",
+    "advanced.ipv6_allowed_networks.label": "Extra toegestane IPv6-netwerken",
+    "advanced.ipv6_allowed_networks.help": "IPv6-clients bereiken de eigen poort van deze server alleen vanuit het lokale netwerk: loopback, link-local, unique local (fc00::/7) en de netwerken waarmee de Home Assistant-host direct is verbonden. IPv4 blijft ongewijzigd. Vermeld andere toe te staan IPv6-netwerken, gescheiden door komma's of nieuwe regels (bijvoorbeeld 2001:db8:5::/48). Het toevoegen van ::/0 staat elke IPv6-client toe, ook vanaf het internet als je router inkomend IPv6 doorlaat.",
     "advanced.fuzzy_threshold.label": "Fuzzy-zoekdrempel",
     "advanced.fuzzy_threshold.help": "Lagere waarden staan lossere entiteitsovereenkomsten toe.",
     "advanced.automation_config_time_budget.label": "Tijdsbudget voor automatiseringsconfiguratie (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/pl.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Budżet ponowień dla nieudanego wywołania REST.",
     "advanced.verify_ssl.label": "Weryfikuj certyfikaty TLS",
     "advanced.verify_ssl.help": "Weryfikuje certyfikat TLS serwera Home Assistant. Wyłącz tę opcję tylko w zaufanej sieci, dla certyfikatu z podpisem własnym lub niezgodności nazwy hosta: osłabia to bezpieczeństwo transportu.",
+    "advanced.ipv6_allowed_networks.label": "Dodatkowe dozwolone sieci IPv6",
+    "advanced.ipv6_allowed_networks.help": "Klienci IPv6 mogą łączyć się z własnym portem tego serwera tylko z sieci lokalnej: loopback, link-local, unique local (fc00::/7) oraz sieci, z którymi host Home Assistant jest bezpośrednio połączony. Protokół IPv4 nie jest tym objęty. Wymień inne sieci IPv6, które chcesz dopuścić, oddzielając je przecinkami lub nowymi liniami (na przykład 2001:db8:5::/48). Dodanie ::/0 zezwala każdemu klientowi IPv6, w tym z internetu, jeśli Twój router przepuszcza ruch przychodzący IPv6.",
     "advanced.fuzzy_threshold.label": "Próg wyszukiwania rozmytego",
     "advanced.fuzzy_threshold.help": "Niższe wartości pozwalają na luźniejsze dopasowywanie encji.",
     "advanced.automation_config_time_budget.label": "Limit czasu konfiguracji automatyzacji (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/ru.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Бюджет повторных попыток для каждого неудачного REST-вызова.",
     "advanced.verify_ssl.label": "Проверять TLS-сертификаты",
     "advanced.verify_ssl.help": "Проверять TLS-сертификат сервера Home Assistant. Отключайте это только в доверенной сети для самоподписанного сертификата или несовпадения имени хоста: это снижает безопасность передачи данных.",
+    "advanced.ipv6_allowed_networks.label": "Дополнительные разрешенные сети IPv6",
+    "advanced.ipv6_allowed_networks.help": "Клиенты IPv6 могут обращаться к собственному порту этого сервера только из локальной сети: loopback, link-local, unique local (fc00::/7) и сетей, к которым напрямую подключен хост Home Assistant. IPv4 это не затрагивает. Перечислите другие разрешенные сети IPv6 через запятую или с новой строки (например, 2001:db8:5::/48). Добавление ::/0 разрешает доступ всем клиентам IPv6, включая интернет, если ваш роутер пропускает входящий трафик IPv6.",
     "advanced.fuzzy_threshold.label": "Порог нечёткого поиска",
     "advanced.fuzzy_threshold.help": "Меньшие значения допускают более нечеткое сопоставление сущностей.",
     "advanced.automation_config_time_budget.label": "Бюджет времени конфигураций автоматизаций (с)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/sv.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "Antal tillåtna försök per misslyckat REST-anrop.",
     "advanced.verify_ssl.label": "Verifiera TLS-certifikat",
     "advanced.verify_ssl.help": "Verifiera Home Assistant-serverns TLS-certifikat. Stäng bara av detta på ett betrott nätverk, för ett självsignerat certifikat eller om värdnamnet inte matchar: det försvagar transportsäkerheten.",
+    "advanced.ipv6_allowed_networks.label": "Extra IPv6-nätverk som tillåts",
+    "advanced.ipv6_allowed_networks.help": "IPv6-klienter når denna servers egen port endast från det lokala nätverket: loopback, link-local, unique local (fc00::/7) och de nätverk som Home Assistant-värden är direkt ansluten till. IPv4 påverkas inte. Lista andra IPv6-nätverk att tillåta, separerade med kommatecken eller nya rader (till exempel 2001:db8:5::/48). Att lägga till ::/0 tillåter alla IPv6-klienter, inklusive från internet om din router släpper igenom inkommande IPv6.",
     "advanced.fuzzy_threshold.label": "Fuzzy-sökningströskel",
     "advanced.fuzzy_threshold.help": "Lägre värden tillåter mer tillåtande entitetsmatchning.",
     "advanced.automation_config_time_budget.label": "Tidsbudget för automatiseringskonfiguration (s)",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/zh-Hans.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "每次失败的 REST 调用的重试预算。",
     "advanced.verify_ssl.label": "验证 TLS 证书",
     "advanced.verify_ssl.help": "验证 Home Assistant 服务器的 TLS 证书。仅在受信任的网络上、针对自签名证书或主机名不匹配的情况关闭此选项：这会削弱传输安全性。",
+    "advanced.ipv6_allowed_networks.label": "允许的额外 IPv6 网络",
+    "advanced.ipv6_allowed_networks.help": "IPv6 客户端仅能从本地网络访问该服务器自身的端口：回环、链路本地、唯一本地（fc00::/7）以及 Home Assistant 主机直接连接的网络。IPv4 不受影响。请列出需要允许的其他 IPv6 网络，以逗号或换行符分隔（例如 2001:db8:5::/48）。添加 ::/0 将允许所有 IPv6 客户端，如果您的路由器允许入站 IPv6 流量，则也包括来自互联网的客户端。",
     "advanced.fuzzy_threshold.label": "模糊搜索阈值",
     "advanced.fuzzy_threshold.help": "较低的值允许更宽松的实体匹配。",
     "advanced.automation_config_time_budget.label": "自动化配置时间预算（秒）",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/settings_ui/locales/zh-Hant.json RENAMED Viewed

@@ -458,6 +458,8 @@
     "advanced.max_retries.help": "每個失敗 REST 呼叫的重試預算。",
     "advanced.verify_ssl.label": "驗證 TLS 憑證",
     "advanced.verify_ssl.help": "驗證 Home Assistant 伺服器的 TLS 憑證。僅在受信賴的網路、針對自簽憑證或主機名稱不符的情況下關閉此功能：這會削弱傳輸安全性。",
+    "advanced.ipv6_allowed_networks.label": "允許的額外 IPv6 網路",
+    "advanced.ipv6_allowed_networks.help": "IPv6 用戶端僅能從本機網路存取此伺服器本身的連接埠：回送（loopback）、鏈路本機（link-local）、唯一本機（fc00::/7）以及 Home Assistant 主機直接連接的網路。IPv4 不受影響。列出要允許的其他 IPv6 網路，以逗號或新行分隔（例如 2001:db8:5::/48）。新增 ::/0 將允許所有 IPv6 用戶端，若您的路由器允許入站 IPv6，也包含來自網際網路的用戶端。",
     "advanced.fuzzy_threshold.label": "模糊搜尋閾值",
     "advanced.fuzzy_threshold.help": "較低的值允許較寬鬆的實體比對。",
     "advanced.automation_config_time_budget.label": "自動化設定時間預算（秒）",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/blueprint_sources.py RENAMED Viewed

@@ -219,7 +219,7 @@ async def _via_component(client: Any, domain: str, path: str) -> _ComponentBody:
             )
         return _NO_COMPONENT_BODY
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → metadata-only
+        # HomeAssistantConnectionError or any other error → metadata-only
         # (no full-body legacy fetch exists; the base metadata is already served).
         logger.warning(
             "ha_mcp_tools/blueprint_get connection error; served metadata-only: %r",

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/component_config_reads.py RENAMED Viewed

@@ -27,11 +27,11 @@ returns its payload (an entity_lookup with an EMPTY ``matches`` list is
 authoritative — "no registry entry with that unique_id" — kept distinct from the
 ``None`` miss).
-Both helpers apply the uniform transport-fallback taxonomy: a
-``HomeAssistantConnectionError`` off ``send_command`` — and the plain
-``Exception`` ``get_websocket_client()`` raises when ``WebSocketManager`` cannot
-(re)build the pooled socket — are caught and mapped to ``None`` so the legacy
-path runs, NEVER propagated out of the read. Neither consumer's legacy path dies
+Both helpers apply the uniform transport-fallback taxonomy: a transport failure
+— ``HomeAssistantConnectionError`` off ``send_command`` or from a failed (re)build
+of the pooled socket in ``get_websocket_client()``, or ``HomeAssistantAuthError``
+when HA rejects the token — is caught and mapped to ``None`` so the legacy path
+runs, NEVER propagated out of the read. Neither consumer's legacy path dies
 identically on a pooled-WS drop, so propagating would abort work the legacy path
 still completes:
@@ -120,8 +120,8 @@ async def fetch_entity_lookup_via_component(
             logger.warning("%s failed; fell back to legacy: %r", WS_ENTITY_LOOKUP, exc)
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError: a pooled-WS drop or a failed
-        # (re)connect.
+        # HomeAssistantConnectionError (a pooled-WS drop or a failed
+        # (re)connect) or any other error.
         # The resolvers' legacy paths do NOT die identically (see module docstring),
         # so route to legacy rather than escape.
         logger.warning(

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/component_devices.py RENAMED Viewed

@@ -193,7 +193,7 @@ async def fetch_device_list_via_component(client: Any) -> dict[str, Any] | None:
             logger.warning("%s failed; fell back to legacy: %r", WS_DEVICE_LIST, exc)
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → legacy (the
+        # HomeAssistantConnectionError or any other error → legacy (the
         # legacy device list rides the send_websocket_message bridge).
         logger.warning(
             "%s connection error; falling back to legacy: %r", WS_DEVICE_LIST, exc

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/component_registry_lookup.py RENAMED Viewed

@@ -104,7 +104,7 @@ async def fetch_entities_for_config_entry_via_component(
             )
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → legacy (the
+        # HomeAssistantConnectionError or any other error → legacy (the
         # legacy entity_registry/list dump rides the bridge; see module
         # docstring). Never propagate a transport failure out of the read.
         logger.warning(
@@ -159,7 +159,7 @@ async def resolve_entities_via_component(
             )
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → legacy. The
+        # HomeAssistantConnectionError or any other error → legacy. The
         # simple-delete consumer's legacy per-id retry loop only runs when this
         # returns None, so an escaping transport failure would skip it entirely.
         logger.warning(

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/log_sources_logbook.py RENAMED Viewed

@@ -602,12 +602,9 @@ class LogbookLogSourceMixin:
                     order,
                 )
-            wrapped = await add_timezone_metadata(self._client, logbook_data)
             if transport_warnings:
-                # Top-level, alongside the other tool warnings: nesting these
-                # under ``data`` would hide them from the warning merger.
-                wrapped["warnings"] = transport_warnings + wrapped.get("warnings", [])
-            return wrapped
+                logbook_data["warnings"] = transport_warnings
+            return await add_timezone_metadata(self._client, logbook_data)
         except ToolError:
             raise

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/response_helpers.py RENAMED Viewed

@@ -416,10 +416,27 @@ async def add_timezone_metadata(
     - Naive strings (no offset) are assumed to be UTC before conversion.
     - ``ZoneInfoNotFoundError`` (tzdata not installed) falls back to UTC.
     - Any config-fetch failure also falls back to UTC without conversion.
+    A top-level ``warnings`` list in *data* is returned beside ``data`` instead
+    of inside it, ahead of any timezone warning the wrapper adds, and omitted
+    when empty; *data* itself is left unchanged.
     """
     if not include_metadata:
         return data
+    result = await _wrap_with_timezone(client, data, convert_timestamps)
+    inner = result["data"]
+    if isinstance(inner, dict) and isinstance(inner.get("warnings"), list):
+        result["data"] = {k: v for k, v in inner.items() if k != "warnings"}
+        if warnings := inner["warnings"] + result.get("warnings", []):
+            result["warnings"] = warnings
+    return result
+async def _wrap_with_timezone(
+    client: Any, data: dict[str, Any], convert_timestamps: bool
+) -> dict[str, Any]:
+    """Fetch the timezone, convert *data* and wrap it; may add top-level ``warnings``."""
     ha_timezone, fetch_failed = await fetch_ha_timezone(client)
     if not convert_timestamps:

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/component.py RENAMED Viewed

@@ -767,7 +767,9 @@ class ComponentSearchMixin(LegacySearchMixin):
           ``send_websocket_message`` bridge, so a component-side fault degrades
           to partial results rather than escaping. The bridge shares this
           pooled connection, so a dead transport raises there too (#1947) and
-          the registry-unavailable warning names what was skipped.
+          the registry-unavailable warning names what was skipped. When no
+          legacy surface answers either, the legacy search raises its
+          structured error instead.
         """
         if isinstance(exc, (HomeAssistantCommandError, HomeAssistantCommandTimeout)):
             if is_unknown_command(exc):

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/legacy.py RENAMED Viewed

@@ -135,6 +135,14 @@ class LegacySearchMixin(EntityModesMixin):
                 continue
             _apply_search_outcome(response, label, outcome)
+        if outcomes and len(errors) == len(outcomes):
+            # No surface answered, so empty buckets would read as "nothing
+            # matched": report the first surface's error instead.
+            first = cast(Exception, outcomes[0])
+            if isinstance(first, ToolError):
+                raise first
+            exception_to_structured_error(first)
         # ``count`` mirrors the previous ha_search_entities semantics: items
         # returned in this response (post-pagination), not total matches across
         # the corpus. Total matches live in entity_total_matches +
@@ -347,17 +355,9 @@ class LegacySearchMixin(EntityModesMixin):
                 # carry area_result's warnings; forward them here in one place so a
                 # visibility/registry degradation on the area path is not silently
                 # dropped (mirrors the non-area path's merge_visibility_warnings).
-                # The builders now return the search dict directly (no
-                # add_timezone_metadata wrapper), so warnings merge into that dict;
-                # the ``["data"]`` unwrap is a defensive holdover for a hypothetical
-                # future wrapped payload.
-                warn_target = (
-                    area_search["data"]
-                    if isinstance(area_search, dict) and "data" in area_search
-                    else area_search
+                return merge_visibility_warnings(
+                    area_search, area_result.get("warnings", [])
                 )
-                merge_visibility_warnings(warn_target, area_result.get("warnings", []))
-                return area_search
             if domain_filter and (not query or not query.strip()):
                 return await self._search_domain_only(

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/modes.py RENAMED Viewed

@@ -167,8 +167,7 @@ class EntityModesMixin(EntityEnrichmentMixin):
         merge_visibility_warnings(search_data, enrich_warnings)
         # No add_timezone_metadata: entity records carry no timestamp fields, so
-        # the enrichment converted nothing and its /api/config fetch was pure
-        # waste (the orchestrator discards its metadata wrapper anyway).
+        # the enrichment converted nothing and its /api/config fetch was pure waste.
         return search_data
     async def _search_area_only_populated(

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/overview.py RENAMED Viewed

@@ -468,13 +468,14 @@ class OverviewMixin(SearchToolsBase):
           non-empty ``slice_errors`` — ``_build_overview_slices`` returns
           ``None``): treated like the command-error branch (legacy + warning +
           log), so a partial snapshot never serves a silently-degraded overview.
-        - ``HomeAssistantConnectionError`` (pooled-WS drop) or the plain
-          ``Exception`` ``get_websocket_client()`` raises on a failed (re)connect:
-          served the same way — the legacy overview reads ``/api/states`` +
-          ``/api/services`` over REST and the registries through the swallowing
-          ``send_websocket_message`` bridge, so it degrades to a partial overview
-          rather than dying identically on a pooled-WS drop; a transport failure
-          must not escape.
+        - ``HomeAssistantConnectionError`` (pooled-WS drop or a failed (re)connect
+          in ``get_websocket_client()``): served the same way — the legacy
+          overview reads ``/api/states`` + ``/api/services`` over REST and the
+          registries through the ``send_websocket_message`` bridge, so it
+          degrades to a partial overview rather than dying identically on a
+          pooled-WS drop; a transport failure must not escape. A token HA
+          rejects (``HomeAssistantAuthError``) takes this branch too, but the
+          legacy reads use the same token and fail with it.
         """
         try:
             raw = await self._send_component_overview(inputs)

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/response.py RENAMED Viewed

@@ -189,6 +189,17 @@ def _mirror_partial_to_warnings(response: dict[str, Any]) -> None:
         warnings.append(warning_text)
+def _omit_empty_warnings(response: dict[str, Any]) -> dict[str, Any]:
+    """Drop an empty ``warnings`` list: the response contract omits it.
+    The builders seed ``warnings`` as ``[]`` so they can extend it; this runs
+    once on the finished response of every ``ha_search`` path.
+    """
+    if response.get("warnings") == []:
+        del response["warnings"]
+    return response
 def _project_response_fields(
     response: dict[str, Any], parsed_fields: list[str] | None
 ) -> dict[str, Any]:
@@ -500,20 +511,9 @@ def _build_hidden_ids(registry_result: Any) -> set[str]:
 def _apply_search_outcome(
     response: dict[str, Any],
     label: str,
-    outcome: dict[str, Any],
+    payload: dict[str, Any],
 ) -> None:
-    """Apply one gather outcome (entities or configs) to the response dict in-place.
-    Both ``_ha_search_entities`` and ``_ha_deep_search`` return their search dict
-    directly. The entity builders no longer wrap it via ``add_timezone_metadata``:
-    entity-search records carry none of the timestamp fields that enrichment
-    converts, so it was a discarded ``/api/config`` fetch. The ``{"data": ...}``
-    unwrap is kept as a defensive no-op so a future wrapped payload still reads
-    correctly.
-    """
-    payload = (
-        outcome["data"] if isinstance(outcome, dict) and "data" in outcome else outcome
-    )
+    """Apply one gather outcome (entities or configs) to the response dict in-place."""
     if label == "entities":
         response["entities"] = payload.get("results", [])
         response["entity_total_matches"] = payload.get("total_matches", 0)

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/search/state.py RENAMED Viewed

@@ -13,7 +13,6 @@ from ...client.rest_client import (
     HomeAssistantAPIError,
     HomeAssistantCommandError,
     HomeAssistantCommandTimeout,
-    HomeAssistantConnectionError,
 )
 from ...client.websocket_client import get_websocket_client
 from ...errors import create_validation_error
@@ -297,11 +296,11 @@ class StateMixin(SearchToolsBase):
         Returns the component's ``{states, missing}`` payload (found ids mapped to
         their ``State.as_dict()`` body) or ``None`` when the component lacks the
         ``states`` capability, was downgraded (``unknown_command`` → invalidate the
-        cached caps), or errored (logged). Falls back **silently** — unlike
-        ``ha_search`` / ``ha_get_zone`` which append a ``warnings[]`` entry —
-        because ``ha_get_state``'s single- and bulk-mode responses do not share one
-        warnings channel; the ``log.warning`` preserves operator visibility and the
-        legacy REST path returns the byte-identical correct data either way.
+        cached caps), errored, or returned a malformed payload (both logged).
+        Falls back **silently** — unlike ``ha_search`` / ``ha_get_zone``, which
+        append a ``warnings[]`` entry — because the legacy REST path returns the
+        byte-identical correct data either way, so the caller has nothing to act
+        on; the ``log.warning`` preserves operator visibility.
         ``ha_get_state``'s legacy path is a REST ``get_entity_state`` read on a
         SEPARATE transport, so a WS transport/connect failure
         (``HomeAssistantConnectionError``, covering both a pooled-WS drop and a
@@ -316,11 +315,7 @@ class StateMixin(SearchToolsBase):
             return None
         try:
             raw = await self._send_component_states(entity_ids)
-        except (
-            HomeAssistantCommandError,
-            HomeAssistantCommandTimeout,
-            HomeAssistantConnectionError,
-        ) as exc:
+        except (HomeAssistantCommandError, HomeAssistantCommandTimeout) as exc:
             if is_unknown_command(exc):
                 invalidate_caps(self._client)
             else:
@@ -329,14 +324,19 @@ class StateMixin(SearchToolsBase):
                 )
             return None
         except Exception as exc:  # noqa: BLE001
-            # Anything the tuple above doesn't cover → legacy REST, so an
-            # install whose REST API still works keeps answering.
+            # Mostly HomeAssistantConnectionError (a pooled-WS drop or a failed
+            # (re)connect); a WS auth failure or a raw socket error lands here
+            # too. Legacy REST rides a separate transport, so an install whose
+            # REST API still works keeps answering.
             logger.warning(
                 "ha_mcp_tools/states connection error; fell back to legacy: %r", exc
             )
             return None
-        result = raw.get("result") or {}
-        if not isinstance(result.get("states"), dict):
+        result = raw.get("result")
+        if not isinstance(result, dict) or not isinstance(result.get("states"), dict):
+            logger.warning(
+                "ha_mcp_tools/states returned a malformed payload; fell back to legacy"
+            )
             return None
         return result

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/tools_config_helpers.py RENAMED Viewed

@@ -212,25 +212,27 @@ class HelperConfigTools:
         # silent empty). Storage/collection types keep the legacy fallback.
         is_flow = helper_type not in SIMPLE_HELPER_TYPES
-        # Prefer the custom component's in-process listing when it advertises
-        # the capability: one WS round-trip that joins the entity registry, so
-        # each record carries the current entity_id + display name (the #1794
-        # stale-id fix, shipped additively) instead of only the storage id.
-        # Fall back cleanly for storage types when the component is absent,
-        # downlevel, or errors — the taxonomy lives in
-        # ``_list_helpers_via_component``. The legacy body below is untouched.
-        caps = await get_component_caps(self._client)
-        if component_supports(caps, "helpers_list"):
-            component_response = await self._list_helpers_via_component(
-                helper_type, is_flow=is_flow
-            )
-            if component_response is not None:
-                return _paginate_helpers_response(component_response, offset, limit)
-        if is_flow:
-            # No usable component path and the legacy body cannot serve flow
-            # helpers: hard error rather than an empty or misleading list.
-            _raise_flow_requires_component(helper_type)
         try:
+            # Prefer the custom component's in-process listing when it advertises
+            # the capability: one WS round-trip that joins the entity registry, so
+            # each record carries the current entity_id + display name (the #1794
+            # stale-id fix, shipped additively) instead of only the storage id.
+            # Fall back cleanly for storage types when the component is absent,
+            # downlevel, or errors — the taxonomy lives in
+            # ``_list_helpers_via_component``.
+            # Inside the ``try`` so an error the fallback re-raises reaches the
+            # structured-error handler below.
+            caps = await get_component_caps(self._client)
+            if component_supports(caps, "helpers_list"):
+                component_response = await self._list_helpers_via_component(
+                    helper_type, is_flow=is_flow
+                )
+                if component_response is not None:
+                    return _paginate_helpers_response(component_response, offset, limit)
+            if is_flow:
+                # No usable component path and the legacy body cannot serve flow
+                # helpers: hard error rather than an empty or misleading list.
+                _raise_flow_requires_component(helper_type)
             result = await self._client.send_websocket_message(
                 {"type": f"{helper_type}/list"}
             )
@@ -297,8 +299,8 @@ class HelperConfigTools:
           for a storage type, serve the correct result from the legacy WS list,
           append a ``warnings[]`` entry, and ``log.warning``. For a flow type,
           raise the component-required error — no legacy fallback exists.
-        - ``HomeAssistantConnectionError`` (pooled-WS drop) or the plain
-          ``Exception`` ``get_websocket_client()`` raises on a failed (re)connect:
+        - ``HomeAssistantConnectionError`` (pooled-WS drop or a failed (re)connect
+          in ``get_websocket_client()``) or ``HomeAssistantAuthError`` (token rejected):
           for a storage type, the legacy ``{helper_type}/list`` body is attempted,
           with a ``warnings[]`` entry + ``log.warning``. It rides the
           ``send_websocket_message`` bridge over the SAME pooled connection
@@ -339,8 +341,9 @@ class HelperConfigTools:
             return legacy
         except Exception as exc:
             # Transport/establishment failure — a pooled-WS drop or a failed
-            # (re)connect, both HomeAssistantConnectionError. A storage type
-            # still attempts the legacy
+            # (re)connect (HomeAssistantConnectionError), a rejected token
+            # (HomeAssistantAuthError) or any other error. A storage type still
+            # attempts the legacy
             # `{helper_type}/list` body: it rides the same pooled connection, so it
             # recovers a component-side fault but not a dead socket, where the
             # bridge raises in turn (#1947). A flow type has NO legacy body, so its

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/tools_dev.py RENAMED Viewed

@@ -318,7 +318,7 @@ async def _fetch_server_entry_via_component(client: Any) -> dict[str, Any] | Non
             logger.warning("%s failed; fell back to legacy: %r", WS_SERVER_ENTRY, exc)
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → legacy probe
+        # HomeAssistantConnectionError or any other error → legacy probe
         # (which rides the send_websocket_message bridge).
         logger.warning(
             "%s connection error; falling back to legacy: %r", WS_SERVER_ENTRY, exc

{ha_mcp_dev-9.1.0.dev3274 → ha_mcp_dev-9.1.0.dev3279}/src/ha_mcp/tools/tools_entities.py RENAMED Viewed

@@ -174,7 +174,7 @@ async def fetch_entity_enrichment_via_component(
             logger.warning("%s failed; skipped enrichment: %r", WS_ENTITY_ENRICH, exc)
         return None
     except Exception as exc:  # noqa: BLE001
-        # HomeAssistantConnectionError / plain establish Exception → skip
+        # HomeAssistantConnectionError or any other error → skip
         # enrichment (strictly additive; no legacy fetch dies here).
         logger.warning(
             "%s connection error; skipped enrichment: %r", WS_ENTITY_ENRICH, exc

ha-mcp-dev 9.1.0.dev3274__tar.gz → 9.1.0.dev3279__tar.gz

ha-mcp-dev 9.1.0.dev3274tar.gz → 9.1.0.dev3279tar.gz