Appdaemon keeps changing the ha_url in appdaemon.yaml. Why?

Third party integrations AppDaemon
1

I recently changed the domain name that HA runs on, and in that respect everything works fine.

However I am unable to get appdaemon to connect using the new domain name.
When I write the new domain name in ha_url, appdaemon overwrites it with the old domain name when it starts up. And in doing so it cannot connect to HA!

Here is the excerpt from appdaemon.yaml.

appdaemon:
  latitude: 50
  longitude: -1
  elevation: 107
  time_zone: Europe/London
  log_thread_actions: 0
  plugins:
    HASS:
      type: hass
      ha_url: https://domain.duckdns.org
      token: 1234
      app_init_delay: 10
      cert_verify: false

Appdaemon ovewrites whatever I put in the new ha_url, e.g. https://newdomain.org or https://192.168.1.1:8123.

Does anyone know why this happening please or what extra steps I need to take to get AD to use the new domain name?

Btw I am using docker versions or HA, AD and nginx proxy manager if that helps.

Thanks

2

Try deleteing the docker container and make a new one. Specify the new ha_url in the docker run command you use to create the container.

3

That’s exactly what it was, thanks Tomas. I headed over to Portainer to check the environment variables and could see the har_url entry that was obviously overwriting the yaml config file in AD.

1 Like