Remote Access to Home Assistant - Without VPN
Access your Home Assistant from anywhere with a secure SSH tunnel. No VPN, no port forwarding, no router configuration. Setup with one command.
- Secure HTTPS tunnel
- Zero router configuration
- Works after one command
Why remote access to Home Assistant is so hard
Traditional solutions create more problems than they solve
VPN is complex and breaks mobile access
Setting up WireGuard or OpenVPN requires router configuration, key generation, and constant maintenance. VPN drains battery and doesn't reconnect reliably on mobile.
Port forwarding exposes your network
Opening port 8123 on your router makes your Home Assistant - and potentially your entire network - visible to the internet. A single misconfiguration can be devastating.
Nabu Casa only works with Home Assistant
If you also run Grafana, Node-RED, ESPHome, or any other service on your server, Nabu Casa can't help. You need a separate solution for each service.
From zero to remote access in 3 steps
No networking knowledge required
Install the agent
One curl command on your Home Assistant server. The agent installs as a system service and starts automatically.
Get your HTTPS subdomain
Your Home Assistant receives a permanent HTTPS subdomain of its own (e.g., smith-7b2e4d1a9f03.smarthomeentry.com) with automatic SSL.
Access from anywhere
Open your subdomain in any browser - phone, tablet, or laptop. Your Home Assistant is always just one click away.
Built for Home Assistant users
Everything you need for secure remote access
Works with all HA setups
Home Assistant OS, Docker, Core, Supervised - SmartHomeEntry works with every installation method.
Your own HTTPS subdomain
Get a permanent, memorable address like yourname.smarthomeentry.com with automatic SSL certificate.
Full dashboard with integrations
Automations, history, graphs, Node-RED, ESPHome - the entire Home Assistant ecosystem accessible through your browser.
No static IP or DDNS required
Works behind CGNAT, dynamic IPs, and restrictive ISPs. The agent makes only outbound connections.
Health monitoring & alerts
Know when your Home Assistant goes offline. Get email or webhook notifications within minutes.
SmartHomeEntry vs. alternatives
See how we compare to traditional remote access solutions
| SmartHomeEntry | VPN | Nabu Casa | |
|---|---|---|---|
| Setup time | ~2 min | 1-4h | ~5 min |
| No router config | ✓ | ✗ | ✓ |
| Your own HTTPS subdomain | ✓ | ✗ | ✗ |
| One-command install | ✓ | ✗ | ✓ |
| Works without static IP | ✓ | ✗ | ✓ |
* Nabu Casa works only with Home Assistant
Home Assistant remote access - frequently asked questions
Install the SmartHomeEntry agent with one curl command on your HA server (HAOS, Docker, Supervised, or Core). The agent opens a reverse SSH tunnel to our relay and registers a permanent HTTPS subdomain (e.g. yourhome.smarthomeentry.com). Zero router configuration, zero VPN - you just open the URL in your browser from anywhere.
Yes, with two differences: (1) Nabu Casa works ONLY with Home Assistant - SmartHomeEntry also handles Domoticz, OpenHAB, Node-RED, Grafana, Nextcloud, Jellyfin, any HTTP/HTTPS service. (2) You get a short, memorable HTTPS subdomain (yourhome.smarthomeentry.com) instead of nabucasa.com/ui/token... - easier to share, works without a Nabu account login. Pricing starts at $5 for 7 days (Nabu: ~$6.50/month flat fee).
Once the agent is installed, enter your subdomain (e.g. yourhome.smarthomeentry.com) in the Home Assistant mobile app - just like your local address. The app uses standard HTTPS, no VPN, no battery drain. Push notifications, camera streaming and all integrations work normally, including when switching between WiFi and mobile data.
Yes - this is one of the main SmartHomeEntry use cases. The agent only makes outbound SSH connections to our relay, so it needs no public IP, no port forwarding, no static address. It works behind CG-NAT on mobile operators, cable ISPs, and restrictive networks where traditional VPN or port forwarding fail.
We don't recommend it. Exposing port 8123 or 443 puts your HA directly on the public internet - automated scanners find it within minutes. Any new vulnerability in HA, Supervisor, or an add-on (ESPHome, Frigate, HACS) gives an attacker a foothold in your home network. SmartHomeEntry avoids this entirely: the agent initiates an outbound tunnel, and your HA is never directly reachable from the internet - only through our relay over HTTPS.
Technically yes - they don't conflict at the HA level. In practice you usually pick one: if you want Google Assistant/Alexa cloud integration, Nabu has it built in. If you only need remote UI access and you also run Node-RED, Grafana, Nextcloud or a NAS on the same machine, SmartHomeEntry is one tool for everything (see q2).
Get remote access to Home Assistant with one command
Get started now. No router configuration needed. No VPN required.
Related articles
In-depth guides and case studies for this integration
How to Manage Multiple Home Assistant Installations Remotely
You look after Home Assistant for several clients or properties. Here is what actually works for reaching all of them, what each approach costs in time, and where every option breaks down.
Read more
Home Assistant Green vs Raspberry Pi: Why 199 Dollars Is Not the Comparison
Green costs 199 USD and people call it expensive. Price out an equivalent Pi 5 build and the gap mostly disappears - but two other differences do not, and neither is the CPU.
Read more
Home Assistant Remote Access 2026: What the Tutorials Don't Tell You
7 ways to reach Home Assistant from outside - and the real pitfalls (CGNAT, security, family without a VPN, dying SD cards). Works behind every ISP, even 5G and mobile LTE.
Read more