Home Assistant is a free, open-source home automation platform that runs on your own hardware and puts you — not a manufacturer's cloud server — in control of your devices. It's the single most popular self-hosted smart-home system in the world, but the flexibility that makes it powerful also makes it intimidating on day one. This guide walks through exactly what you need and the order to do things in.

What Home Assistant actually is

Home Assistant is software, not a device. It runs on a small computer somewhere on your home network, talks to your smart-home devices over their native protocols (Wi-Fi, Zigbee, Z-Wave, Bluetooth, and more), and gives you one consistent dashboard and automation engine across all of them — regardless of brand. Instead of five different apps for five different brands of smart plug, you get one.

Because it runs locally, most of it keeps working even if your internet connection drops. Your lights, locks, and thermostat don't stop responding just because a manufacturer's servers are down.

Step 1: Choose your hardware

Home Assistant needs somewhere to run continuously. Common options, roughly ordered from cheapest to most capable:

  • Raspberry Pi 4 or 5 (4GB+ RAM): The classic starting point. Inexpensive, low power draw, well documented. A good SD card or, better, a USB SSD will make it noticeably more reliable long-term.
  • A dedicated mini PC (Intel N100 class): More overhead for add-ons, faster database performance, and it can double as other home-lab duties. Worth it if you already know you'll grow into a larger setup.
  • An old laptop or spare PC: Perfectly fine to start, provided you can leave it running and it isn't excessively power-hungry.
  • Home Assistant Yellow or Green: Official, purpose-built hardware from the Home Assistant project. More expensive but zero-guesswork.

If you're not sure you'll stick with it, start with hardware you already own — you can always migrate your configuration to better hardware later using a backup (see our backup guide).

Step 2: Install Home Assistant OS

For beginners, install Home Assistant Operating System (HAOS) rather than running it inside an existing OS. HAOS is a dedicated, minimal operating system that manages Home Assistant, its add-ons, and updates for you.

  1. Download the Home Assistant flashing tool from the official Home Assistant website.
  2. Select your hardware (e.g. "Raspberry Pi 4") and let the tool write the OS image to your SD card or SSD.
  3. Insert the media into your device, connect it to your router with an ethernet cable if possible, and power it on.
  4. Wait 10–20 minutes for first boot — it's doing a lot of setup in the background even though nothing appears to happen.

Once it's up, visit http://homeassistant.local:8123 from a browser on the same network to reach the onboarding wizard.

Tip: Wired ethernet is more reliable than Wi-Fi for the machine running Home Assistant itself, especially if it's also acting as a Zigbee or Z-Wave coordinator.

Step 3: Complete onboarding

The setup wizard will ask you to create an administrator account, set your home's location (used for sunrise/sunset-based automations and weather), and it will automatically scan your network for compatible devices. Don't worry about connecting everything immediately — get the basics running first.

Step 4: Add your first integrations

"Integrations" are how Home Assistant talks to specific brands and protocols. Go to Settings → Devices & Services → Add Integration and search for whatever you already own — many popular brands (Philips Hue, IKEA, Sonos, Shelly, and hundreds more) are detected automatically. Add two or three devices first so you can learn the interface without being overwhelmed.

Advertisement

Step 5: Build a simple dashboard

Home Assistant auto-generates a basic dashboard, but it's worth spending 15 minutes organizing it by room or function once you have a handful of devices. Go to the dashboard, click the three-dot menu, and choose "Edit Dashboard" to start rearranging cards.

Step 6: Write your first automation

Automations follow a simple pattern: trigger → condition (optional) → action. A good first automation is turning on a light when a door sensor opens after sunset. Go to Settings → Automations & Scenes → Create Automation and use the visual editor — you don't need to write any code.

For more ideas once you're comfortable, see our guide to automations worth setting up first.

Step 7: Set up backups before you need them

This is the step most beginners skip and later regret. Configure automatic backups from day one — see our full backup and restore guide for a strategy that takes about ten minutes to set up.

Common first-week mistakes

  • Adding too many devices at once. Add a few, learn the naming and area conventions, then scale up.
  • Skipping areas/rooms. Assigning devices to areas early makes voice control and dashboards far easier later.
  • Ignoring updates. Home Assistant ships frequent updates with real fixes; read release notes before updating, and always keep a recent backup.

Where to go next

Once your core setup is stable, read why local-first matters to understand which integrations to prioritize, and Zigbee vs. Z-Wave vs. Wi-Fi before your next device purchase.