How to Install Home Assistant OS on a Raspberry Pi 2026

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

This step-by-step guide shows you how to install Home Assistant on a Raspberry Pi. It's a proven way to build a smart home hub with full local control. The setup takes about 30 minutes. You'll have a single dashboard managing all your IoT devices.

Bottom line: One-third of all Home Assistant users run on Raspberry Pi (Home Assistant Blog, 2024). Flash Home Assistant OS to a microSD card using Pi Imager, insert it into your Pi 4 or Pi 5, plug in power and Ethernet, then open homeassistant.local:8123 in a browser. The whole process takes under 30 minutes.

You will:

• Set up the OS on your SD card
• Put the hardware together
• Get your hub running and online

With a Pi 4 or 5 and a few basic tools, you can build a hub that manages all your IoT devices from one screen.

Why Is Home Assistant OS the Best Choice for Raspberry Pi?

Home Assistant reached 2 million active installations in April 2025, and the platform deprecated both Core (2.5% of users) and Supervised (3.3%) methods that same year (Home Assistant Blog, 2025). That leaves Home Assistant OS as the recommended path for nearly all users.

HAOS is a tiny, fast operating system built specifically for the Pi and similar boards. It runs lean and stays out of your way. The Supervisor handles updates, add-ons, and backups on its own. You don't need to manage any of that yourself. This method gives you the best combination of stability, community support, and easy maintenance.

What Are the Key Components?

Home Assistant's architecture splits into four layers that work together across 2 million active installations (Home Assistant, 2025). Before you start, it helps to know what each piece does:

• Home Assistant OS: The small operating system that runs on your Pi
• Core: The smart control software inside the OS
• Supervisor: Handles updates, add-ons, and system tasks automatically
• Ecosystem: All the integrations, add-ons, and community tools

This guide uses the OS method. It's the easiest way to get started on a Pi.

What Do You Need Before Starting?

Over 68 million Raspberry Pi boards have been sold since 2012 (Raspberry Pi Ltd, 2024), and the Pi 4 and Pi 5 are the recommended models for Home Assistant. Make sure you have these items before you begin:

• A Raspberry Pi 4 or Raspberry Pi 5
• A microSD card with at least 32 GB storage
• A good power supply for your board
• An SD card reader to flash the OS
• An ethernet cable, or a Wi-Fi network ready to use
• A computer to download and flash the OS

One line there deserves more than a bullet. The power supply is the part people cheap out on, and undervoltage produces failures that look like software bugs. My board doesn't use a wall adapter at all. The Raspberry Pi 5 is mounted on a DIN rail in the electrical cabinet, next to the breakers, and it's fed from a Mean Well MDR-60-5 supply rated 5 V at 10 A. That decision came out of the wiring stage rather than the software stage, and it removed a whole category of problem: no plug to knock out of a socket, no adapter of unknown quality, and plenty of headroom for a USB coordinator and an SSD on the same rail.

Why A2 SD Cards Matter

A2 microSD cards are built for fast, small file tasks. That's exactly what Home Assistant does all day. An A2 card keeps writes fast and boot times short. It also lasts much longer than a standard card. Pick a card with at least 2 GB of RAM on the board too.

Want even better reliability? Backblaze data shows SSDs have a lifetime annual failure rate of just 0.90% (Backblaze, 2023). A USB-to-SSD adapter with the Pi gives you 3-5x faster I/O and far longer lifespan than any SD card.

How Do You Prepare Your SD Card with the Home Assistant OS?

1. Download the official Pi Imager tool from the Raspberry Pi website.

2. Open the Imager app.

• Pick your device.
• Go to Choose OS, then Other specific-purpose OS, then Home assistants and home automation. Pick the version that matches your Pi model.

• Insert your microSD card into the reader. Then pick it under Choose Storage.

• Click Next to write the OS to the card. This erases all data on it. Back up anything important first.

• When done, eject the card safely.

How Do You Flash Home Assistant Using Balena Etcher?

If you'd rather flash manually, use Balena Etcher. It's a clean, simple tool.

Direct Image Download

Find all images at Home Assistant OS GitHub releases.

Download the HAOS image that matches your Pi model. For Pi 5 it looks like:

• Image: haos_rpi5-64-XX.X.img.xz (replace XX.X with the latest version number)
• Checksum: haos_rpi5-64-XX.X.img.xz.sha256

Tip: Balena Etcher can flash compressed .img.xz files directly - no need to unpack.

What You'll Need

• A microSD card (16 GB min; 32 GB+ is better, A2/U3 if you can)
• A card reader
• Balena Etcher (Windows, macOS, or Linux)
• Pi board, official power supply, and ethernet for first boot

Flash with Balena Etcher

1. Save the .img.xz file to your computer.
2. Check the file hash if you want to be sure it's not corrupt:
   • Windows (PowerShell):

     Get-FileHash .\haos_rpi5-64-XX.X.img.xz -Algorithm SHA256

   • macOS:

     shasum -a 256 haos_rpi5-64-XX.X.img.xz

   • Linux:

     sha256sum haos_rpi5-64-XX.X.img.xz

   Compare the output to the .sha256 file contents. They must match exactly.
3. Install and open Balena Etcher.
4. Click Flash from file and pick the .img.xz file.
5. Click Select target and pick your microSD card. Double-check the drive letter.
6. Click Flash. Wait for it to finish and verify.
7. Enter your password if prompted.
8. Eject the card safely.

How Do You Assemble and Boot Your Pi?

Now it's time to put things together:

1. Insert the flashed microSD card into your Pi.
2. Plug in the ethernet cable. Connect it to your router. This gives a stable first-boot connection.
3. Add a Zigbee dongle via USB if you plan to use non-Wi-Fi devices, or pair a standalone coordinator from our best Zigbee hubs guide. Use a short USB extension cable to avoid signal issues.
4. Plug in the power supply. The Pi will boot into Home Assistant OS.

For step three I use a Home Assistant Connect ZBT-1, and it currently carries several dozen Zigbee devices: unbranded GU10 bulbs, leak sensors, ceiling mmWave motion sensors, a 24G presence sensor, soil moisture probes, a rain sensor, a rotary knob and a Sonoff MINI-ZBR3. One USB stick, no vendor bridge, no cloud account in the path. The extension cable isn't optional advice either. Plugged straight into a board sitting in a metal cabinet, a coordinator is fighting both USB 3 interference and a Faraday cage, and you'll blame the sensors for it.

For step four, remember that a Pi under load pulls more than a phone charger wants to give. Undervoltage shows up as random reboots during a database write, which is exactly how SD cards die.

You don't need a monitor or keyboard. The Pi runs headlessly. The first boot can take a few minutes, so be patient.

How Do You Access Your New Home Assistant Hub?

• Open a browser on your computer or phone. It must be on the same network as the Pi.
• Go to http://homeassistant.local:8123 or use your Pi's IP address with :8123.
• The first boot can take up to 20 minutes. It's setting everything up. Wait it out.
• After setup, you'll create a user account. Save your login details somewhere safe. You can't recover them if lost.

How Do You Fix Common Setup Issues?

If something goes wrong, try these fixes:

• Re-flash the SD card with the right OS image for your Pi model.
• Check your network. Wired ethernet works best for the first boot.
• Make sure your power supply is strong enough. Low power causes boot failures.
• Visit the Home Assistant community forums for help with your specific device.

How Do You Keep HAOS Updated?

Home Assistant shipped 12 major releases in 2024, each adding new integrations and security patches (Home Assistant Blog, 2024). Updates come frequently. When a new version ships, you will see a notification in the Settings panel. Before upgrading, check the release notes at the Home Assistant blog for any known issues with your Pi model.

The safest upgrade approach is this:

• Create a backup before every major update.
• Wait 2-3 days after a major release to let early bug reports come in.
• If an update causes issues, use Settings > System > Backups to restore your last working state.

The Supervisor handles all update mechanics. You do not need to re-flash your SD card for updates. Stay on the latest release for security patches and new integrations.

What Should You Do After Setup?

Once your hub is running, here's the path that works best. Start simple and build up.

First Time Steps:

1. Create a user account with a strong password
2. Set your home location for weather and sun-based automations
3. Pick your unit system (metric or imperial)
4. Set up your Wi-Fi if you prefer wireless

Use a quality A2 microSD card and back up your settings often. Add a case with a heat sink to keep your Pi cool during long use. Try simple automations based on time, presence, or sensor data.

Next Steps: Open the add-on store under Settings > Add-ons to install ESPHome, SSH, or Z-Wave support. Once the host is online, it helps to understand how HA models your gear, our guide to entities, devices, and automations explains the building blocks before you connect your first smart devices. Start with Wi-Fi devices for the easiest experience. Advanced users can edit configuration.yaml directly for fine-grained control over integrations and sensors. Build a few simple automations using the built-in editor. Try community blueprints and pre-made scripts. Set up alerts on your phone.

Hardware Add-Ons: If you use non-Wi-Fi devices, consider a Zigbee dongle for Philips, IKEA, and similar devices. Add a Z-Wave stick for older smart home devices. Pick up a Thread/Matter USB stick for newer smart home standards.

What Can You Build With Your Hub?

Here's what you can actually do with your hub once it's running:

Lights: Turn on hall lights at 80% when motion is detected at night. Turn them off 5 minutes after motion stops. Skip daytime hours in summer to save energy.

Climate: Warm your home one hour before you wake up. Lower the heat when everyone leaves. Create a guest mode that adjusts the temp and locks the doors. This is where a Pi stops being a hobby board. My heating is a Gree Versati III SPLIT heat pump rated 10 kW, and Home Assistant talks to it over Modbus rather than through a vendor app, so the pump's own numbers land in the same place as everything else. Underneath it sit 10 heating zones, each driven by a Sonoff panel reflashed to run under HA instead of the manufacturer's thermostat firmware. That combination was the single largest piece of work in the whole build, and it's also the one I'd defend hardest, because heating is the system where being locked out of your own data hurts most.

Energy: Track which devices use the most power. Turn them off after a set idle time. Avoid running big appliances during peak rate hours.

Security: Arm your system when everyone leaves. Randomly turn lights on and off to look like someone's home. Get phone alerts when a door or window opens. Use reliable sensors to keep an eye on every entry point. Worth saying plainly: the alarm itself shouldn't be the Pi's job. Mine is a wired Satel system that arms, disarms and sounds entirely on its own hardware, and it reaches Home Assistant through an Ethernet module and the satel_integra integration. HA reads zone states and can arm it, but if the Pi is off getting an update, the alarm doesn't notice or care. That split is deliberate. Automation on top, life safety underneath.

Morning Routine: Build a "Good Morning" scene. Gradually brighten your bedroom lights. Start the coffee. Show the weather on your dashboard.

Why Does Home Assistant Beat Other Hubs?

Most smart home hubs lock you into one brand. Amazon Alexa needs Amazon. Google Home needs Google. Home Assistant works with nearly any device from any brand. If you want remote access without opening ports, Nabu Casa's 6.50 EUR/month subscription adds encrypted cloud connectivity and voice assistant support. With over 3,400 integrations available and 2 million active installations (Home Assistant, 2025), the platform keeps growing. You get:

• No vendor lock-in
• No subscription fees for local control
• Your data stays on your own network
• Full customization for advanced users
• Long-term support even if a brand stops making products

The Pi is a solid hub platform. It's cheap, uses little power, and runs 24/7 without big electricity bills. The community is huge. You'll find help for almost any problem.

How Do the Raspberry Pi Models Compare for Home Assistant?

The Raspberry Pi 5 uses an Arm Cortex-A76 processor clocked at 2.4 GHz, delivering 2-3x the performance of the Pi 4's Cortex-A72 (Raspberry Pi Ltd, 2023). Here's how the three main models compare for Home Assistant:

Feature          | Pi 4 (4GB)  | Pi 5 (4GB)  | Pi Zero 2W
Processor Speed  | 1.5 GHz     | 2.4 GHz     | 1.0 GHz
RAM              | 4GB         | 4GB         | 512MB
Device Limit     | 200-300     | 300-500+    | 10-30
Add-ons Limit    | 3-5         | 5-8         | 1-2
Price            | 50 EUR      | 75 EUR      | 14 EUR
Recommended      | Small home  | Large home  | Testing

The Raspberry Pi 5 boots nearly twice as fast as the Pi 4 for Home Assistant workloads (Peyanski, 2024). The newer D0 stepping also cuts idle power by 30% (Jeff Geerling, 2024). The Pi 4 handles small to medium homes well. The Pi 5 is better for big setups with 300+ devices. The Zero 2W is fine for testing but not for daily use.

Start with the Pi 4 (4GB) if your budget is tight. Move to the Pi 5 if you plan to grow your setup. An SSD upgrade adds 28 EUR to 46 EUR but makes the Pi 3 to 5 times faster.

How Do You Secure and Back Up Your Hub?

Security research consistently finds that a majority of IoT devices in homes run with default or weak credentials, making them easy targets for unauthorized access. Use a fixed IP address for your Pi. Set it in your router's settings. This stops homeassistant.local from failing to resolve. Use a strong password on your account right away. Enable two-factor authentication in Settings. Keep your system updated - new versions fix security issues. Use HTTPS with a Let's Encrypt cert for safe remote access. A VPN is safer than opening a port to the internet.

Set up auto backups in Settings. Keep the last 7 days saved. Store a copy on a USB drive or in the cloud. Test restoring from backup every month.

Here's how that looks in practice for me, including the part that isn't finished. The Home Assistant configuration is a Git repository pushed to GitHub, which means every automation has a history and git blame answers the question "when did this stop making sense and what was I thinking". Data goes to Google Cloud. Secrets live outside the repository, because a public mistake with a private token is a bad afternoon. And the honest gap: I have never actually restored from those backups. Not once. So I can tell you the pipeline exists and that version control on automations has already saved me from my own edits, but a backup you haven't tested is a hypothesis, not a plan. Do as I say on this one, not as I do.

If your Pi fails, here's how to recover:

1. Flash a new SD card with the latest Home Assistant OS.
2. Don't create an account yet. Go straight to Settings and restore from backup.
3. Everything comes back: your devices, automations, and settings.

When Is a Raspberry Pi the Wrong Home Assistant Box?

Honest answer: more often than this guide's title suggests. Add up a Pi 5, the official 27W power supply, a case with cooling, and the SSD upgrade you'll genuinely want, and you land at 130 to 160 dollars. Used mini PCs with an Intel N100 or an older Core i5 regularly sell in that same range, and they bring more RAM, faster storage out of the box, and x86 compatibility for add-ons like Frigate camera detection that struggle on Arm without a Coral accelerator.

Skip the Pi entirely if any of these apply to you. You plan to run video processing or local voice models, both eat the Pi's CPU alive. That one is easy to test honestly: three Reolink PoE streams, an E1 Outdoor, an E330 and a video doorbell, are nothing at all while the Pi is only passing them through to a viewer, and a completely different question the moment you ask it to detect objects in them. You already own any spare x86 machine, even an old laptop with a broken screen outlasts an SD card.

Then there's the failure mode nobody advertises. In this house, Home Assistant is a single point of failure for lighting. The switches are wired for it, the bulbs are Zigbee, and if the Pi is down the lights genuinely do not work. I accepted that on purpose, with my eyes open, in exchange for one control layer and no vendor bridges. It's a defensible trade for someone who enjoys this. It is a terrible trade if the people living with the result would rather the light just came on. Be sure which of those you are before you build it, because SD card corruption after a power cut remains the single most common way a Pi-based Home Assistant dies, and it always picks the weekend you're away. The Pi earns its place through low power draw, silence, and the huge community, not through being the best hardware for the job.

What Are the Home Assistant Install Options?

• Home Assistant OS (this guide): Best for beginners. Easy updates and add-ons. Takes 30 to 45 minutes.
• Container: Good for Docker users. Needs more manual work.
• Core: For developers who know Python. Most control, steepest learning curve. Being deprecated in 2025.
• Virtual Machine: Great for testing before buying a Pi.

Your Pi is now ready to become a powerful smart home hub. Start simple. Build up over time. The platform grows with you.

For the full Home Assistant installation documentation, check the official site. Once your hub is running, continue with the first 10 things to configure in Home Assistant to set up your smart home properly.