Nabu Casa Remote UI vs. DuckDNS and port forwarding

I currently access my Home Assistant instance remotely by using DuckDNS and forwarding the port 8123 in my router. This has always worked perfectly fine.

I’m wondering what the new Remote UI feature is all about, since accessing HA remotely has always been easy and it doesn’t seem like there is a real need for it. Is it only meant for instances where port forwarding doesn’t work for whatever reason? Or is there any other benefit of the Remote UI that I’m not seeing?

Not having to open a port is the major bonus.

Yeah, I guess from a security standpoint that could be a bonus. On the other hand, if the proxy server is compromised that would be an even bigger security issue for everyone. And attacks on that proxy server are much more likely than on my local instance.

Does anyone know where the proxy is hosted? And does it impact the responsiveness, i.e. add a delay? I’m in Australia and if the proxies are hosted in the US, I think that may be noticeable (we get 300-500ms pings to the US).

1 Like

I live in NZ, performance is certainly acceptable.

There is a months free trial.

integrating other cloud components is easier, especially Google Home and Amazon Alexa

1 Like

Now, if one was to use Nabu Case only (and it’s great already for the Alexa interface), what changes are there to make? Can I remove the port forward in my router, DuckDNS?

Sorry to reply to a 27 day old thread. I was looking for this information too. I just enabled Remote UI in Nabu Casa. I’d like to uninstall the Duck DNS add-on from Hass.io, but I wasn’t sure if it was as easy as clicking the UNINSTALL link from the add-on page? Then removing the router port forwarding entries.
Thanks if anyone can help!

1 Like

I am trying to do the same… hopefully someone can offer some guidance!

You can uninstall duckdns (although if you are using duckdns to provide dns for other stuff, leave it alone).

And yes remove the port forwards.