Trying to revive appdaemon after a long period of not updating HA

I hadn’t updated HA in many months, so I decided to bite the bullet and try a docker based installation with the latest. I got HA up and running (more or less), but now I’m trying to get appdaemon going and I’m a little lost out of the gate.

In the docs, it says “TOKEN: If your Home Assistant is using Long Lived Tokens you will need to use TOKEN”. So, umm, how would I know if HA is “using long lived tokens”? I tried some basic googling but could not find a straightforward answer.

So if I ignore that, and try to start using the recommended command line without the token bit:

docker run --rm -it -p 5050:5050
-e HA_URL=“myHA_URL”
-e DASH_URL=“http://:5050$HOSTNAME
acockburn/appdaemon:latest

I get:

2018-11-22 06:00:13.266104 INFO AppDaemon: HASS: Connected to Home Assistant 0.82.0
2018-11-22 06:00:13.266517 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-11-22 06:00:18.273400 INFO AppDaemon: HASS: Connected to Home Assistant 0.82.0
2018-11-22 06:00:18.273794 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds

I googled this as well, and got advice to “use -D DEBUG” for more information. Ok, but… as arguments to what? Adding it to various places in the docker command line produced errors.

Something I’m unclear about is… how is appdaemon finding my config files? I did not seem to supply them to the appdaemon instance, like I did for HA.

if you installed the latest version from HA and you now have username pasword combination, you also got long lived tokens. you set them by clicking in HA frontend on the user icon on the top left
without setting the token in HA you wont get appdaemon working.

i hope you follow this doc:
https://appdaemon.readthedocs.io/en/latest/DOCKER_TUTORIAL.html
and afterwards you need to follow this for setting up your configuration:
https://appdaemon.readthedocs.io/en/latest/CONFIGURE.html

Thanks, that worked. PR submitted for the docs.