@quadportnick
I’ll try without --net=host.
10.10.10.200 is the same ip of the synology… hass is running on synology on listening on 8123 with https
@aimc if the HASS url is HTTPS but the certificate is self-signed, would AppDaemon/python refuse the connection without having that imported in that instance?
Thanks! Since everything else worked I didn’t even think about that… 
Thats what the cert_path directive is for - if its self signed AppDaemon needs to see the cert.
This looks like a corruption in your compiled python - you will probably need to clear out the pyc files - this has been discussed before on here, so a forum search should help.
@aimc ahhh got it. Which. Now I get why it’s not working. I was too focused on the network behavior 
@ciquattro in your appdaemon config, you need to use the paths relative to the Docker inside, not outside. So your internal mounts not the Synology paths (/conf, /certs)
@aimc @quadportnick
certs path is:
/volume1/docker/homeassistant/config/certs:/certs
so the appdaemon config is:
[AppDaemon]
ha_url = https://10.10.10.200:8123
ha_key = xxxxxxxx
logfile = STDOUT
errorfile = STDERR
app_dir = /volume1/docker/appdaemon/conf/apps
threads = 10
cert_path = /volume1/docker/homeassistant/config/certs
latitude =
longitude =
elevation =
time_zone =
# Apps
[hello_world]
module = hello
class = HelloWorld
Now I have to run the docker command and put this -v /volume1/docker/homeassistant/config/certs right?
so the new command will be:
docker run -v /volume1/docker/homeassistant/config/conf:/conf -v /volume1/docker/homeassistant/config/certs:/certs --restart always --name appdaemon mezz64/appdaemon
I’m not sure that this vaule is correct
-v /volume1/docker/homeassistant/config/certs:/certs I have to add the :/certs? The docker container will check for /certs path?
Your appdaemon app_dir and cert_path paths should start with just /conf and /certs. appdaemon is running inside the container and your -v commands are saying outside:inside, so you want to use what you specified as the inside path on the inside.
The appdaemon container has zero knowledge of or access to the host’s file system outside of what you map, so /volume1 etc is meaningless from its perspective.
like this?
[AppDaemon]
ha_url = https://10.10.10.200:8123
ha_key = xxxxxxx
logfile = STDOUT
errorfile = STDERR
app_dir = /conf/apps
dash_url = https://10.10.10.200:5050
threads = 10
cert_path = /certs
latitude =
longitude =
elevation =
time_zone =
# Apps
[hello_world]
module = hello
class = HelloWorld
That looks much better yes. Also mask your key!
nothing
same results:
root@DSM01:~# docker run -v /volume1/docker/homeassistant/config/conf:/conf -v /volume1/docker/homeassistant/config/certs:/certs --restart always --name appdaemon mezz64/appdaemon
2017-03-31 13:52:38.010938 INFO AppDaemon Version 1.5.2 starting
2017-03-31 13:52:38.048048 WARNING Unable to connect to Home Assistant, retrying in 5 seconds@quadportnick - is there any way to pass parameters through to be appended to the CMD ? If we can run this with -D DEBUG we will get more info. Otherwise @Ciquattro could edit his docker file I suppose but there must be a more elegant way to do this?
at the moment I’m with these configs:
[AppDaemon]
ha_url = https://10.10.10.200:8123
ha_key = xxxxxxxxxx
logfile = STDOUT
errorfile = STDERR
app_dir = /conf/apps
dash_url = https://10.10.10.200:5050
threads = 10
cert_path = /certs
latitude =
longitude =
elevation =
time_zone =
# Apps
[hello_world]
module = hello
class = HelloWorld
Docker command:
docker run -v /volume1/docker/homeassistant/config/conf:/conf -v /volume1/docker/homeassistant/config/certs:/certs -p 5050:5050 --name appdaemon mezz64/appdaemonYes there is a syntax for this when running a new container to avoid having to build a new image. On a container itself you basically delete it and recreate. Docker doesn’t care much about containers. The philosophy is about keeping them disposable
I believe it’s like
docker run --entrypoint==XXX
I’m on mobile and juggling views is annoying.
OK, I’ll look into that - being able to run a debug version will be very useful in the future.
@Ciquattro - can you try the following:
take a backup of Dockerfile, then edit it to look like this:
FROM python:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
VOLUME /conf
# Copy source
COPY . .
# INSTALL
RUN pip3 install .
CMD [ "appdaemon", "-c", "/conf", "-D", "DEBUG" ]
Then rebuild the image and try running it. You should get s lot more logging and hopefully an error trace for the connection.
How I can do it? because I’m using this docker repository
I don’t currently maintain docker images anywhere although I am looking into it.
According to the version, 1.5.2, this is the latest AppDaemon v1, but in order to run the dashboard you should be running v2beta. To get that to run in Docker you need to follow the steps I gave in the original beta announcement, which is linked at the top of this thread.
I found that config (yaml) doesn’t support scandinavian characters like “æøå”. Dashboards refuses to load.
1 Like
Does it work if you put them in quotes?
Yeah that fixed it. Thanks!
Great work btw and thanks to all for helping. For me it covers everything I had and even more than v1.
2 Likes