ha-mcp-dev 7.6.0.dev657__tar.gz → 7.6.0.dev659__tar.gz

{ha_mcp_dev-7.6.0.dev657/src/ha_mcp_dev.egg-info → ha_mcp_dev-7.6.0.dev659}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.6.0.dev657
+Version: 7.6.0.dev659
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT
@@ -245,6 +245,26 @@ Spend less time configuring, more time enjoying your smart home.
 
 ---
 
+## 🆚 ha-mcp vs. Home Assistant's built-in MCP Server
+
+Home Assistant ships its own [MCP Server integration](https://www.home-assistant.io/integrations/mcp_server/). It is built on the **Assist** pipeline, so a connected MCP client can read and control the entities you have exposed to Assist and run the intents Assist understands — handy for voice-style control of already-exposed devices.
+
+ha-mcp is a standalone server built for **configuring, building, and debugging** your smart home, not just controlling it. On top of device control, it adds capabilities the built-in integration does not have:
+
+| Capability | Built-in MCP Server | ha-mcp |
+|------------|:-------------------:|:------:|
+| Control exposed devices, query states | Yes | Yes |
+| Entity scope | Only entities exposed to Assist | Everything in Home Assistant |
+| Create / edit automations, scripts, scenes | No | Yes |
+| Build & edit dashboards | No | Yes |
+| Debug automations from traces, read history & logs | No | Yes |
+| Manage helpers, areas, zones, labels, groups | No | Yes |
+| Backups, add-ons, HACS, device & entity registry | No | Yes |
+
+**Rule of thumb:** Use the built-in integration for voice-style control of devices you have already exposed; use ha-mcp when you want an AI assistant that can also build and maintain your Home Assistant setup.
+
+---
+
 ## 🔌 Custom Component (ha_mcp_tools) *(beta)*
 
 Some tools require a companion custom component installed in Home Assistant. Standard HA APIs do not expose file system access or YAML config editing. This component provides both.

{ha_mcp_dev-7.6.0.dev657 → ha_mcp_dev-7.6.0.dev659}/README.md

@@ -215,6 +215,26 @@ Spend less time configuring, more time enjoying your smart home.
 
 ---
 
+## 🆚 ha-mcp vs. Home Assistant's built-in MCP Server
+
+Home Assistant ships its own [MCP Server integration](https://www.home-assistant.io/integrations/mcp_server/). It is built on the **Assist** pipeline, so a connected MCP client can read and control the entities you have exposed to Assist and run the intents Assist understands — handy for voice-style control of already-exposed devices.
+
+ha-mcp is a standalone server built for **configuring, building, and debugging** your smart home, not just controlling it. On top of device control, it adds capabilities the built-in integration does not have:
+
+| Capability | Built-in MCP Server | ha-mcp |
+|------------|:-------------------:|:------:|
+| Control exposed devices, query states | Yes | Yes |
+| Entity scope | Only entities exposed to Assist | Everything in Home Assistant |
+| Create / edit automations, scripts, scenes | No | Yes |
+| Build & edit dashboards | No | Yes |
+| Debug automations from traces, read history & logs | No | Yes |
+| Manage helpers, areas, zones, labels, groups | No | Yes |
+| Backups, add-ons, HACS, device & entity registry | No | Yes |
+
+**Rule of thumb:** Use the built-in integration for voice-style control of devices you have already exposed; use ha-mcp when you want an AI assistant that can also build and maintain your Home Assistant setup.
+
+---
+
 ## 🔌 Custom Component (ha_mcp_tools) *(beta)*
 
 Some tools require a companion custom component installed in Home Assistant. Standard HA APIs do not expose file system access or YAML config editing. This component provides both.

{ha_mcp_dev-7.6.0.dev657 → ha_mcp_dev-7.6.0.dev659}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "7.6.0.dev657"
+version = "7.6.0.dev659"
 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.dev657 → ha_mcp_dev-7.6.0.dev659}/src/ha_mcp/server.py

@@ -1212,7 +1212,11 @@ class HomeAssistantSmartMCPServer(EnhancedToolsMixin):
         self.mcp.tool(
             name=SKILL_TOOL_NAME,
             description=tool_description,
-            annotations={"readOnlyHint": True, "idempotentHint": True},
+            annotations={
+                "readOnlyHint": True,
+                "idempotentHint": True,
+                "title": "Get Home Assistant Best Practices Skill Guide",
+            },
             tags={"System"},
         )(ha_get_skill_guide)
         logger.info(

{ha_mcp_dev-7.6.0.dev657 → ha_mcp_dev-7.6.0.dev659}/src/ha_mcp/tools/tools_config_automations.py

@@ -566,7 +566,7 @@ class AutomationConfigTools:
             "alias": "Morning Lights",
             "description": "Turn on bedroom lights at 7 AM to help wake up",
             "trigger": [{"platform": "time", "at": "07:00:00"}],
-            "action": [{"service": "light.turn_on", "target": {"area_id": "bedroom"}}]
+            "action": [{"action": "light.turn_on", "target": {"area_id": "bedroom"}}]
         })
 
         Motion-activated lighting — `for:` on the off-transition replaces action-delay:
@@ -583,9 +583,9 @@ class AutomationConfigTools:
                         {"condition": "trigger", "id": "motion_on"},
                         {"condition": "sun", "after": "sunset"}
                     ],
-                     "sequence": [{"service": "light.turn_on", "target": {"entity_id": "light.hallway"}}]},
+                     "sequence": [{"action": "light.turn_on", "target": {"entity_id": "light.hallway"}}]},
                     {"conditions": [{"condition": "trigger", "id": "motion_off"}],
-                     "sequence": [{"service": "light.turn_off", "target": {"entity_id": "light.hallway"}}]}
+                     "sequence": [{"action": "light.turn_off", "target": {"entity_id": "light.hallway"}}]}
                 ]}
             ]
         })
@@ -597,8 +597,8 @@ class AutomationConfigTools:
                 "alias": "Updated Morning Routine",
                 "trigger": [{"platform": "time", "at": "06:30:00"}],
                 "action": [
-                    {"service": "light.turn_on", "target": {"area_id": "bedroom"}},
-                    {"service": "climate.set_temperature", "target": {"entity_id": "climate.bedroom"}, "data": {"temperature": 22}}
+                    {"action": "light.turn_on", "target": {"area_id": "bedroom"}},
+                    {"action": "climate.set_temperature", "target": {"entity_id": "climate.bedroom"}, "data": {"temperature": 22}}
                 ]
             }
         )
@@ -636,7 +636,7 @@ class AutomationConfigTools:
 
         TRIGGER TYPES: time, time_pattern, sun, state, numeric_state, event, device, zone, template, and more
         CONDITION TYPES: state, numeric_state, time, sun, template, device, zone, and more
-        ACTION TYPES: service calls, delays, wait_for_trigger, wait_template, if/then/else, choose, repeat, parallel
+        ACTION TYPES: action calls, delays, wait_for_trigger, wait_template, if/then/else, choose, repeat, parallel
 
         For comprehensive automation documentation with all trigger/condition/action types and advanced examples:
         - Use: ha_get_skill_guide
@@ -747,13 +747,34 @@ class AutomationConfigTools:
                 and e.status_code == 404
             ):
                 await self._raise_automation_not_found(identifier)
+            error_text = str(e)
             suggestions = [
                 "Check automation configuration format",
                 "Ensure required fields: alias, trigger, action",
                 "Use entity_id format: automation.morning_routine or unique_id",
                 "Use ha_search_entities(domain_filter='automation') to find automations",
-                "Use ha_get_skill_guide for help",
+                "Use ha_get_skill_guide for automation examples",
             ]
+            if isinstance(e, HomeAssistantAPIError):
+                if "'service'" in error_text and "not allowed" in error_text:
+                    suggestions.insert(
+                        0,
+                        "Use 'action:' not 'service:' for service calls in action steps "
+                        "(renamed in HA 2024.8).",
+                    )
+                elif "unexpected keyword argument" in error_text.lower():
+                    suggestions.insert(
+                        0,
+                        "An action step contains a field that belongs at the automation root "
+                        "(e.g. alias, trigger, condition). Each action step should only contain "
+                        "action/target/data/delay/choose/if/repeat/parallel keys.",
+                    )
+                elif "'variables'" in error_text and "dictionary" in error_text:
+                    suggestions.insert(
+                        0,
+                        "variables must be a dict mapping names to values, "
+                        'e.g. {"variables": {"my_var": 42}}',
+                    )
             if bp_warnings:
                 suggestions.append(
                     "Config had best-practice issues that may be related: "

{ha_mcp_dev-7.6.0.dev657 → ha_mcp_dev-7.6.0.dev659}/src/ha_mcp/tools/tools_config_scripts.py

@@ -512,9 +512,9 @@ class ConfigScriptTools:
         Create service call script:
         ha_config_set_script(script_id="blink_light", config={
             "sequence": [
-                {"service": "light.turn_on", "target": {"entity_id": "light.living_room"}},
+                {"action": "light.turn_on", "target": {"entity_id": "light.living_room"}},
                 {"delay": {"seconds": 2}},
-                {"service": "light.turn_off", "target": {"entity_id": "light.living_room"}}
+                {"action": "light.turn_off", "target": {"entity_id": "light.living_room"}}
             ],
             "alias": "Light Blink",
             "mode": "single"
@@ -547,8 +547,8 @@ class ConfigScriptTools:
         Update script:
         ha_config_set_script(script_id="morning_routine", config={
             "sequence": [
-                {"service": "light.turn_on", "target": {"area_id": "bedroom"}},
-                {"service": "climate.set_temperature", "target": {"entity_id": "climate.bedroom"}, "data": {"temperature": 22}}
+                {"action": "light.turn_on", "target": {"area_id": "bedroom"}},
+                {"action": "climate.set_temperature", "target": {"entity_id": "climate.bedroom"}, "data": {"temperature": 22}}
             ],
             "alias": "Updated Morning Routine"
         })

{ha_mcp_dev-7.6.0.dev657 → ha_mcp_dev-7.6.0.dev659/src/ha_mcp_dev.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.6.0.dev657
+Version: 7.6.0.dev659
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT
@@ -245,6 +245,26 @@ Spend less time configuring, more time enjoying your smart home.
 
 ---
 
+## 🆚 ha-mcp vs. Home Assistant's built-in MCP Server
+
+Home Assistant ships its own [MCP Server integration](https://www.home-assistant.io/integrations/mcp_server/). It is built on the **Assist** pipeline, so a connected MCP client can read and control the entities you have exposed to Assist and run the intents Assist understands — handy for voice-style control of already-exposed devices.
+
+ha-mcp is a standalone server built for **configuring, building, and debugging** your smart home, not just controlling it. On top of device control, it adds capabilities the built-in integration does not have:
+
+| Capability | Built-in MCP Server | ha-mcp |
+|------------|:-------------------:|:------:|
+| Control exposed devices, query states | Yes | Yes |
+| Entity scope | Only entities exposed to Assist | Everything in Home Assistant |
+| Create / edit automations, scripts, scenes | No | Yes |
+| Build & edit dashboards | No | Yes |
+| Debug automations from traces, read history & logs | No | Yes |
+| Manage helpers, areas, zones, labels, groups | No | Yes |
+| Backups, add-ons, HACS, device & entity registry | No | Yes |
+
+**Rule of thumb:** Use the built-in integration for voice-style control of devices you have already exposed; use ha-mcp when you want an AI assistant that can also build and maintain your Home Assistant setup.
+
+---
+
 ## 🔌 Custom Component (ha_mcp_tools) *(beta)*
 
 Some tools require a companion custom component installed in Home Assistant. Standard HA APIs do not expose file system access or YAML config editing. This component provides both.