Editing scripts in UI with legacy scripts

Configuration
Tags: #<Tag:0x00007f3270914548>
#1

I have been using HA a long time so all of my scripts were created by hand. I have a bunch of files in a scripts directory and my configuration.yaml has this…

####################################
# Scripts
####################################
script: !include_dir_merge_named scripts

I created a new script with the fancy new UI and after I saved it I couldn’t find it. After some looking I found the new script in a scripts.yaml file in my config directory but my configuration does not read that file.

How can I use both sources? My scripts folder AND the scripts.yaml file the UI creates.

#2

I don’t think you can !
If you want to use the UI editor and the single scripts.yaml file you would need to remove the !include line in your configuration

#3

That is a good question. It can be accomplished with Automations, however I cannot get this same trick to work with scripts.

automation yaml: !include_dir_merge_named automations
automation: !include automations.yaml
#4

It should work fine with script

1 Like
#5

Oh, you are correct sir! Thank you for pushing me to try it again.

@oliwa this works for me. You have to restart for it to take effect.

script yaml: !include_dir_marge_named scripts
script: !include scripts.yaml
#6

I did that and when I reload the scripts all of my old scripts are gone and just the ones in the script.yaml are in the scripts list.

####################################
# Scripts
####################################
script yaml: !include_dir_merge_named scripts
script: !include scripts.yaml
#7

Your old scripts will only show up in the devtool states page. Also, if you’re dead set on using the UI, just copy/paste the scripts into your scripts.yaml. Then you can edit your old ones and new ones.

#8

All of the scripts in my Lovelace UI are not found now so I can’t run any of them.

#9

but when you restart they do show up? Could be a reload issue.

#10

also, lovelace does not equal dev tools states page

#11

Restarting did not change the behavior.

Yes, I know what the Dev Tools States page is. Having to go there to run a script where before I could click the script from Lovelace is not a viable option for me.

#12

I reverted back to using script: !include_dir_merge_named

#13

It’s not intended, I wanted you to check to verify that they still existed in the system. Responding with “lovelace doesn’t show them” tells me you didn’t read my sentence and decided to blurt something else out.

#14

I reloaded, only one script in the dev tools.

I restarted, only one script in dev tools.

With this…

####################################
# Scripts
####################################
script yaml: !include_dir_merge_named scripts
script: !include scripts.yaml

The scripts are only loaded from the scripts.yaml file. Nothing is loaded from the directory.

#15

I just came here to tell you trying this made all of my yaml scripts disappear. That’s why I didn’t have that enabled. Haha.

#16

Hi,
i can confirm, it’s also not working in my case.