ha-mcp-dev 8.3.0.dev2472__tar.gz → 8.3.0.dev2473__tar.gz

{ha_mcp_dev-8.3.0.dev2472/src/ha_mcp_dev.egg-info → ha_mcp_dev-8.3.0.dev2473}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 8.3.0.dev2472
+Version: 8.3.0.dev2473
 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.3.0.dev2472 → ha_mcp_dev-8.3.0.dev2473}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "8.3.0.dev2472"
+version = "8.3.0.dev2473"
 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.3.0.dev2472 → ha_mcp_dev-8.3.0.dev2473}/src/ha_mcp/settings_ui/locales/en.json

@@ -287,12 +287,12 @@
     "backup.bulk.filter_required": "Set at least one filter (Domain, Entity, or age in days).",
     "backup.bulk.confirm": "Delete all backups matching: {filters}?",
     "backup.bulk.deleted": "Deleted {count} backup(s)",
-    "filesystem.custom.title": "Custom filesystem directories (advanced)",
-    "filesystem.custom.help": "Extra paths (one per line) that file tools may <strong>read and write</strong>. Relative config paths and allowed HAOS sibling volumes are supported. Each entry allows that path and anything below it; config-relative filenames, such as <code>sensor.yaml</code>, can be entered directly. Applies immediately.",
+    "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>, <code>/ssl</code>, and <code>/backup</code> are supported. Each entry allows that path and anything below it. 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.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 directories are currently unavailable.",
-    "filesystem.custom.save": "Save directories",
+    "filesystem.custom.unavailable": "Custom paths are currently unavailable.",
+    "filesystem.custom.save": "Save paths",
     "filesystem.custom.saved_rejected": "Saved. Rejected (blocked or invalid): {paths}",
     "origins.env_locked": "Set via environment variable; unset it to edit here.",
     "origins.addon_synced": "Synced to the app (add-on) Configuration tab. Restart required after save.",

{ha_mcp_dev-8.3.0.dev2472 → ha_mcp_dev-8.3.0.dev2473}/src/ha_mcp/settings_ui/settings.js

@@ -1653,8 +1653,8 @@ function renderFsCustomPathsSubForm(parentEl, masterOn, fsOn) {
       ? d.deny_floor.join(', ')
       : '.storage, secrets.yaml';
   info.innerHTML =
-    `<div class="feature-name">${escapeHtml(t('filesystem.custom.title', {}, 'Custom filesystem directories (advanced)'))}</div>` +
-    `<div class="feature-help">${tHtml('filesystem.custom.help', {}, 'Extra directories (one per line) that the file tools may READ and WRITE, either relative to your config dir or an absolute allowed HAOS sibling volume. Each entry grants both read and write. Applies immediately; no restart needed.')}</div>` +
+    `<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>, <code>/ssl</code>, and <code>/backup</code> are supported. Each entry allows that path and anything below it. 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.blocked', {paths: `<code>${escapeHtml(denyList)}</code>`}, 'Always blocked (cannot be added): {paths}, path traversal (<code>..</code>), and any absolute path outside the HAOS sibling volumes.')}</div>`;
 
   const control = document.createElement('div');
@@ -1674,7 +1674,7 @@ function renderFsCustomPathsSubForm(parentEl, masterOn, fsOn) {
     const note = document.createElement('div');
     note.className = 'feature-locked-note';
     note.textContent =
-      d.reason || t('filesystem.custom.unavailable', {}, 'Custom directories are currently unavailable.');
+      d.reason || t('filesystem.custom.unavailable', {}, 'Custom paths are currently unavailable.');
     control.appendChild(note);
   } else {
     const ta = document.createElement('textarea');
@@ -1684,7 +1684,7 @@ function renderFsCustomPathsSubForm(parentEl, masterOn, fsOn) {
     const btn = document.createElement('button');
     btn.id = 'fsCustomPathsSave';
     btn.className = 'adv-save-btn';
-    btn.textContent = t('filesystem.custom.save', {}, 'Save directories');
+    btn.textContent = t('filesystem.custom.save', {}, 'Save paths');
     btn.addEventListener('click', saveFsCustomPaths);
     const status = document.createElement('div');
     status.id = 'fsCustomPathsStatus';

{ha_mcp_dev-8.3.0.dev2472 → ha_mcp_dev-8.3.0.dev2473/src/ha_mcp_dev.egg-info}/PKG-INFO

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