fix: use correct method get_entity_registry_list() instead of get_entity_registry()

- Fixed bug where delete_automation tried to call non-existent get_entity_registry() method
- Changed to get_entity_registry_list() which is the correct method name
- This fixes ghost entry removal from Entity Registry when automation not found in storage

Author: Coolver

CHANGELOG.md

@@ -2,6 +2,43 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.10.34] - 2026-01-27
+
+### 🚀 API-based automation & script management + Security fix
+
+**Breaking the file structure barrier: Now works with ALL automations and scripts, regardless of where they live**
+
+#### The Problem We Solved
+
+Previously, the agent could only see and manage automations and scripts that were stored in the traditional `automations.yaml` and `scripts.yaml` files. This created a frustrating limitation for users with mature Home Assistant setups:
+
+- **Users with packages**: If you organized your config using `packages/*.yaml` files (a common practice for larger installations), the agent couldn't see those automations/scripts
+- **UI-created automations**: Automations created through Home Assistant's web interface are stored in `.storage` and were completely invisible to the agent
+- **Mixed setups**: Many users have a mix of file-based and UI-created automations, but the agent could only work with the file-based ones
+
+**Real-world impact**: A user reported having 159 automations in their system, but the agent could only see 4 of them (the ones in `automations.yaml`). The other 155 automations were invisible and unmanageable through the agent.
+
+#### The Solution
+
+We've completely rebuilt how the agent interacts with automations and scripts. Instead of reading and writing YAML files directly, the agent now uses Home Assistant's official WebSocket API (`config/automation/list`, `config/script/list`, etc.). This means:
+
+- ✅ **See everything**: `list_automations` and `list_scripts` now return ALL automations/scripts that Home Assistant knows about, regardless of where they're stored:
+  - From `automations.yaml` / `scripts.yaml` (traditional files)
+  - From `packages/*.yaml` files (organized configs)
+  - Created via UI (stored in `.storage`)
+- ✅ **Get individual items**: You can now fetch a specific automation or script by ID using `get_automation` or `get_script`, without loading entire YAML files
+- ✅ **List IDs only**: Both endpoints support `ids_only=true` parameter to get just a list of IDs without full configurations, saving tokens and context
+- ✅ **Create/update/delete via API**: All write operations now go through Home Assistant's API, so they work regardless of your file structure
+- ✅ **Smart Git versioning**: After each operation, the agent exports the current state of all automations/scripts to Git in `export/automations/<id>.yaml` and `export/scripts/<id>.yaml` format, creating a complete history
+- ✅ **Intelligent rollback**: When rolling back to a previous Git commit, the agent detects exported automations/scripts and applies them via API, ensuring consistent restoration
+- ✅ **Backwards compatible**: Old Git commits (without the export/ structure) still work via file-based rollback, so your existing backups remain functional
+
+**Result**: That user with 159 automations? Now all 159 are visible and manageable. No more file structure limitations.
+
+#### Security Fix (from PR #22)
+
+- ✅ **Secure API key regeneration**: The `/api/regenerate-key` endpoint now requires authentication (valid API key in `Authorization: Bearer <key>` header) to prevent unauthorized key regeneration from arbitrary web pages. Previously, any website could call this endpoint and regenerate your API key without authentication, creating a critical security vulnerability. The UI still works seamlessly by passing the current key in the request header when regenerating keys.
+
 ## [2.10.33] - 2026-01-27
 
 ### 🚀 API-based automation & script management + Security fix

README.md

@@ -1,6 +1,6 @@
 # HA Vibecode Agent - Home Assistant Add-on
 
-[![Version](https://img.shields.io/badge/version-2.10.33-blue.svg)](https://github.com/Coolver/home-assistant-vibecode-agent)
+[![Version](https://img.shields.io/badge/version-2.10.34-blue.svg)](https://github.com/Coolver/home-assistant-vibecode-agent)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![MCP Package](https://img.shields.io/npm/v/@coolver/home-assistant-mcp?label=MCP%20Package)](https://www.npmjs.com/package/@coolver/home-assistant-mcp)
 

app/main.py

@@ -26,7 +26,7 @@
 logger = setup_logger('ha_cursor_agent', LOG_LEVEL)
 
 # Agent version
-AGENT_VERSION = "2.10.33"
+AGENT_VERSION = "2.10.34"
 
 # FastAPI app
 app = FastAPI(

app/services/ha_client.py

@@ -781,7 +781,7 @@ async def delete_automation(self, automation_id: str) -> Dict:
                     ws_client = await get_ws_client()
 
                     # Get Entity Registry to find automations by alias
-                    entity_registry = await ws_client.get_entity_registry()
+                    entity_registry = await ws_client.get_entity_registry_list()
                     automation_entities = [e for e in entity_registry if e.get('entity_id', '').startswith('automation.')]
 
                     # Normalize automation_id for alias matching
@@ -872,7 +872,7 @@ async def delete_automation(self, automation_id: str) -> Dict:
                     pass
 
                 # Get Entity Registry to find all matching automations
-                entity_registry = await ws_client.get_entity_registry()
+                entity_registry = await ws_client.get_entity_registry_list()
                 automation_entities = [e for e in entity_registry if e.get('entity_id', '').startswith('automation.')]
 
                 # Get actual entity_id from location if available

config.yaml

@@ -1,6 +1,6 @@
 # Home Assistant Add-on Configuration
 name: HA Vibecode Agent
-version: "2.10.33"
+version: "2.10.34"
 slug: home_assistant_cursor_agent
 description: "Enable Cursor, VS Code, Claude Code, or any MCP-enabled IDE to help you vibe-code and manage Home Assistant: create and debug automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language"
 url: https://github.com/Coolver/home-assistant-cursor-agent