HA AIO, AppDaemon, duckdns, and letsencrypt

Configuration
1

I’ve been trying to setup up AppDeamon and have been running into configuration issues. No matter what AppDeamon configuration I use, I get some type of connect failed/refused/max attempts error.

Has anyone here set this combination up before? I’d like to know a few things:

Are you using your duckdns ha_url or your internal ip?
If you are using your duckdns url, are you providing it with the port or without the port? Which port, 8123 or 443?
Are you using a cert? If so, what cert_path are you pointing to?

Anyone who can shed some light on this would be great.

2

I have AppDaemon running with HA secured using letsencrypt and duckdns. It is configured to use duckdns url without port like https://xxxxxx.duckdns.org and password, don’t have any cert path set in AppDaemon and works great.

[AppDaemon]
ha_url = https://******.duckdns.org
ha_key = *******
logfile = STDOUT
errorfile = STDERR
app_dir = conf/apps
threads = 20
latitude = xx.xxxx
longitude = xx.xxxx
elevation = xxxx
3

It just doesn’t work for me. My current settings:

[AppDaemon]
ha_url = https://******.duckdns.org
ha_key = ******
logfile = STDOUT
errorfile = STDERR
app_dir = 
threads = 10
timeout = 60
# Apps
[hello_world]
module = hello
class = HelloWorld

This is the error I am always getting with this setup:

2017-02-25 16:14:00.458085 WARNING Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/appdaemon/appdaemon.py", line 1361, in run
    ws = create_connection("{}/api/websocket".format(url))
  File "/usr/local/lib/python3.4/dist-packages/websocket/_core.py", line 487, in create_connection
    websock.connect(url, **options)
  File "/usr/local/lib/python3.4/dist-packages/websocket/_core.py", line 211, in connect
    options.pop('socket', None))
  File "/usr/local/lib/python3.4/dist-packages/websocket/_http.py", line 71, in connect
    sock = _open_socket(addrinfo_list, options.sockopt, options.timeout)
  File "/usr/local/lib/python3.4/dist-packages/websocket/_http.py", line 114, in _open_socket
    sock.connect(address)
OSError: [Errno 113] No route to host

Whats really annoying is that all other packages have no issue connecting to my HA, just appdaemon.

4

You aren’t using a self signed cert so you don;t need to specify a cert_dir.

The error above looks like a port forwarding issue on your router - the router has to not only have port forwarding setup to map from the outside in, but it also needs to know to route packets from the inside out and back in again as you are forcing it to get to HA via your external IP address. This is an unfortunate consequence of SSL - you can’t use the internal IP address.

So, you need to have a look at your router config to fix this it would seem.

5

I understand what you are saying but I do not know how to execute that. What phrases should I google to find out how to create this route?

6

What type of router do you have?

7

Its a linksys smart WIFI, one of those cloud based ones. It’s got a nice UI but that’s about it. I am limited with its functionality. I was toying with the idea of putting ddwrt on it but, ddwrt appears to not support my model number. I can port forward single ports and forward ranges. I see a section for static routing but I have never done that. I assume that’s what I would do… just don’t want to change settings before making sure that is the solution.