Moving automation from UI to "manual" messes up its display/formatting, as if no blueprint anymore

Configuration
1

I try to save stable bits of my config to easily redeploy on new hardware.
So I’ve moved bits of automations.yaml to another folder and refactored configurations.

My problem is that the blueprint formatting of the automation disappeared and I wonder if it’s expected or if I misconfigured something.

I used to see this nice blueprint-based formatting:

image
image1107×727 55.2 KB

and the same one (or very close) once converted to a non-ui automation:

image
image1599×706 48.3 KB

I dont mind it being readonly, but I see no reason why it should lose the blueprint formatting ? Is this normal ? I see no error on load, the blueprint is still here in the correct location (I think).

Here is how I updated configuration.yaml:

# I've seen the tag "manual" in a nixos test and even after reading the doc,
# I dont know if the label "manual" is arbitrary or if it's some official value from home-assistant ?:
automation manual: !include_dir_list /nix/store/g1f2mzs97qrmsbv5bl4di80bvgfh4s6z-automations
automation ui: !include automations.yaml

with

$ ls /nix/store/g1f2mzs97qrmsbv5bl4di80bvgfh4s6z-automations
hue-dimmer1.yaml
$ head /nix/store/g1f2mzs97qrmsbv5bl4di80bvgfh4s6z-automations/hue-dimmer1.yaml
id: '1790284003170'
alias: dimmer-1-salon
description: ''
use_blueprint:
  path: blueprint-hue-switch.yaml
  input:
    remote: 2c377411ae73ec3db6c19e51b4abd370
    double_click_delay: 400
    on_single_press:
    - action: light.turn_on

To sum up, is it expected my display changed when converting the automation to “manual” ? or should I check my config again ?

Best regards,
Matt

possibly related: Getting "This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn't have an ID." when opening automation

2

It’s now just showing the blueprint output, which is the automation and is expected.

3

thanks for confirming it’s expected. Since the only difference with the content in automation.yaml is that it’s now in a read-only file, is there hope to see the same interface as in the original automation (even if it’s read-onlu) ? I found it more understanble/parsable. I think I read in other posts that HA wouldn’t because someone might alter the yaml content but I believe blueprint standardize the output so if it fails the check the display could revert to the current “raw” mode and otherwise (ie, successful parsing) show the nice blueprint view.

Thanks for all that you do, home-assistant is amazing. I have a working local voice setup with the voice preview I bought to support nabucasa.