WARNING config_dir: /home exists, but is not writeable, owner: root

Blockquote
2018-11-01 12:38:39.590147 WARNING config_dir: /home exists, but is not writeable, owner: root
2018-11-01 12:38:39.596432 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-11-01 12:38:39.718782 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-11-01 12:38:39.719161 WARNING AppDaemon: HASS: ha_key is deprecated please use HASS Long Lived Tokens instead
2018-11-01 12:38:39.719566 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-11-01 12:38:39.719966 INFO Starting Dashboards
2018-11-01 12:38:39.721836 WARNING css: /home exists, but is not writeable, owner: root
2018-11-01 12:38:39.723722 WARNING javascript: /home exists, but is not writeable, owner: root
2018-11-01 12:38:39.730949 INFO API is disabled
Blockquote

I’ve installed Appdaemon vi pip3 on an ubuntu server.
HomeAssistant is running fine, as well the apps from Appdaemon.

The problem I have that I can’t make any dashboard.
I’ve tried running Appdaemon as root, but that didn’t solve the problem.
The compiled directory’s worn’t created during installation, so I made them myself with the correct owner.

It’s got something to do with the three Warnings, I think.

Any idea how to solve this?

running AD as root is a bad idea.
just make sure that the user you use to start AD has full control over the config dir and all its files and subdirs. (read, write, execute)

edit: sorry i did look wrong.

please share your appdaemon.yaml and your complete log

and what do you mean exactly with you cant make any dashboard?
making a dashboard is creating a yaml file with the extention dash on the right place.

I do have a yaml dashboard file.
I have the same yaml file on a raspberry pi and there it is running fine.

please share more info.
complete log
appdaemon.yaml
dir structure and location from the dashboard file
how you tried to access the dashboard

here is my appdaemon.yaml

log:
logfile: /home/appdaemon/.appdaemon/appdaemon.log
errorfile: /home/appdaemon/.appdaemon/apperror.log
appdaemon:
threads: 10
app_dir: /home/appdaemon/.appdaemon/apps
plugins:
HASS:
type: hass
ha_url: http://192.168..:8123
ha_key: ********
hadashboard:
dash_url: http://192.168.
.:5050
dash_dir: /home/appdaemon/.appdaemon/dashboards

please share yaml as codeblock.
i cant read it like this.

Blockquote

log:
logfile: /home/appdaemon/.appdaemon/appdaemon.log
errorfile: /home/appdaemon/.appdaemon/apperror.log
appdaemon:
threads: 10
app_dir: /home/appdaemon/.appdaemon/apps
plugins:
HASS:
type: hass
ha_url: http://192.168..:8123
ha_key: *******
hadashboard:
dash_url: http://192.168.
.:5050
dash_dir: /home/appdaemon/.appdaemon/dashboards

Blockquote

that didnt make it any better :wink:

log:
logfile: /home/appdaemon/.appdaemon/appdaemon.log
errorfile: /home/appdaemon/.appdaemon/apperror.log
appdaemon:
threads: 10
app_dir: /home/appdaemon/.appdaemon/apps
plugins:
HASS:
type: hass
ha_url: http://192.168..:8123
ha_key: *******
hadashboard:
dash_url: http://192.168.
.:5050
dash_dir: /home/appdaemon/.appdaemon/dashboards

still not the right way. thats a quote
it doesnt show the spaces and please remove or hange your password.

log:
  logfile: /home/appdaemon/.appdaemon/appdaemon.log
  errorfile: /home/appdaemon/.appdaemon/apperror.log
appdaemon:
  threads: 10
  app_dir: /home/appdaemon/.appdaemon/apps
  plugins:
    HASS:
      type: hass
      ha_url: http://192.168.***.**:8123
      ha_key: *********
hadashboard:
  dash_url: http://192.168.***.**:5050
  dash_dir: /home/appdaemon/.appdaemon/dashboards

I saw this error too. Something broke on last release and dashboards that used to work right aren’t anymore. If you have a custom widget the problem is worst. I’m still investigating…

thats no error. its a warning and if it is about /home you dont need to worry about it.

if you did update from 3.0.1 to 3.0.2 you need to clear the compiled dir
nothing really changed in the dashboard, but you need to clear cashe files.

by the way, i got a ton of custom widgets and no problem with the update.

clear the compiled dir solved some strange things… thanks. I think it’s not done automatically when upgrading the container, right?

no it isnt, because the compiled dir is (or at least should be) outside the container, because its in the config dir.
you dont want anything to change in your config when you upgrade your container :wink: