hassio-addons / addon-appdaemon3

AppDaemon3 - Home Assistant Community Add-ons
https://addons.community
MIT License
41 stars 12 forks source link

After upgrade from AD3 1.5 to 1.6, it doesn't work any more #30

Closed rpcaeiro closed 5 years ago

rpcaeiro commented 6 years ago

Problem

The AD service is running, but the Dashboard is not running anymore No errors In the appdeamon.yaml I have added the long-lived token generated by the HA

plugins: HASS: type: hass ha_url: http://hassio/homeassistant app_dir: /config/appdaemon/apps Token: eyJ0eXAiOiJKV1QiLCJhbGciOiJ........

No other error is shown in any of the other log files. I already checked everything, I don't know what else more I can do.

Thanks Rui

addons-assistant[bot] commented 6 years ago

:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

tjorim commented 6 years ago

Change the ha_url and don't use a long-lived access token, the add-on takes care of that. https://github.com/hassio-addons/addon-appdaemon3/issues/27#issuecomment-435335330 After that restart the add-on and the token should get corrected.

rpcaeiro commented 6 years ago

Hi tjorim,

Now the config is: plugins: HASS: type: hass ha_url: http://hassio/homeassistant app_dir: /config/appdaemon/apps dash_url: http://192.168.1.152:5050

I think apps are working but the dash is not. I'm only interested in the dash. No errors are shown. Thanks Rui

rpcaeiro commented 5 years ago

Solved! The problem was in the version 1.5, that was incorrectly configured and the upgrade went wrong. To solve this, first I had to downgrade it to version 1.5, correct the appdaemon.yaml file and then upgrade again. Before upgrading, make sure the entry ha_key is there. This key is created automatically by the AD. This key is then replaced by a token that will be used from 1.6 on.

addons-assistant[bot] commented 5 years ago

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.