Quick reload not actually reloading YAML

Hi,
I’ve set up a simple shell_command in my configuration.yaml like this:

shell_command:
  touch_file: touch /backup/touch

I can run it from Developer Tools / Services (although it throws an error but that’s a different discussion).
Now I’d like to change the path of the file I’m touching.
After doing so, I go to Developer Tools / YAML / Restart.
I find a new option “Quick reload, Load new YAML configurations without a restart”. I remember reading about it and get excited. I press “Quick reload” and go back to debugging my shell_command only to find out that “Quick reload” did not reload my configuration.yaml file and is still using the old path configured in my shell_command.

Did nobody test this or am I doing things wrong or am I misinterpreting what Quick reload is supposed to be doing?

Cheers

I believe the shell_command needs a restart of HA. Where is this quick reload you are speaking off?

Like I said, Developer Tools / YAML, then hit the restart button in “Check and Restart”.
Needs a fairly recent version of HA. I’m running 2023.3.5

If you go to Developer Tools → YAML you will see a list of all the reloadable integrations.

1 Like

So if something it’s on this list, for example, Sensors, then this requires a restart of Home Assistant to apply changes?

No the exact opposite. If it is on the list it can be quick reloaded.

1 Like

Why is there a “Quick reload” that says “Loads new YAML configurations without a restart” but it only applies to that list of configurations in the “YAML configuration reloading” section, which is already reloadable by clicking “All YAML configuration”. The lack of disclaimer in the “Quick reload” dialog about it only applying to a certain subset of YAML configurations led me to a problem where I didn’t realize logger was one of the excluded configurations. It seems like there should either be more clarity in the “Quick reload” subtext, remove that option entirely, or, ideally, support YAML reloading for all core components.

1 Like

Have to say I agree. Almost lost my nerve when trying to set up EMHASS. Just couldn’t understand why, no matter what I did, I couldn’t repair an error. In the end, none of the repairs was updated, but I had all my faith in “Update whole yaml-configuration” (in Finnish). I suggest, a small note about this is put there. I’m sure it would change a lot of frustration.

There’s another caveat too. If it is the first time you are using one of the reloadable integrations you still have to restart. After that you can reload when making additions/changes.

Thanks, understood!

One extra point. I decided to follow advice elsewhere and switched all my shell commands for EMHASS to rest commands. Was pleasently surprised to find that one included in the list of yaml config entities with a quick reload button. As an extra to easier debugging, reading code is much more intuitive.