Just like we have in automations that we can add blocks of automations with different labels.
Currently, if you have a single automation that uses !secret, you won’t be able to use the Automation Editor at all.
File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 304, in secret_yaml
raise HomeAssistantError("Secrets not supported in this YAML file")
homeassistant.exceptions.HomeAssistantError: Secrets not supported in this YAML file
The way I circumvented it was creating a group of automation labeled as “manual” that only is modified manually.
Just like so:
automation manual: !include_dir_merge_list automations # labeled automations - it works!
automation: !include automations.yaml
Today, I found out that Script Editor has the same behavior of Automation Editor, I mean, when a single script uses !secret, then the Script Editor doesn’t work at all for the exact same reason.
So, my request is to be able to do something like:
script manual: !include_dir_merge_list scripts # labeled scripts - feature request
script: !include scripts.yaml
This way, I could separate the scripts that use !secret to update them manually and be able to use Script Editor again.