After you make changes to appdaemon.yaml you have to restart AD for the app log to be available. Beyond that, you’ll need to provide additional information such as error logs.
No the issue is that it’s Docker, and you are trying to write a file that the AppDaemon Docker container does not have access to. When you tell it to write to /volume1/docker/appdaemon/a.log you are telling the Docker container to write to that file INSIDE the container, a path that won’t exist unless it has been specifically mounted in the Docker run command or compose file. The whole point of Docker is that it DOES NOT have access to the entire file system of the HOST.
@mobile.andrew.jones thank you for your time and comphrensive reply. I understand the concept a little better. I did the following, with no success:
appdaemon.yaml
Try running AppDaemon in interactive mode (ie don’t use -d) and see what errors show up, we are looking to see if there is a Error 13 file permission error creating the log file in the first place.
2022-01-06 10:21:25.275519 INFO AppDaemon: Initializing app pump_overrun using class Pump from module pump_overrun
2022-01-06 10:21:25.277578 ERROR pump_overrun: User defined log myapp not found
2022-01-06 10:21:25.282420 INFO pump_overrun: <class 'method'>
2022-01-06 10:21:25.286367 INFO MQTT: Topic pump_run_time_last_5m already subscribed to
2022-01-06 10:21:25.295044 INFO pump_overrun: Pump Overrun automation started
2022-01-06 10:21:26.316814 INFO AppDaemon: Terminating pump_overrun
2022-01-06 10:21:26.320484 INFO AppDaemon: Reloading Module: /conf/apps/pump_overrun.py
2022-01-06 10:21:26.326217 INFO AppDaemon: Initializing app pump_overrun using class Pump from module pump_overrun
2022-01-06 10:21:26.329201 ERROR pump_overrun: User defined log myapp not found
2022-01-06 10:21:26.334321 INFO pump_overrun: <class 'method'>
2022-01-06 10:21:26.338227 INFO MQTT: Topic pump_run_time_last_5m already subscribed to
2022-01-06 10:21:26.347053 INFO pump_overrun: Pump Overrun automation started