Add show-automation-editor event for custom cards & panels

[philippwaller]

Proposed change

Expose showAutomationEditor(data?: Partial<AutomationConfig>, expanded?: boolean) as a public method on the ha-panel-custom. This allows custom panels (iframes) to open the Automation Editor prefilled with data.

Add a new event for show-automation-editor. This allows custom cards & panels to open the Automation Editor prefilled with data.

Until now, only the core UI could open the automation editor prefilled. Custom panels (iframes) had no way to do this, because the editor initialization (initialAutomationEditorData) was only accessible inside the main app. By exposing showAutomationEditor, embedded panels can now trigger the same flow and hand over prefilled data.

Use case:
For the KNX integration we provide a Telegram Monitor. This tool shows how KNX devices on the network exchange messages with each other (e.g., a wall switch sending a telegram to a light actuator). We want to add a feature that lets the user create an automation directly from such a telegram, like so:

create_automation_from_group_monitor.mov

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[MindFreeze]

I wonder if should just expose this on the hass object so it is available everywhere

[philippwaller]

I wonder if should just expose this on the hass object so it is available everywhere

Thanks a lot for the feedback!
I actually followed the approach used for navigate, which is also exposed to custom panels for the same reason. Since this change is only relevant for external panels, I felt it was more consistent to keep it at the panel level.

[MindFreeze]

The frontend team discussed this and we agreed that this should be exposed but as an event similar to more-info. This way it can be used by custom cards as well.

Side note: the navigate method seems to not be needed anymore as it always uses the main window now

[philippwaller]

Great! I’ve just updated the PR to expose it as an event.

[Copilot]

Pull Request Overview

This PR adds support for custom cards and panels to open the Home Assistant Automation Editor with prefilled data by introducing a new show-automation-editor event. Previously, only the core UI could programmatically open the automation editor with initial data, limiting the functionality available to custom integrations and panels.

Key changes:

• Creates a new mixin that handles show-automation-editor events and delegates to the existing showAutomationEditor function
• Adds the mixin to the base HassElement class to make the functionality available throughout the application
• Defines proper TypeScript interfaces for the event parameters

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/state/hass-element.ts	Imports and applies the new AutomationEditorMixin to the base HassElement class
src/state/automation-editor-mixin.ts	New mixin that listens for show-automation-editor events and handles them
src/data/automation.ts	Adds TypeScript interface definitions for the new event and its parameters

[MindFreeze]

Thank you!