AppDaemon stops after updating to 0.15.0 #287

PeterAndreS · 2023-11-15T10:49:39Z

Problem/Motivation

(Why the issue was filed)
Stoped working!

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)
Latest update of AppDaemon:

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Log:

Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/
Collecting influxdb
  Obtaining dependency information for influxdb from https://wheels.home-assistant.io/musllinux-index/influxdb-5.3.1-py2.py3-none-any.whl.metadata
  Downloading https://wheels.home-assistant.io/musllinux-index/influxdb-5.3.1-py2.py3-none-any.whl.metadata (6.0 kB)
Requirement already satisfied: python-dateutil>=2.6.0 in /usr/lib/python3.11/site-packages (from influxdb) (2.8.2)
Requirement already satisfied: pytz in /usr/lib/python3.11/site-packages (from influxdb) (2023.3.post1)
Requirement already satisfied: requests>=2.17.0 in /usr/lib/python3.11/site-packages (from influxdb) (2.28.2)
Requirement already satisfied: six>=1.10.0 in /usr/lib/python3.11/site-packages (from influxdb) (1.16.0)
Collecting msgpack (from influxdb)
  Downloading https://wheels.home-assistant.io/musllinux-index/msgpack-1.0.7-cp311-cp311-musllinux_1_2_x86_64.whl (240 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 240.6/240.6 kB 7.2 MB/s eta 0:00:00
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/lib/python3.11/site-packages (from requests>=2.17.0->influxdb) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3.11/site-packages (from requests>=2.17.0->influxdb) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/lib/python3.11/site-packages (from requests>=2.17.0->influxdb) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.11/site-packages (from requests>=2.17.0->influxdb) (2023.7.22)
Downloading https://wheels.home-assistant.io/musllinux-index/influxdb-5.3.1-py2.py3-none-any.whl (77 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.9/77.9 kB 10.5 MB/s eta 0:00:00
Downloading https://wheels.home-assistant.io/musllinux-index/influxdb-5.3.1-py2.py3-none-any.whl (77 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.9/77.9 kB 48.4 MB/s eta 0:00:00
Installing collected packages: msgpack, influxdb
Successfully installed influxdb-5.3.1 msgpack-1.0.7
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/
Collecting influxdb-client
  Downloading influxdb_client-1.38.0-py3-none-any.whl (743 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 743.5/743.5 kB 16.1 MB/s eta 0:00:00
Collecting reactivex>=4.0.4 (from influxdb-client)
  Downloading reactivex-4.0.4-py3-none-any.whl (217 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 217.8/217.8 kB 30.1 MB/s eta 0:00:00
Requirement already satisfied: certifi>=14.05.14 in /usr/lib/python3.11/site-packages (from influxdb-client) (2023.7.22)
Requirement already satisfied: python-dateutil>=2.5.3 in /usr/lib/python3.11/site-packages (from influxdb-client) (2.8.2)
Requirement already satisfied: setuptools>=21.0.0 in /usr/lib/python3.11/site-packages (from influxdb-client) (67.7.2)
Requirement already satisfied: urllib3>=1.26.0 in /usr/lib/python3.11/site-packages (from influxdb-client) (1.26.18)
Requirement already satisfied: six>=1.5 in /usr/lib/python3.11/site-packages (from python-dateutil>=2.5.3->influxdb-client) (1.16.0)
Collecting typing-extensions<5.0.0,>=4.1.1 (from reactivex>=4.0.4->influxdb-client)
  Downloading https://wheels.home-assistant.io/musllinux-index/typing_extensions-4.8.0-py3-none-any.whl (31 kB)
Installing collected packages: typing-extensions, reactivex, influxdb-client
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Successfully installed influxdb-client-1.38.0 reactivex-4.0.4 typing-extensions-4.8.0
Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/
Collecting pyeloverblik
  Downloading pyeloverblik-0.4.1-py3-none-any.whl (10 kB)
Requirement already satisfied: requests in /usr/lib/python3.11/site-packages (from pyeloverblik) (2.28.2)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/lib/python3.11/site-packages (from requests->pyeloverblik) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3.11/site-packages (from requests->pyeloverblik) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/lib/python3.11/site-packages (from requests->pyeloverblik) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.11/site-packages (from requests->pyeloverblik) (2023.7.22)
Installing collected packages: pyeloverblik
Successfully installed pyeloverblik-0.4.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/
Collecting pythermiagenesis
  Downloading pythermiagenesis-0.1.7-py3-none-any.whl (17 kB)
Collecting pymodbustcp==0.1.10 (from pythermiagenesis)
  Downloading pyModbusTCP-0.1.10.tar.gz (17 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Building wheels for collected packages: pymodbustcp
  Building wheel for pymodbustcp (setup.py): started
  Building wheel for pymodbustcp (setup.py): finished with status 'done'
  Created wheel for pymodbustcp: filename=pyModbusTCP-0.1.10-py3-none-any.whl size=16967 sha256=80bb452965f419b076c01d10bfe8cd09ccaf2ad63af106604764e73602b5e9e0
  Stored in directory: /tmp/pip-ephem-wheel-cache-z5irjpra/wheels/76/37/f4/816d7f608bcbac7b6dc96c59d366bf10af2ca12cc99bb207a3
Successfully built pymodbustcp
Installing collected packages: pymodbustcp, pythermiagenesis
Successfully installed pymodbustcp-0.1.10 pythermiagenesis-0.1.7
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
s6-rc: info: service init-appdaemon successfully started
s6-rc: info: service appdaemon: starting
s6-rc: info: service appdaemon successfully started
s6-rc: info: service legacy-services: starting
[11:40:58] INFO: Starting AppDaemon...
s6-rc: info: service legacy-services successfully started
Traceback (most recent call last):
  File "/usr/bin/appdaemon", line 8, in <module>
    sys.exit(main())
ERROR Error loading secrets file: /config/secrets.yaml
             ^^^^^^
  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
[11:41:01] INFO: Service AppDaemon exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service appdaemon: stopping
s6-rc: info: service appdaemon successfully stopped
s6-rc: info: service init-appdaemon: stopping
s6-rc: info: service init-appdaemon successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

The text was updated successfully, but these errors were encountered:

frenck · 2023-11-15T10:51:08Z

Thanks for the report, the config folder moved. Checking where this one is originating from...

../Frenck

dersch81 · 2023-11-15T10:51:29Z

Same for me, also using the backup back to 14.0 does not work anymore

-----------------------------------------------------------
 Add-on: AppDaemon
 Python Apps and Dashboard using AppDaemon 4.x for Home Assistant
-----------------------------------------------------------
 Add-on version: 0.15.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.1  (amd64 / qemux86-64)
 Home Assistant Core: 2023.11.2
 Home Assistant Supervisor: 2023.11.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-appdaemon: starting
s6-rc: info: service init-appdaemon successfully started
s6-rc: info: service appdaemon: starting
s6-rc: info: service appdaemon successfully started
s6-rc: info: service legacy-services: starting
[11:48:51] INFO: Starting AppDaemon...
s6-rc: info: service legacy-services successfully started
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
[11:48:54] INFO: Service AppDaemon exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service appdaemon: stopping
s6-rc: info: service appdaemon successfully stopped
s6-rc: info: service init-appdaemon: stopping
s6-rc: info: service init-appdaemon successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

PeterAndreS · 2023-11-15T11:00:08Z

Expected behavior folder name?

All files moved to new location as expected but is foldername okay?
addon_configs\a0d7b954_appdaemon

frenck · 2023-11-15T11:05:06Z

I've updated the breaking change section:

If you have this in your appdaemon.yaml file:

secrets: /config/secrets.yaml

You will need to adjust this to:

secrets: /homeassistant/secrets.yaml

dersch81 · 2023-11-15T11:08:22Z

where can i find the appdaemon.yaml?

/homeassistant/appdaemon is empty

Jabe · 2023-11-15T11:08:43Z

@frenck It reverts to secrets: /config/secrets.yaml on each start unfortunately.

kefrens · 2023-11-15T11:09:56Z

Facing same issue and as @Jabe mentionned its reverts to secrets: /config/secrets.yaml after each start :(

@dersch81 you can find it on \homeassistant\addon_configs\axxxxxxxx_appdaemon

frenck · 2023-11-15T11:14:05Z

The add-on configuration folders can be found in the add-on configuration shares. If you access it using samba, this share is called addon_configs.

If you are using SSH, VSCode or any other similar terminal, you can find them in /addon_configs.

../Frenck

dersch81 · 2023-11-15T11:16:41Z

same as @kefrens changed to /homeassistant/secrets.yaml but after restart it is reverted back to /config/secrets.yaml

mupsje · 2023-11-15T11:22:29Z

@frenck It reverts to secrets: /config/secrets.yaml on each start unfortunately.

yup, every time it restarts it changed back to

secrets: /config/secrets.yaml

PeterAndreS · 2023-11-15T11:24:50Z

When secrets: /homeassistant/secrets.yaml is set in a0d7b954_appdaemon\appdaemon.yaml
It reverts to secrets: /config/secrets.yaml an restarts.

When secrets is removed from yaml it starts but still looks in /config folder...

023-11-15 12:15:13.072835 WARNING AppDaemon: ------------------------------------------------------------
2023-11-15 12:15:13.073366 WARNING AppDaemon: File '/config/apps/testmodule.yaml' invalid structure - ignoring
2023-11-15 12:15:13.074813 INFO AppDaemon: /config/apps/testmodule.yaml added or modified
2023-11-15 12:15:13.075552 INFO AppDaemon: Found 1 active apps
2023-11-15 12:15:13.075724 INFO AppDaemon: Found 0 inactive apps
2023-11-15 12:15:13.075869 INFO AppDaemon: Found 0 global libraries
2023-11-15 12:15:13.076776 INFO AppDaemon: Adding /config/apps to module import path
2023-11-15 12:15:13.080232 WARNING AppDaemon: No app description found for: /config/apps/ems_genesis.py - ignoring
2023-11-15 12:15:13.080885 WARNING AppDaemon: No app description found for: /config/apps/ha_helper_updater.py - ignoring
2023-11-15 12:15:13.081500 WARNING AppDaemon: No app description found for: /config/apps/ems_genesis - org.py - ignoring
2023-11-15 12:15:13.081993 INFO AppDaemon: Loading App Module: /config/apps/hello.py
2023-11-15 12:15:13.109411 WARNING AppDaemon: No app description found for: /config/apps/testmodule.py - ignoring
2023-11-15 12:15:13.110084 WARNING AppDaemon: No app description found for: /config/apps/ems_electricity.py - ignoring
2023-11-15 12:15:13.110544 INFO AppDaemon: Loading app hello_world using class HelloWorld from module hello
2023-11-15 12:15:13.111792 INFO AppDaemon: Calling initialize() for hello_world
2023-11-15 12:15:13.148255 INFO hello_world: Hello from AppDaemon
2023-11-15 12:15:13.148979 INFO hello_world: You are now ready to run Apps!
2023-11-15 12:15:13.149956 INFO AppDaemon: App initialization complete
2023-11-15 12:16:33.158487 INFO AppDaemon: New client Admin Client connected

frenck · 2023-11-15T11:25:15Z

@pmansvelder Hidden your comment. An issue cannot be triaged by "I have the same problem". Please don't make such postings in any issue report. Thanks 👍

frenck · 2023-11-15T11:25:59Z

Looking into it, not fully understanding what makes it reverting it.

pmansvelder · 2023-11-15T11:28:30Z

Sorry, I will try to do better:
I installed 0.15, after this I noticed appdaemon stopped running; when looking in the log I saw the exact same message as above:

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

So I tried copying back my old config which has the line with /config/secrets.yaml commented out:

---
#secrets: /config/secrets.yaml
appdaemon:
  latitude: 52.379189
  longitude: 4.899431
  elevation: 2
  time_zone: Europe/Amsterdam
  plugins:
    HASS:
      type: hass
    MQTT:
      type: mqtt
      namespace: mqtt
      client_id: appdaemon
      client_host: core-mosquitto.local.hass.io
      client_port: 1883
      client_user: "mqtt-user"
      client_password: "mqtt"
      client_topics: NONE
http:
  url: http://127.0.0.1:5050
admin:
api:
hadashboard:

But when I started appdaemon it reverted back to the original config.
I have tried restarting homeassistant, but the problem persists.

I am using HomeAssistant Yellow with the Appdaemon add-on

dersch81 · 2023-11-15T11:31:00Z

Looking into it, not fully understanding what makes it reverting it.

Thanks for you effort. Seems both Add-On updates are now making you more busy than expected

frenck · 2023-11-15T11:31:24Z

Found the appdaemon issue. Will create a fix right away 🙏

frenck · 2023-11-15T11:32:17Z

Looking into it, not fully understanding what makes it reverting it.

Thanks for you effort. Seems both Add-On updates are now making you more busy than expected

LOL yeah, not the best combination of add-ons to have issues with atm 😓

../Frenck

pmansvelder · 2023-11-15T11:35:08Z

Found the appdaemon issue. Will create a fix right away 🙏

Thanks for the quick reply, didn't mean to troll like that, I appreciate your work very much, it has made configuring and using HA a breeze in comparison with the manual installation I used before…

frenck · 2023-11-15T11:36:16Z

@shamal69 That seems completely wrong! Please nobody use that ⚠️

Hid that comment to prevent other destroying stuff.

frenck · 2023-11-15T11:37:41Z

Found the appdaemon issue. Will create a fix right away 🙏

Thanks for the quick reply, didn't mean to troll like that, I appreciate your work very much, it has made configuring and using HA a breeze in comparison with the manual installation I used before…

Oh I'm more mad at myself for having shipped these bugs in the first place. I do test a lot and care a lot about these things. Anyways, at least it shows I'm still human.

dersch81 · 2023-11-15T11:40:47Z

You can not be human you are doing to much awesome stuff normally. Only having a bad day. Now go back to be inhuman software guy as usual to feed us with amazing HA stuff every day!!11!!11!!111!!1

frenck · 2023-11-15T11:42:31Z

Shipped v15.0.2: https://github.com/hassio-addons/addon-appdaemon/releases/tag/v0.15.2

PeterAndreS · 2023-11-15T12:04:53Z

0.15.1
Now appdaemon starts without revers secrets setting.
Note: I had to manually add my modules in apps.yaml again.
And logging is removed from a0d7b954_appdaemon\appdaemon.yaml. (No log files.)

Old settings in appdaemon.yaml, how to refere to new location?
logs:
main_log:
filename: /config/appdaemon/logs/appdaemon.log

I tried this:
logs:
main_log:
filename: /addon_configs/a0d7b954_appdaemon/logs/appdaemon.log
Result:
FileNotFoundError: [Errno 2] No such file or directory: '/addon_configs/a0d7b954_appdaemon/logs/appdaemon.log'

vaibhav2912 · 2023-11-29T04:49:21Z

ℹ️ The solution

Important, v0.15.0 & v0.15.1 have an issue with failing to detect the migration that already happened.

That is unfortunate, but it did happen and didn't show up in testing, unfortunately 😭

If you have upgraded from v0.14 or older to v0.15.0 or v0.15.1 you will encounter a migration problem.

To solve this:

Restore a backup (AppDaemon + home assistant config as that is where the appdaemon config is stored)

Clear out the AppDaemon folder in /addon_configs/, which contains the invalid migration. You can access this folder using the terminal add-on or using the addon_configs share provided by the Samba add-on.

Once you are back up and running on the previous version, upgrade to v0.15.2.

I've addressed the issue as quickly as possible, but I cannot revert what has been done.

I'm mostly mad at myself right now, and I'm deeply sorry this happened.

Sorry for the issue this might have caused for you 🙏

../Frenck

I followed this and after update to 0.15.2, updated secret file location to secrets: /homeassistant/secrets.yaml but appdaemon addon still didn't start. The error was log file location.
Before and after update, my appdaemon.yaml file had following for logs,

logs:
main_log:
filename: /config/appdaemon/logs/appdaemon.log
access_log:
filename: /config/appdaemon/logs/access.log
error_log:
filename: /config/appdaemon/logs/error.log
diag_log:
filename: /config/appdaemon/logs/diag.log

Appdaemon addon complained that it can't find this location so I changed it to /addon_config/a0d7b954_appdaemon/logs which is where my logs folder was moved to after addon update to 0.15.2 but it still didn't like that.
So I finally got appdaemon to start up on 0.15.2 by changing my logs storage location to /homeassistant/appdaemon/logs/ folder (any folder in /homeassistant/ [which is just another name for /config/] would work)

Surely there must be a way to allow HACS installs with AppDaemon to still work correctly?

HACS runs in Home Assistant, Home Assistant itself has no access to the add-on configuration folders.

Based on this, homeassistant can't access /addon_config/a0d7b954_appdaemon/ folder. So we can't store logs in /addon_config/a0d7b954_appdaemon/ folder anymore, correct ?

danVnest · 2023-11-29T06:25:31Z

I had the same problem. @frenck mentioned somewhere else that the addon itself sees /addon_config/a0d7b954_appdaemon/ as /config/, and as such the following works in my appdaemon.yaml:

logs:
  main_log:
    filename: /config/logs/main.log
  error_log:
    filename: /config/logs/errors.log
  diag_log:
    filename: /config/logs/diag.log
  access_log:
    filename: /config/logs/access.log

danVnest · 2023-11-29T06:39:16Z

Has anyone got a good approach to maintaining their Home Assistant and AppDaemon config in a single git repository like I am?
I'm currently using sudo mount --bind /addon_configs/a0d7b954_appdaemon /homeassistant/appdaemon during development which works via ssh, but is not ideal and doesn't work with Samba.

snjallingur · 2023-12-02T09:41:58Z

The suggested "Solution" does not work for me. I have reverted to v14.0, but when I try to erase the config files/folders I see that they are empty.

Any suggestions? Am I looking at the wrong place?

Truehub23 · 2023-12-03T20:38:25Z

I installed AD from scratch but I don't understand: everything remains confined in /addon_configs/a0d7b954_appdaemon/ . I can't interact with /homeassistant/config and other subfolders, I can't figure out the right path, I have a script that needs to read a value on a file under /config/downloads and I don't know how to do it.

I have HA supervised Rpi4, tnx

MarcDorval · 2023-12-03T21:24:48Z

I created a /homeassistant/appdaemon_logs/ folder then moved my appdeamon log file to /homeassistant/appdaemon_logs/appdeamon.log, and edited the axxxxx_appdeamon/appdeamon.yaml file accordingly:

logs:
  main_log:
    filename: /homeassistant/appdaemon_logs/appdeamon.log

And now AppDeamon can access the file and write to it.

I'd say there's an access restriction to axxxxx_appdeamon/logs/ from within AppDaemon...

The worst thing for non-specialists is that the error message says 'no file' while even though the file is there (under axxxxx_appdeamon/logs/) AppDaemon can't access it. When you are more familiar with Linux this rings the 'access issue' bell.

NB: I started lookind at AppDaemon yesterday for the very first time. I would not imagine I could contribute so quickly...

MarcDorval · 2023-12-03T21:31:25Z

@Truehub23 as far as I can see, /config/ is also /homeassistant/

So, you should use /homeassistant/downloads, not /homeassistant/config/downloads

MichaelBrimer · 2023-12-11T18:39:40Z

This seems to be the same problem in version 0.16.0
Do you have any idea about when this will be fixed?

Pferdebockwurst · 2023-12-11T21:50:28Z

@frenck are you working on this issue or do you consider it already resolved?

maxhuyk · 2023-12-13T21:25:41Z

Hi, I got the same problem, but I am missing the complete appdaemon folder its not inside addon_configs nor in the root directory, I am using version 0.16
any idea what to do?
Greetings

kamahat · 2023-12-19T20:41:00Z

/homeassistant/appdaemon_logs

backup your files, suppression de addon, have a coffee, reinstall the addon . go to /addon_configs/a0d7b954_appdaemon and reinstall your files

kamahat · 2023-12-19T21:06:15Z

I created a /homeassistant/appdaemon_logs/ folder then moved my appdeamon log file to /homeassistant/appdaemon_logs/appdeamon.log, and edited the axxxxx_appdeamon/appdeamon.yaml file accordingly:
logs:
  main_log:
    filename: /homeassistant/appdaemon_logs/appdeamon.log
And now AppDeamon can access the file and write to it.

I'd say there's an access restriction to axxxxx_appdeamon/logs/ from within AppDaemon...

The worst thing for non-specialists is that the error message says 'no file' while even though the file is there (under axxxxx_appdeamon/logs/) AppDaemon can't access it. When you are more familiar with Linux this rings the 'access issue' bell.

NB: I started lookind at AppDaemon yesterday for the very first time. I would not imagine I could contribute so quickly...

that solution worked fo me.
I also add to manualy create an empty files for logs specific to applications.

Pferdebockwurst · 2023-12-26T10:04:39Z

At this point I consider this as abandoned

stovedoctor · 2023-12-26T21:40:28Z

All working fine for me after following all the details steps in the fix. Maintenance is everything https://youtu.be/PvaDCBYTXhc?si=dzFC8Dni4E2pRGi_ Rod poplarchick http://www.thestovedoc.com Celebrating 34 seasons of excellence in the Hearth Products industry.

…

On Tue, Dec 26, 2023, 2:04 AM Pferdebockwurst ***@***.***> wrote: At this point I consider this as abandoned — Reply to this email directly, view it on GitHub <#287 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AONXIPOI4WNVFPT3J5WNNRLYLKOMRAVCNFSM6AAAAAA7MJDCX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGQZDMNRRGE> . You are receiving this because you commented.Message ID: ***@***.***>

sygad · 2023-12-31T18:04:48Z

I've tried to follow along but it seems to have taken a few twists and turns.

I don't have a backup where I can restore my config from so I can't follow that step.

I am running v0.16 of AppDaemon and would like to know what I can do to get my NSPanel Lovelace UI working again.

I have connected (samba) to the folder structure and have found my old config for the panel (addon_configs> a0d7b954_appdaemon > apps > apps.yaml)

Can anyone offer any guidance, I feel a bit lost by all this now, cheers

MichaelBrimer · 2024-01-01T10:40:34Z

@frenck is appdaemon not maintenaed any more?
What is the best alternativ to appdaemon?

jgalak · 2024-01-08T18:40:34Z

@frenck is appdaemon not maintenaed any more? What is the best alternativ to appdaemon?

Appdaemon is still supported, afaik. Frenck isn't the author/maintainer of Appdaemon itself, just of the add-on that encapsulates it to make easier to install. Unfortunately, this change broke some stuff, but everything needed to fix it is in this thread - I know, I just went through fixing it, as I missed the update in Nov and had been wondering why my scripts stopped working...

Best alternative? For me, there isn't one. I vastly prefer this way of doing automations over either the native HA or CodeRed. But those are the alternatives.

Now, all that being said, I think this is a bad change. Backup/restore were working fine before, just not as encapsulated as frenck appears to like. So from my point of view, there's nothing positive gained. And two significant negatives - breaking the ability to get appdaemon scripts through HACS, and the fact that it messes with my git setup. I suspect if most appdaemon users were asked about this, they'd prefer the change not occur...

frenck · 2024-01-08T18:48:35Z

@frenck is appdaemon not maintenaed any more? What is the best alternativ to appdaemon?

That is a question for the AppDaemon project, not this add-on.

frenck · 2024-01-08T18:52:44Z

@jgalak Sorry to hear you don't agree. I am pretty sure, as with any change, some like, others don't.

When creating a backup, one should expect it to have all of it in it, and this wasn't the case. Not agreeing on that, sounds odd... but if you think that is normal for a backup... that is fine by me 🤷

Feel free to do better by building and maintaining your own add-on 👍

../Frenck

frenck · 2024-01-08T18:55:06Z

As this issue has been resolved quite some time ago (hours after the release). I've left it open for people to find and see.

Is has been 2 months at this point, so time to close it.

../Frenck

Pferdebockwurst · 2024-01-08T23:18:12Z

@frenck Take some time and re-think about your interactions with users regarding this issue. To me, your attitude sheds a very bad light on your otherwise good work in this project. Programming is not the only necessary skill for being a good maintainer.

stovedoctor · 2024-01-09T00:50:11Z

It's messed up mine but I saw it Early and had a backup of my data base.
With @frenck steps on how to fix I was back up and running in just a few minutes.
Why it is important to have full backups and individual backups local and off HA I keep my backups 50 deep because I don't normally catch issues right away this time of year when I'm busy with service work.

Keep up the awesome work @frenck
We love what you and the team do.
Chuchu

frenck · 2024-01-09T06:06:56Z

@frenck Take some time and re-think about your interactions with users regarding this issue. To me, your attitude sheds a very bad light on your otherwise good work in this project. Programming is not the only necessary skill for being a good maintainer.

Sorry to hear you don't agree. I did the best I can to resolve the issue as quickly as possible and to provide the necessary instruction to resolve it.

If this wasn't sufficient for your taste, then I am sorry. Maybe this add-on is not for you. You are free to use something else.

Thanks 👍

../Frenck

frenck · 2024-01-09T06:07:47Z

Lock down the issue now as well.

This is no longer discussing the actual issue.

This comment was marked as duplicate.

Sign in to view

frenck added priority-high After critical issues are fixed, these should be dealt with before any further issues. in-progress Issue is currently being resolved by a developer. labels Nov 15, 2023

frenck self-assigned this Nov 15, 2023

frenck mentioned this issue Nov 15, 2023

Fix incorrect check if AppDaemon configuration already exists #289

Merged

frenck removed the in-progress Issue is currently being resolved by a developer. label Nov 15, 2023

frenck mentioned this issue Nov 15, 2023

Fixed another incorrect check #290

Merged

This was referenced Nov 28, 2023

Problem after starting #309

Closed

NSPanel: Configuration gone after Update. #305

Closed

my appdaemon won't keep running I start it then chack back later and its not running #304

Closed

noofny mentioned this issue Dec 21, 2023

AppDaemon addon now crashes when starting since update to 0.16.0 #318

Closed

frenck closed this as completed Jan 8, 2024

hassio-addons locked and limited conversation to collaborators Jan 9, 2024

AppDaemon stops after updating to 0.15.0 #287

AppDaemon stops after updating to 0.15.0 #287

Comments

PeterAndreS commented Nov 15, 2023 • edited by frenck Loading

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

Log:

frenck commented Nov 15, 2023

dersch81 commented Nov 15, 2023 • edited by frenck Loading

PeterAndreS commented Nov 15, 2023

Expected behavior folder name?

frenck commented Nov 15, 2023

dersch81 commented Nov 15, 2023

Jabe commented Nov 15, 2023

kefrens commented Nov 15, 2023

frenck commented Nov 15, 2023

dersch81 commented Nov 15, 2023 • edited Loading

mupsje commented Nov 15, 2023

This comment was marked as duplicate.

PeterAndreS commented Nov 15, 2023 • edited by frenck Loading

frenck commented Nov 15, 2023

frenck commented Nov 15, 2023

pmansvelder commented Nov 15, 2023 • edited Loading

dersch81 commented Nov 15, 2023

frenck commented Nov 15, 2023 • edited Loading

frenck commented Nov 15, 2023

pmansvelder commented Nov 15, 2023

frenck commented Nov 15, 2023 • edited Loading

frenck commented Nov 15, 2023

dersch81 commented Nov 15, 2023

frenck commented Nov 15, 2023 • edited Loading

PeterAndreS commented Nov 15, 2023 • edited Loading

vaibhav2912 commented Nov 29, 2023 • edited Loading

ℹ️ The solution

danVnest commented Nov 29, 2023 • edited Loading

danVnest commented Nov 29, 2023

snjallingur commented Dec 2, 2023

Truehub23 commented Dec 3, 2023 • edited Loading

MarcDorval commented Dec 3, 2023 • edited Loading

MarcDorval commented Dec 3, 2023 • edited Loading

MichaelBrimer commented Dec 11, 2023 • edited Loading

Pferdebockwurst commented Dec 11, 2023

maxhuyk commented Dec 13, 2023

kamahat commented Dec 19, 2023

kamahat commented Dec 19, 2023

Pferdebockwurst commented Dec 26, 2023

stovedoctor commented Dec 26, 2023 via email

sygad commented Dec 31, 2023

MichaelBrimer commented Jan 1, 2024

jgalak commented Jan 8, 2024

frenck commented Jan 8, 2024

frenck commented Jan 8, 2024

frenck commented Jan 8, 2024

Pferdebockwurst commented Jan 8, 2024 • edited Loading

stovedoctor commented Jan 9, 2024

frenck commented Jan 9, 2024

frenck commented Jan 9, 2024

PeterAndreS commented Nov 15, 2023 •

edited by frenck

Loading

dersch81 commented Nov 15, 2023 •

edited by frenck

Loading

dersch81 commented Nov 15, 2023 •

edited

Loading

PeterAndreS commented Nov 15, 2023 •

edited by frenck

Loading

pmansvelder commented Nov 15, 2023 •

edited

Loading

frenck commented Nov 15, 2023 •

edited

Loading

frenck commented Nov 15, 2023 •

edited

Loading

frenck commented Nov 15, 2023 •

edited

Loading

PeterAndreS commented Nov 15, 2023 •

edited

Loading

vaibhav2912 commented Nov 29, 2023 •

edited

Loading

danVnest commented Nov 29, 2023 •

edited

Loading

Truehub23 commented Dec 3, 2023 •

edited

Loading

MarcDorval commented Dec 3, 2023 •

edited

Loading

MarcDorval commented Dec 3, 2023 •

edited

Loading

MichaelBrimer commented Dec 11, 2023 •

edited

Loading

Pferdebockwurst commented Jan 8, 2024 •

edited

Loading