How to Access Your Home Assistant Dashboard Remotely

What are the different ways to access HA remotely?

Home Assistant runs on your local network by default — accessible at something like http://homeassistant.local:8123 when you're home. To access it from work, a café, or your phone on mobile data, you need one of several remote access methods:

• Home Assistant Cloud (Nabu Casa): Paid service ($6.50/month) that creates a secure HTTPS tunnel. The easiest option.
• Tailscale VPN: Free for personal use. Creates a private encrypted network between your devices. Zero port forwarding needed.
• Cloudflare Tunnel: Free. Routes traffic through Cloudflare's edge network. Requires a domain name and some configuration.
• Port forwarding: Expose HA directly to the internet through your router. Free but not recommended for security reasons.
• Dynamic DNS + reverse proxy: Advanced setup using your own domain, NGINX or Caddy, and Let's Encrypt SSL. Free but complex.

How does Home Assistant Cloud (Nabu Casa) work?

Home Assistant Cloud, operated by Nabu Casa (the company behind Home Assistant), creates an encrypted tunnel between your HA instance and Nabu Casa's servers. When you access your HA URL remotely, traffic is routed through this tunnel — you never need to open any ports on your router or configure any DNS.

Setup takes literally 3 minutes:

1. Go to Settings → Home Assistant Cloud in HA
2. Create a Nabu Casa account ($6.50/month, cancel anytime)
3. Sign in — HA immediately shows you a remote access URL like https://abcdef.ui.nabu.casa
4. Bookmark this URL or set it in the HA companion app as your external URL

Nabu Casa also enables Alexa and Google Assistant integration with one click, and funds the ongoing development of Home Assistant. Many users consider it worth paying even if they could set up a free alternative, because it directly supports the open-source project.

The tunnel is TLS-encrypted end-to-end, authenticated with your account credentials, and Nabu Casa does not have access to your data or devices. Latency depends on tunnel routing but is typically 50–150ms for basic controls — imperceptible for switching lights or checking sensors.

How do you set up Tailscale for free remote access?

Tailscale is the best free option for remote access. It uses WireGuard under the hood to create a private mesh VPN between your devices. When you access HA remotely via Tailscale, you connect to your HA instance's Tailscale IP address as if you were on your home network — no tunnelling through third-party servers, just a direct encrypted connection.

Setup (about 10 minutes):

1. Create a free Tailscale account at tailscale.com (free for up to 3 users and 100 devices)
2. In Home Assistant, go to Settings → Add-ons → Add-on Store and install the Tailscale add-on
3. Start the add-on and open the web UI — it shows a login URL. Visit it and authorise the HA machine in your Tailscale network.
4. Install the Tailscale app on your phone/laptop and sign in with the same account
5. Your HA instance now has a Tailscale IP (e.g., 100.64.x.x). Access it at http://100.64.x.x:8123 from any device running Tailscale

Enable Tailscale's "subnet router" feature in the add-on settings to access all your home network devices (not just HA) through the VPN. Enable the "Exit node" feature if you want to route all internet traffic through your home when away (useful for privacy on public Wi-Fi).

Can you use Cloudflare Tunnel for remote access?

Yes. Cloudflare Tunnel (formerly Argo Tunnel) is free and routes your HA traffic through Cloudflare's global CDN edge, giving you a public HTTPS URL without opening any ports. You need a domain name registered with Cloudflare ($8–$15/year for a .com), but the tunnel itself is free.

Setup is more involved: You need to install the cloudflared daemon (available as a HA add-on via HACS), configure a tunnel in the Cloudflare Zero Trust dashboard, and set up a DNS record pointing to the tunnel. Takes 30–45 minutes the first time.

Cloudflare Tunnel is popular with advanced users who want their own domain name (e.g., https://home.yourdomain.com) with Cloudflare's DDoS protection and Access policies (you can add a login page in front of HA for extra security).

Should you use port forwarding?

Port forwarding exposes HA directly to the public internet via your router — not recommended for most users. The security risks are significant: you're exposing a web application to every port scanner and botnet on the internet. If your HA install has any vulnerability, or if you use a weak password, it can be compromised.

If you insist on port forwarding, at minimum: use a strong, unique password; enable multi-factor authentication in HA; use HTTPS (not HTTP) with a valid SSL certificate from Let's Encrypt; and consider blocking access from countries you don't visit. Even with all these measures, Tailscale or Nabu Casa are meaningfully safer because they don't expose a port at all.

Does the Raspberry Pi hardware affect remote access?

Your HA hardware (Raspberry Pi, Green, NUC, etc.) doesn't affect which remote access method you use — all methods work on all hardware. However, hardware does affect reliability: a Raspberry Pi running off an SD card can become unresponsive if the card corrupts, meaning your remote access goes down too. If remote access reliability matters, use a Pi 5 with NVMe storage, or the Home Assistant Green with its eMMC storage.

Comparing all remote access methods

Frequently Asked Questions

SmartWired participates in the Amazon Associates Programme. We may earn a commission from qualifying purchases at no extra cost to you.