Home Assistant Beginner FAQs: Backups, Remote Access, Local Control
If you’re new to Home Assistant, the three questions that come up most are how to back up your setup, how to reach it when you’re away, and how to keep everything working on your local network. This article answers those directly, then explains the background, options, and common pitfalls so you can set up a reliable smart home hub.
What Home Assistant Actually Is
Home Assistant is free, open-source software that runs on a dedicated device (like a Raspberry Pi or a small PC) and connects to your smart lights, sensors, cameras, and other devices. It gives you one dashboard to control everything, and it processes all commands locally on your network rather than relying on a cloud service. That local-first design is the core reason people choose it over proprietary hubs.
Because it’s software, your configuration lives in a set of text files and a database. That makes backups straightforward—you copy the files—but it also means you need to think about where those files are stored and how to restore them if the device fails.
Backups: What to Save and How
Your Home Assistant setup consists of three main parts: the configuration files (YAML files that define automations, scenes, and device integrations), the database (which stores history and states), and any add-ons you’ve installed (like a media server or a network storage add-on). The simplest backup is a complete snapshot of the entire system, which includes all three.
If you’re running Home Assistant OS or a supervised installation, the built-in Backups feature creates a single compressed file containing everything. You can trigger it manually from Settings → System → Backups, or schedule automatic backups. The file is saved to the local disk by default, but you should copy it somewhere else—a USB drive, a network share, or a cloud service like Google Drive or Dropbox via an add-on.
For a manual configuration (running Home Assistant Core in a Python environment), you can simply copy the .homeassistant directory (or config folder) to a safe location. The most important files are configuration.yaml, secrets.yaml (which holds passwords and tokens), and the .storage folder (which holds the state of integrations).
Restoring is equally simple: in the Backups page, upload a backup file and choose “Restore.” It will bring back your configuration, integrations, and history. Test a restore at least once—many users discover too late that their backup was incomplete or corrupted.
Remote Access: Three Main Options
Remote access means controlling Home Assistant when you’re not on your home Wi-Fi. There are three common ways to do it, each with different trade-offs.
- Home Assistant Cloud (Nabu Casa) – A paid subscription service that provides a secure remote connection without any port forwarding or dynamic DNS. You just log in with your Nabu Casa account, and you get a URL like
https://yourname.nabu.casa. It also enables voice assistants and Alexa/Google integration. Cost is around $6.50 per month (as of 2024). - Port forwarding + Dynamic DNS – You open a port on your router and forward it to your Home Assistant device, then use a dynamic DNS service (like DuckDNS) to get a stable hostname. This is free but requires you to set up SSL certificates (via Let’s Encrypt) and exposes your network to the internet. It’s not recommended for beginners because misconfiguration can lead to security issues.
- VPN (WireGuard or Tailscale) – You install a VPN server on your home network, or use a mesh VPN like Tailscale, and connect to it from your phone or laptop. Once connected, you can access Home Assistant as if you were home. This is more secure than port forwarding and often easier than it sounds—Tailscale can be installed as an add-on in a few clicks.
For most beginners, Nabu Casa or Tailscale are the best choices. Both avoid exposing your home network directly to the internet. If you go the VPN route, you’ll need to open the Home Assistant app while connected to the VPN—there’s no separate URL to type.
Local Control: What Stays On Your Network
Local control means your devices and automations work even if your internet connection goes down. Home Assistant is designed for this: it communicates with devices on your LAN using protocols like Zigbee, Z-Wave, or Wi-Fi (via local APIs). As long as your router and Home Assistant device are powered, automations run, dashboards work, and devices respond.
However, there are exceptions. Some integrations rely on cloud services—for example, certain Wi-Fi bulbs only work through the manufacturer’s cloud, and voice assistants like Alexa or Google require internet. If you want true local control, choose devices that support local APIs. For Zigbee and Z-Wave, you’ll need a USB stick like a Conbee or Z-Wave stick, which lets Home Assistant talk directly to the devices without a hub.
A common misconception is that you need internet for Home Assistant to work at all. That’s false for the core system. But if you use the mobile app while away from home, you’ll need remote access (as above). Locally, the app works over Wi-Fi without internet.
Common Problems and How to Avoid Them
Beginners often hit the same wall: the setup works, but something breaks after an update. Here are the most frequent issues and fixes.
- Backup file too large – If you have years of history, the database can be gigabytes. Use the “Recorder” integration to purge old data, or exclude the database from backups (you can re-create history later).
- Remote access not working – If you set up port forwarding, make sure your router’s external port matches the internal port (usually 8123). Also, your ISP might block port 80/443, so use a non-standard port.
- Zigbee devices dropping off – This is often due to interference or too many devices on one coordinator. Move the USB stick away from metal and USB 3.0 ports, and add more routers (powered Zigbee devices) to extend the mesh.
- Automations not firing – Check the “State” of the entity in Developer Tools. Often the trigger is wrong (e.g., using “state” instead of “from/to”).
How to Choose: Cloud vs. Local vs. Hybrid
Your choice depends on your priorities. If you want maximum privacy and reliability, go local-only: use Zigbee/Z-Wave devices, avoid cloud-dependent integrations, and use a VPN for remote access. If you want convenience and voice control, Nabu Casa is the easiest path—it’s a subscription, but it supports the project and saves you time.
Many users start with Nabu Casa, then later switch to Tailscale once they’re comfortable. There’s no penalty for switching—your automations and devices stay the same.
Costs and Hardware
Home Assistant itself is free. You need hardware to run it. A Raspberry Pi 4 or 5 (with a good SD card or SSD) is the most common choice, costing around $50–$100. A used mini PC (like an Intel NUC) is more powerful and often more reliable for larger setups. You’ll also need a Zigbee/Z-Wave USB stick ($30–$50) if you want to use those wireless protocols.
There are no mandatory costs beyond hardware and electricity. Nabu Casa is optional, and you can run everything without it.
Safety and Security Considerations
Local control has a security advantage: your data stays in your home. But remote access introduces risk. If you expose Home Assistant to the internet, use strong passwords, enable two-factor authentication, and keep the system updated. Avoid using default ports and never disable authentication.
Also, be careful with third-party add-ons. Only install from the official add-on store or reputable repositories. A malicious add-on could access your entire system.
Finally, remember that Home Assistant is a hobbyist tool—it’s not a certified security appliance. For critical systems (like door locks), use a separate, dedicated smart home hub that is professionally supported.
Frequently Asked Questions
Do I need a cloud subscription to use Home Assistant?
No. Home Assistant works fully offline. The cloud subscription (Nabu Casa) is only for remote access and voice assistant integration. You can use a VPN or port forwarding for free remote access.
How do I back up my Home Assistant automatically?
Go to Settings → System → Backups, and enable “Automatic backups.” You can set a schedule (e.g., daily) and choose how many backups to keep. To store them off-device, install the Samba Backup add-on or use a cloud sync add-on like Google Drive Backup.
What is the difference between Home Assistant OS and Home Assistant Core?
Home Assistant OS is a full operating system that includes Home Assistant and an add-on store. It’s the easiest to install and manage. Home Assistant Core is just the Python application that runs on an existing OS (like Debian). The OS version is recommended for beginners because it handles updates and backups automatically.
Can I access Home Assistant without internet?
Yes, locally. When you’re on the same Wi-Fi, you can access the dashboard by typing the IP address of your Home Assistant device (e.g., http://192.168.1.10:8123). The mobile app also works locally. For remote access, you need internet (or a VPN).
Why are my devices not showing up in Home Assistant?
Most likely the device isn’t on the same network or the integration isn’t set up. For Wi-Fi devices, ensure they are on the same VLAN/subnet. For Zigbee/Z-Wave, you need to pair them via the integration’s “Add Device” button. Check the logs for errors.
Is Home Assistant safe to expose to the internet?
It can be, if you follow security best practices: use a strong password, enable 2FA, use HTTPS via Let’s Encrypt, and keep the system updated. However, a VPN is safer because it doesn’t expose any ports. For most beginners, a VPN is recommended.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.