I’m having a issue with file permission error using the latest AppDaemon. HA is installed in a virtual environment as user home assistant and I received an version error with aiohttp when I attempted to install Appdaemon in the same VE. After searching I found a suggestion to installed AppDaemon in a separate VE which I thought would be a good idea. After the install I put the AppDaemon config and apps files under /home/homeassistant/conf as I had done before. However when I started AppDaemon I received the following traceback regarding the permission problem with creating the appDaemon log.
File “/usr/lib/python3.6/logging/init.py”, line 1031, in init
StreamHandler.init(self, self._open())
File “/usr/lib/python3.6/logging/init.py”, line 1060, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: ‘/home/homeassistant/conf/appdaemon.log’
The /home/homeassistant/conf directory permission are set correctly. I am not sure what is wrong since I was homeassistant user and had the AppDaemon VE activated. Should I locate AppDaemon config and apps in a different location?
Any thoughts what I could be doing wrong.
Ubuntu 18.04 running on an Intel NUC
Thanks
Mark
using HA and AD in seperate venvs is absolutely better. (i had them running in the same long time untill there was trouble)
i also advice 2 different dirs side by side for 2 different config areas, but it isnt neccesary.
it seems to me that the user that starts appdaemon doesnt have writing access in the dir
‘/home/homeassistant/conf/’
the user that starts appdaemon need full control over that dir and all its subdirs
after starting appdaemon you can normally see if the rights are set right in the needed areas, but in this case it cant write there.
are you sure the dir is home/homeassistant and not home/.homeassistant?
Well I knew it had to be something stupid on my part. It was the conf file owner problem. I must have created it using sudo with me as a user instead of homeassistant
Glad to know that it was correct to put AppDaemon in its own VE.
Thanks for the quick response.
Mark
1 Like
i did a long time to get there, because it looks complicated (and keeping everything apart still can be) but after i started to use seperate venvs i really liked it.
now i got 6 venvs, with 4x AD and 2x HA and its easy as pie to add another one.
the most important part is to have a good config erea.
thats why i dont put AD config inside HA config
AD and HA are 2 different programs, so config should be on different places. you also dont put config from NGinx or any other program in the HA config area.
Ah good point about separate configs. I normally don’t update at every HA release. There has to be a good reason for me to update such as bug fixes, security updates and so on. And when I do upgrade creating a new virtual environment makes it easy to do testing on the new code release without affecting my working, “golden” release.
same here.
i got from 0.40 to 0.69 to 0.79 
i only updated because i needed for AD.