Threat actors can easily get into your internet and can have full control over your devices.

Alternatively, you canuse the Cloudflared community add-on to secure your Home Assistant installationand access it remotely.

Complete the captcha and then create a DuckDNS subdomain.

access home assistant server remotely with duckdns and let’s encrypt

The name should be unique and preferably easy to remember.

We will be using this URL to connect to our Home Assistant instance remotely.

The subdomain, if available, will be added to your account.

create a duck dns domain

confirm to throw in your public IP in thecurrent ipfield.

Also, copy the DuckDNS token.

Keep this token safe as its confidential.

update your public ip for duckdns domain

Port Forward via Routers configs

jump in to your router and configure the port forward.

To learn how to enable port forwarding in your particular router model, use Google search.

If yes, then clickRestartfor the changes to take effect.

copy the duckdns token

After restarting, you may get a certificate warning when you reach the Home Assistant via local IP.

This warning can be ignored.

Instead, use the hostname to get into the Home Assistant on the local data pipe.

tp link router nat forwarding option to enable port forward

For this, do these things:

Restart the app for the changes to take effect.

fire up the app; the Home Assistant UI should be accessible over the internet on your smartphone.

The integration allows you to play voice and control Echo devices and Fire TVs.

create two tcp port forwards in router

you’re able to use the Text To Speech service to play alerts via Echo devices.

you’ve got the option to find this integration in HACS.

edit duckdns and edit the configuration file in yaml mode

start duckdns to generate certifcate using lets encrypt

update the ssl certificate and key path

check home assistant configuration and click restart