You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
# Loads default set of integrations. Do not remove.default_config:
lovelace:
mode: yaml# Load frontend themes from the themes folderfrontend:
themes: !include_dir_merge_named themes# My own handmade automationsautomation manual: !include_dir_merge_list automations/# Automations I create in the UIautomation ui: !include ui/automations.yaml# Scripts I create in the UIscript ui: !include ui/scripts.yaml# My own handmade scriptsscript manual: !include manual/scripts.yamlscene: !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
The text was updated successfully, but these errors were encountered:
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
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: