Something happened, and AppDaemon won’t start anymore. I get an error about opening secrets.yaml, but I haven’t changed anything here since May 5th.
I did open the HA config in PyCharm, and accidentally clicked “add interpreter”, but afterwards deleted the venv folder. Other than that, I can’t think of anything that changed when it stopped working (well, updated ESPHome, but pretty sure that isn’t it?)
This is what I see in the AppDAemon logs:
ERROR Error loading secrets file: /config/secrets.yaml
Traceback (most recent call last):
File "/usr/bin/appdaemon", line 8, in <module>
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:
^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable
[15:47:03] INFO: Service AppDaemon exited with code 1 (by signal 0)
Same here. I updated to latest AppDaemon and now it wont start with the same error as Aephir.
Edit: it also cleared my appdaemon folder in /homeassistant/ and put it into /addon_configs/a0d7b954_appdaemon. Tried to put it back but no difference.
There is definitely something broken now. The logs say it’s loading config/appdaemon.yaml and no such file exists. I’m not sure what is going on. I’ll guess i’ll try and revert back to v14
which backup you restore , in unziped appdemon a don’t see appdeamon.yaml
i don’t understand
With this release, the appdaemon data folder will migrate/move out of the Home Assistant configuration folder into a dedicated folder for this add-on. You can access add-on configuration folders using SSH, Samba, VSCode, and similar add-ons by accessing the addon_configs folder/share.
If you have this in your appdaemon.yaml file:
secrets: /config/secrets.yaml
You will need to adjust this to:
secrets: /homeassistant/secrets.yaml
I undid my restore and did as suggested with the addon configs folder and got it working. Probably should’ve read through before jumping off the ship haha
@Bxsteez Don’t feel bad, I managed to install a completely new VM to restore and copy my Appdaemon config from before realizing…
@przemsi However you mount the “config” where the AppDaemon config used to be. I use the SambaShare addon, but how you do doesn’t really matter. If you (as it seems) have CLI access, you might as well just open and modify the appdaemon.yaml with nano, vi, or whatever you use in CLI.
In my case the only thing I did was edit the appdaemon.yaml file in its new directory.
The error was it could find /config/secrets.yaml and I noticed the config files were moved to addon_config/a0d7b954_appdaemon when I opened the network folder via SAMBA so I just edited the file there, restarted and it worked just fine.
So if you can try that first to see if it works for you too.
Just read the post. I also started with trying to restore to get the AppDaemon config because I didn’t read what was going on.
To make it easier for people finding this thread (instead of the older one that also solves the problem, the one I didn’t search for before creating this), I’ve marked the post as solution:
With this release, the 