Path to YAML Files broken

[birdwing]

Ever since your recent changes where you moved the YAML files into the /config folder I have been unable to update the plugs through ESPHome in Home Assistant.

If I leave my ESP yaml file unchanged:

substitutions:
  name: "bedroom-fan"
  friendly_name: "Bedroom Fan"
  disable_webserver: "true"
packages:
  kauf.plf12: github://KaufHA/PLF12/kauf-plf12-lite.yaml
esphome:
  name: ${name}
  name_add_mac_suffix: false
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

And attempt to install I get the following error:

INFO ESPHome 2024.5.2
INFO Reading configuration /config/esphome/bedroom-fan.yaml...
Failed config

packages: [source /config/esphome/bedroom-fan.yaml:6]
  
  Failed to load packages. kauf-plug-lite.yaml does not exist in repository.
  kauf.plf12: github://KaufHA/PLF12/kauf-plf12-lite.yaml

Which.. make sense. The file was moved.
So I updated my ESP yml file to have the new location for kauf-plf12-lite.yaml:

substitutions:
  name: "bedroom-fan"
  friendly_name: "Bedroom Fan"
  disable_webserver: "true"
packages:
  kauf.plf12: github://KaufHA/PLF12/config/kauf-plf12-lite.yaml
esphome:
  name: ${name}
  name_add_mac_suffix: false
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

And I get the same error message:

INFO ESPHome 2024.5.2
INFO Reading configuration /config/esphome/bedroom-fan.yaml...
Failed config

packages: [source /config/esphome/bedroom-fan.yaml:6]
  
  Failed to load packages. config/kauf-plf12-lite.yaml does not exist in repository.
  kauf.plf12: github://KaufHA/PLF12/config/kauf-plf12-lite.yaml

This makes no sense to me, I am very confused.

[bkaufx]

That is pretty weird. That file exists and it's working for me so not sure what is going on your end. You might clean build files or delete .esphome/packages directory.

[birdwing]

Even Cleaning the Build files returns the "does not exist in repository" error.

I can't find the .esphome/packages directory.
Where do they put that on Home Assistant?

[birdwing]

So apparently the solution is to uninstall the ESPHome Addon and then Re-install it.

After that everything updated just fine. No idea what ESPHome was holding onto.. but a re-install seemed to fix it.
Figured I would update this just in case anyone else runs into the same issue as me with this change 👍

[bkaufx]

Ok good. ESPHome hides the .esphome directory in docker for the add-on and kind of questions people pretty harshly if they ask about it. But then ESPHome is regularly burping in weird ways that requires you to clear it manually.

[birdwing]

Thought I was losing my mind 😂