That really doesn’t make sense to me ?
You need to find that “sentence” in your appdaemon.yaml file.
-
Open your
appdaemon.yamlfile. The location has changed, so you need to follow the instructions in this thread (and several others) to find it after the update to addon file storage. -
Then find the line in
appdaemon.yamlthat mentionssecrets.yaml, most likely it’s one of the first lines, and most likely the full line sayssecrets: /config/secrets.yamlif you have not updated it since the new addon file structure. -
Change this line to
secrets: /homeassistant/secrets.yaml, since this is how the addons reference anything in your oldconfigdirectory, i.e., the one wheresecrets.yamlis located if you have followed Home Assistant instructions for setting it up.
This is ho my appdaemon.yaml looks now, the highlighted line (first line) is what was previously secrets: /config/secrets.yaml:
1 Like
@Aephir your ‘appdaemon.yaml’ file is identical to mine, however when I start the appdaemon addon I get the following errors reported in the logs:
ERROR Error loading secrets file: /homeasistant/secrets.yaml
Traceback (most recent call last):
File “/usr/bin/appdaemon”, line 8, in
sys.exit(main())
^^^^^^
File “/usr/lib/python3.11/site-packages/appdaemon/main.py”, line 417, in main
admain.main()
File “/usr/lib/python3.11/site-packages/appdaemon/main.py”, line 276, in main
if “appdaemon” not in config:
So clearly in my instance secrets: /homeasistant/secrets.yaml is not the right path referencing.
Weird, but it looks like the same as here.
Where is you secrets.yaml? It’s in the base directory of Home Assistant (same folder as configuration.yaml), right?
You did update so you have the addon mounts as separate from the homeassistant/config mounts, right? That is, in the base directory where you have configuration.yaml (and secrets.yaml), there should be no appdaemon directory (or if there is, it should be empty).
Yes - my secrets.yaml file is in the same place its been since I began using Home Assistant in 2016, in the /config folder, now renamed the /homeassistant folder.
With regard to your query about the add on mounts, I’m not following you on that one. There is no appdaemon directory in my /homeassistant folder.
My Home Assistant install is via the HA OS method, running on a Rpi4 off a 32Gb SSD card. With the latest install documentation its the installation method as described here:
https://www.home-assistant.io/installation/#diy-with-raspberry-pi
In that context I’m presuming appdaemon, like other add-ons, is running, with HA supervision, in its own docker container independent of the HA container, but is set-up to access the HA container file structure for configuration and data files.
appdaemon all works fine save that clearly I don’t yet understand how to guide appdaemon where to find the /homeassistant folder relative to its own configuration folder, which is at the path /addon_configs/xxxxxxxx.appdaemon. I’m presuming that both the /homeassistant and the /addon_configs folder are at the root level in the HA docker container.
OK, that sounds correct. The addon_configs/ is the “new” mount that appeared in late 2023 (if you kept everything up to date), where all… well, addon configs, are now located (basically the “persistent data” for the docker containers).
Not really sure what to say in that case (well, maybe check for typo’s, the first time I tried, it was pretty late, and I copied someone elses typo: /homeasistant/secrets.yaml 
)
one thing I completely don’t understand about this entire setup: I don’t have a folder ‘homeassistant’ ?!
I’m running HA inside a VM on a windows 10 laptop.
And something else please; from the update 2024.4 there was a change in appdeamon yes?
That is why users with the NSpanel having isssues showing the weather card on the screensaver?
You should add this line to appdeamon.yaml: app_dir /homeassistant/apps but does this work without the actual folder ‘homeassistant’ ??
As I understood it, it’s the folder named config, that Appdaemon (and other addons) now calls homeassistant. So it’s just (mostly) an internal reference issue.
These are the “folders” (mounts) I have when using the Samba share addon:
.
The one highlighted (config) is where I have my secrets.yaml, configuration.yaml, etc., but in appdaemon.yaml (now located on the other highlighted mount: addon_configs in a subfolder named something with XXX_appdaemon), it’s now referenced as /homeassistant/secrets.yaml, not /config/secrets.yaml as it “used to”.
Thank you, simple is always best. Done in a few seconds using the ever dependable File editor add-on.
Was getting very confused with all this talk of mounting and copying things, none of which are necessary.
Thanks for the help in this post. I solved it by just deleting the whole \addon_configs\a0d7b954_appdaemon directory.