I am currently trying to configure AppDaemon to work with my Home Assistant (installed on a Raspberry Pi 3 B+). It appears it is not uncommon for people who have a configuration set up with Duck DNS to struggle with this, but I cannot figure out what to do. Below is what I have in my appdaemon.yaml file.
Are you running Home Assistamt Supervised or Home Assistant OS (add-ons, snapshots etc.)? If so, you should use the appdaemon addon and you don’t need to configure URL, token, etc. As the addon handles it.
@Burningstone I am running Home Assistant OS. That is what I thought too, but the default configuration would not open the Web UI. I would receive an error telling me it could not find the site in another tab (and still receiving the same error).
I guess I will uninstall/reinstall appdaemon to see if that helps.
you’ll need NGINX addon so you can access Appdaemon locally and still keep DuckDNS working for external. Otherwise you’ll need to use the DuckDNS URL everywhere.
It’s a DNS service. As soon as you enable external communication, all communication needs to go through that, including internal. It’s the drawback to exposing your pi with a dns service. Luckily you can use a proxy to route internal info so you can use both your internal IP and External connection.