WARNING AppDaemon: HASS: Error in authentication

Hi, I’ve been trying to make appdaemon work for a while, but for me it’s impossible, I need your wisdom, this is the error that gives me:

pi@raspberry:~ $ appdaemon -c /home/homeassistant/.homeassistant/conf
2019-12-01 19:30:41.565402 INFO AppDaemon Version 3.0.5 starting
2019-12-01 19:30:41.565670 INFO Configuration read from: /home/homeassistant/.homeassistant/conf/appdaemon.yaml
2019-12-01 19:30:41.566655 WARNING config_file: /home/homeassistant/.homeassistant/conf/appdaemon.yaml is owned by root but appdaemon is running as pi
2019-12-01 19:30:41.567738 INFO AppDaemon: Starting Apps
2019-12-01 19:30:41.568126 WARNING config_dir: /home exists, but is not writeable, owner: root
2019-12-01 19:30:41.568335 WARNING config_dir: /home/homeassistant/.homeassistant/conf exists, but is not writeable, owner: root
2019-12-01 19:30:41.568838 WARNING appdir: /home/homeassistant/.homeassistant/conf/apps is owned by root but appdaemon is running as pi
2019-12-01 19:30:41.573603 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2019-12-01 19:30:42.097693 INFO AppDaemon: HASS: HASS Plugin Initializing
2019-12-01 19:30:42.098342 INFO AppDaemon: HASS: HASS Plugin initialization complete
2019-12-01 19:30:42.098695 INFO Dashboards are disabled
2019-12-01 19:30:42.098829 INFO API is disabled
2019-12-01 19:30:42.105430 INFO AppDaemon: HASS: Connected to Home Assistant 0.102.1
2019-12-01 19:30:42.118178 WARNING AppDaemon: HASS: Error in authentication
2019-12-01 19:30:42.118571 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2019-12-01 19:30:47.126675 INFO AppDaemon: HASS: Connected to Home Assistant 0.102.1

and this is my appdaemon.yaml file:
‘’ ’
log:
logfile: STDOUT
errorfile: STDERR
appdaemon:
threads: 10
plugins:
HASS:
type: hass
ha_url: http://192.168.0.22:8123
token: eyJpc3MiOiJjNzVkNDI3ZWVhNTI0MGFkYTQzM2Q1NDFiOTM1OTUyOSIsImlhdCI6MTU3NTIyNDcxOSwiZXhwIjoxODkwNTg0NzE5fQ
‘’’
what am I doing wrong??
thanks!

I am having the same issue. Anyone?

1 Like