Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split manual and UI configuration not working #117322

Open
mikaelhertzman opened this issue May 12, 2024 · 0 comments
Open

Split manual and UI configuration not working #117322

mikaelhertzman opened this issue May 12, 2024 · 0 comments

Comments

@mikaelhertzman
Copy link

The problem

Following these instructions and examples the expected result is for Home Assistant to store automations created manually and in the UI in separate specified paths.

Instead it seems that manual scripts are correctly loaded but anything created in the UI is stored in the default path (next to configuration.yaml) and not in the designated path/file.

I have recreated this issue in two separate installations of Home Assistant, my main installation and a new clean installation without any additional extensions/plugins/integrations.

(configuration.yaml used to recreate the issue is attached below)

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

https://www.home-assistant.io/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml

Diagnostics information

No response

Example YAML snippet

# Loads default set of integrations. Do not remove.
default_config:

lovelace:
mode: yaml

# Load frontend themes from the themes folder
frontend:

themes: !include_dir_merge_named themes

# My own handmade automations
automation manual: !include_dir_merge_list automations/

# Automations I create in the UI
automation ui: !include ui/automations.yaml

# Scripts I create in the UI
script ui: !include ui/scripts.yaml

# My own handmade scripts
script manual: !include manual/scripts.yaml

scene: !include scenes.yaml

Anything in the logs that might be useful for us?

Can't find any thing in the logs indicating any issues with my configuration

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant