ha-mcp-dev 8.5.0.dev2750__tar.gz → 8.5.0.dev2754__tar.gz

{ha_mcp_dev-8.5.0.dev2750/src/ha_mcp_dev.egg-info → ha_mcp_dev-8.5.0.dev2754}/PKG-INFO

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

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "8.5.0.dev2750"
+version = "8.5.0.dev2754"
 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-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Agent skills for Home Assistant: best practices for automations, helpers, templates, scenes, blueprints, device control, dashboards, AppDaemon, and backups",
-    "version": "0.34.0"
+    "version": "0.36.0"
   },
   "plugins": [
     {

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "home-assistant-skills",
   "description": "Agent skills for Home Assistant: best practices for automations, helpers, templates, scenes, blueprints, device control, dashboards, AppDaemon, and backups.",
-  "version": "0.34.0",
+  "version": "0.36.0",
   "repository": "https://github.com/homeassistant-ai/skills",
   "license": "MIT"
 }

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/README.md

@@ -92,7 +92,7 @@ The `home-assistant-best-practices` skill includes:
 |------|---------|
 | [`SKILL.md`](skills/home-assistant-best-practices/SKILL.md) | Decision workflow, anti-pattern table, and pointers to the reference files below |
 | [`references/safe-refactoring.md`](skills/home-assistant-best-practices/references/safe-refactoring.md) | Safe workflow for renaming entities and their display names, replacing helpers, restructuring automations; display-name override, config-entry, and storage-dashboard blind spots |
-| [`references/automation-patterns.md`](skills/home-assistant-best-practices/references/automation-patterns.md) | Purpose-specific and native triggers/conditions, waits, variables, automation modes, control flow (choose, repeat, parallel), disabling automations |
+| [`references/automation-patterns.md`](skills/home-assistant-best-practices/references/automation-patterns.md) | Purpose-specific and native triggers/conditions, waits, variables, automation modes, control flow (choose, repeat, parallel), error handling (`continue_on_error`, admin-only actions), disabling automations |
 | [`references/helper-selection.md`](skills/home-assistant-best-practices/references/helper-selection.md) | Built-in helpers vs template sensors (with decision matrix) |
 | [`references/template-guidelines.md`](skills/home-assistant-best-practices/references/template-guidelines.md) | When to use templates, when to avoid them, template sensor best practices, reusable `custom_templates` macros |
 | [`references/yaml-only-integrations.md`](skills/home-assistant-best-practices/references/yaml-only-integrations.md) | YAML-only integration types, post-edit actions (reload vs restart) |

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/skills/home-assistant-best-practices/SKILL.md

@@ -23,7 +23,7 @@ description: >
   - Existing state changed with no recovery path
   - Jinja copy-pasted between templates
 metadata:
-  version: "34"
+  version: "36"
 ---
 
 # Home Assistant Best Practices
@@ -135,7 +135,7 @@ Read these when you need detailed information:
 | File | When to read |
 |------|--------------|
 | [safe-refactoring](references/safe-refactoring.md) | Renaming entities or their display names, replacing helpers, restructuring automations, or any modification to existing config |
-| [automation-patterns](references/automation-patterns.md) | Writing triggers, conditions, waits, variables, or choosing automation modes; capturing action responses; documenting/annotating steps; disabling automations; `continue_on_error`, stopping a sequence, repeat, if/then vs choose, parallel, trigger IDs |
+| [automation-patterns](references/automation-patterns.md) | Writing triggers, conditions, waits, variables, or choosing automation modes; capturing action responses; documenting/annotating steps; disabling automations; `continue_on_error`, admin-only actions (`Unauthorized`) in scripts, stopping a sequence, repeat, if/then vs choose, parallel, trigger IDs |
 | [helper-selection](references/helper-selection.md) | Deciding whether to use a built-in helper vs template sensor — aggregation, rate of change, thresholds, time-in-state, counting/timing, scheduling, grouping, probabilistic inference, smoothing, climate, domain conversion, decision matrix |
 | [template-guidelines](references/template-guidelines.md) | Confirming templates ARE appropriate for a use case; sharing Jinja logic between templates with `custom_templates` macros |
 | [yaml-only-integrations](references/yaml-only-integrations.md) | Creating or editing YAML-only integrations that have no config flow (e.g. `command_line`, platform-based `mqtt`, `rest`) |

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/skills/home-assistant-best-practices/references/automation-patterns.md

@@ -679,10 +679,12 @@ Fires on persistent-notification lifecycle changes (e.g. react to an integration
 ```yaml
 triggers:
   - trigger: persistent_notification
-    update_type: [added, removed]     # any of: added, removed, updated, current; omit for all
+    update_type: [added, updated]     # any of: added, removed, updated (current never reaches triggers); omit for all
     notification_id: invalid_config   # optional: filter to one notification
 ```
 
+**Since 2026.9, re-posting an existing `notification_id` fires `updated`, not `added`.** Integrations re-post their notices under a fixed ID, so a trigger on `added` alone catches only the first post while that notice is still showing — list `updated` alongside it. Before 2026.9 every create fired `added` and `updated` never fired.
+
 ### Presence and Person Triggers and Conditions (Removed in 2026.5)
 
 The `entered_home`/`left_home` device trigger types and `is_home`/`is_not_home` device condition types for `person` and `device_tracker` domains were **removed in 2026.5**. Use state triggers and conditions instead.
@@ -936,6 +938,18 @@ actions:
 
 **Use sparingly** — silently swallowing errors makes debugging harder. Best for non-critical actions (e.g., logging, optional notifications) where a failure shouldn't block the rest of the automation.
 
+### Admin-only actions in user-started scripts
+
+Some actions refuse a non-admin caller — since 2026.9 these include `update.install`, `update.skip` and `update.clear_skipped`. The check reads the user on the run's context:
+
+| Started by | Admin-only action |
+|---|---|
+| An automation, however triggered (a manual run too), or a script it calls | Runs — every automation run gets a fresh context with no user |
+| An admin (UI, dashboard button, their long-lived token) | Runs |
+| A non-admin user (dashboard button, their long-lived token) | Fails with `Unauthorized` |
+
+`continue_on_error: true` does not fix the non-admin row: it swallows `Unauthorized` like any other runtime error, so the script carries on without the update installed. To let non-admins start it on purpose, have the button call `automation.trigger` on an automation that runs the action (a helper change that triggers the automation also works) — this deliberately grants every user who can press the button that admin-only action.
+
 ---
 
 ## Stopping a Sequence

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754}/src/ha_mcp/resources/skills-vendor/skills/home-assistant-best-practices/references/device-control.md

@@ -509,7 +509,13 @@ Read left to right and stop at the first column that applies.
 | Door/Window | `door.opened` / `door.closed`, `window.opened` / `window.closed` | `state` | — |
 | Temperature | `temperature.crossed_threshold` / `temperature.changed` | `numeric_state` or `state` | — |
 | Switch | `switch.turned_on` / `switch.turned_off` | `state` | — |
-| Battery | `battery.became_low` / `battery.no_longer_low` | `numeric_state` | — |
+| Battery (low flag, `binary_sensor`) | `battery.became_low` / `battery.no_longer_low` | `state` | — |
+| Battery (percentage, `sensor`) | `battery.level_crossed_threshold` / `battery.level_changed` | `numeric_state` | — |
+
+`battery.level_changed` fires on every level change while the reading is inside its
+threshold. For a one-time "dropped below N%" alert use `battery.level_crossed_threshold`: it
+fires only on the crossing, and ignores changes coming from `unavailable`/`unknown`, so a
+restart does not fire it again.
 
 Two rules survive whichever column you land in: **don't key a trigger off a `device_id`**
 outside the cases in [When Device ID is Acceptable](#when-device-id-is-acceptable), and

{ha_mcp_dev-8.5.0.dev2750 → ha_mcp_dev-8.5.0.dev2754/src/ha_mcp_dev.egg-info}/PKG-INFO

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