search

hassio-addons / addon-appdaemon

AppDaemon4 - Home Assistant Community Add-ons
https://addons.community
MIT License
141 stars 45 forks source link

HAASIO 2024.04 AppDaemon fails to start after initial installation #337

Closed leprechaun17 closed 1 month ago

leprechaun17 commented 2 months ago

Problem/Motivation

AppDaemon app fails to start after initial installation

Expected behavior

To actually start

Actual behavior

Error associated with secrets.yaml file not found. Not Appdaemon folder or yaml files are created to modify.

Steps to reproduce

See log info: s6-rc: info: service legacy-services: starting [10:54:34] INFO: Starting AppDaemon... s6-rc: info: service legacy-services successfully started Traceback (most recent call last): File "/usr/bin/appdaemon", line 8, in ERROR Error loading secrets file: /config/secrets.yaml 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

thouters commented 2 months ago

I have the same issue, my config/appdaemon folder appears empty as well o_O

tjorim commented 2 months ago

Make sure you have a secrets.yaml in your add-on config directory. It's not the same as the home assistant config directory.

thouters commented 2 months ago

I hit the update button by accident this morning instead of start. I tried resetting to default settings using the addon UI. Now it seems my scripts and dashboard are gone in my hassio vscode instance. Will have to investigate tonight.

thouters commented 2 months ago

Regarding the issue I reported. So I hit the update button by accident, and no questions asked it upgraded me past https://github.com/hassio-addons/addon-appdaemon/releases/tag/v0.15.2 - which moves the configuration to a container specific share. My configuration was moved there. After changing the secrets path it worked again like before. I suspect people who have auto update on will have breakage because of things like that. Perhaps if the addon can move config, it can do a simple find and replace in the configfile too next time?

github-actions[bot] commented 1 month ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!