Raspberry Pi Home Assistant SSD Setup (US, 2026)

Published 16 May 2026 · 11 min read

If you're about to install Home Assistant on a Raspberry Pi, don't use an SD card. Here's why, and here's the 20-minute setup that won't have you restoring a dead install 18 months from now.

TL;DR — the short version

Buy a Raspberry Pi 5 (2 GB is enough for Home Assistant), an NVMe SSD with a Pi 5 NVMe HAT or a USB-attached SSD, the official 27W USB-C power supply, and a case. Flash the SSD with Home Assistant OS using the Raspberry Pi Imager (64-bit HA OS only — 32-bit support was dropped in HA OS 17.0 in May 2025). The Pi 5 boots from NVMe and USB natively — no EEPROM dance needed (that was a Pi 4 thing). Done in about 20 minutes.

If a DIY Pi build isn't your idea of a Saturday, Home Assistant Green is the pre-built alternative — sold by Nabu Casa and through US resellers at around $199 — and it works the same way once it's on your network. (The older Home Assistant Yellow is being wound down — see the alternatives section below.)

At-a-glance: parts list for a US build

Approximate US street prices, 2026. Stock and price move week to week — treat these as a guide, not a quote.

PartWhy this oneUS priceWhere to buy
Raspberry Pi 5 2 GBEnough for a typical smart home; 4 GB (~$80) if you'll run Frigate or other heavy add-ons~$65Adafruit, Micro Center, Canakit, PiShop.us, Amazon
Pi 5 M.2 HAT+ + 256 GB / 500 GB NVMe SSDCleanest mount, fastest IO, no USB cable dangling$12 HAT+ (or $15 Compact) + ~$30–$50 SSDAdafruit, Canakit, Pimoroni (HAT); Amazon, B&H, Micro Center (SSD)
Or: USB-attached portable SSD (e.g. Samsung T7 Shield 1 TB, Crucial X9 Pro)Cheaper, no HAT, slightly less tidy~$80–$120Amazon, B&H, Best Buy, Micro Center
Official Raspberry Pi 27W USB-C PSUThe Pi 5 spec is 5V/5A (25W); on a smaller 15W/3A PSU it caps downstream USB peripherals at 600 mA total, which can starve an attached SSD~$12Adafruit, Canakit, Amazon
Case with NVMe support (e.g. Argon NEO 5 NVMe, Pimoroni NVMe Base case)Passive cooling, NVMe carrier built in~$25–$35Argon Forty, Pimoroni, Adafruit
(Optional) Home Assistant Connect ZBT-2Zigbee/Thread radio — only if you have direct-Zigbee devices like Aqara or naked Hue bulbs~$50Nabu Casa store, ameriDroid, Amazon

Total for a clean Pi 5 + NVMe build: roughly $130–$200 depending on SSD size and case choice. Add another $50 if you need the Zigbee radio.

Already have a Pi 4? Everything below works on a Pi 4 too — the SD-card problem is the same, and a USB-booted Pi 4 with a real SSD will run Home Assistant for years. Pi 4 needs a one-time EEPROM update (sudo rpi-eeprom-update -a) to enable USB boot; Pi 5 does it out of the box. The 15W Pi 4 PSU is fine for a Pi 4 but will undervolt a Pi 5.

This guide walks the whole thing: parts, the flashing step, first boot, the hardening you should do on day one, and — if you don't want to spend the weekend on it — the two ways to skip the build entirely.

Why SD cards kill Home Assistant installs

Home Assistant is a busy piece of software. It writes to its database constantly: every state change from every sensor, every automation trigger, every log line. A typical home with twenty or thirty devices is thousands of small writes an hour, every hour, forever.

Consumer SD cards aren't built for that. They're designed for cameras and phones, where writes happen in bursts and then stop. Each cell has a finite number of write cycles, and cheap cards burn through them faster than the box claims. Worse, when an SD card starts to fail it rarely warns you — the failure mode is usually silent filesystem corruption. Home Assistant stops booting one morning and your last clean backup is from whenever you last remembered to take one.

The common death window is 18 to 24 months, sometimes sooner. The horror stories on r/homeassistant about HA installs dying overnight are real, and almost all of them are SD card corruption. It's also entirely avoidable.

Why an SSD is the right answer

A proper SSD is built for sustained writes. It boots faster, restores backups faster, handles the recorder database better as it grows, and doesn't silently rot under constant logging.

Two viable mounting options on a Pi 5:

  • NVMe HAT + M.2 NVMe SSD. The HAT sits under the Pi, the NVMe drive sits in the HAT, and the whole sandwich slots into a NVMe-aware case (Argon NEO 5 NVMe, Pimoroni NVMe Base, Geekworm X1001/X1003). Cleanest result. This is the same internal-NVMe layout habbb ships in the UK kit, just sourced from US retailers.
  • USB-attached portable SSD. A Samsung T7 Shield, Crucial X9 Pro or SanDisk Extreme. Cheaper, no HAT, and the Pi 5's USB 3.0 bus is the bottleneck long before the drive is. Works fine — just slightly less tidy.

Either way, you're done buying SD cards for HA.

What you need

Keep the list tight. Buying the right kit once is cheaper than buying the wrong kit twice.

  • Raspberry Pi 5 — 2 GB if you're running a normal smart home, 4 GB if you'll run heavy add-ons (Frigate, ESPHome with lots of devices, BlueMaestro Bluetooth bridges). Available from Adafruit, Micro Center, Canakit and PiShop.us.
  • An NVMe SSD with HAT, or a USB-attached SSD — see above. 256 GB is more than HA will ever need; 500 GB if you want to never think about it again.
  • Official Raspberry Pi 27W USB-C power supply — not a random phone charger. Home Assistant is sensitive to power instability; undervoltage causes weird, hard-to-diagnose failures. The Pi 5 specifically needs the 27W to enable its full USB current budget.
  • Case with decent cooling — passive aluminum cases (Argon NEO 5) are quiet and run cool. A bare Pi running HA 24/7 will throttle without one.
  • Ethernet cable — use wired if you can. Wi-Fi works, but a cabled hub is one fewer thing to debug.

You can do the whole flash from your main computer; the Pi only needs the keyboard/monitor if you want to watch first boot, and even that's optional.

Flashing Home Assistant OS

This is the main event, and it's quick.

  1. Download Raspberry Pi Imager from raspberrypi.com and install it on your computer.
  2. Connect the SSD to your computer — for NVMe, an external USB-to-NVMe enclosure makes this trivial; for USB-attached SSDs, just plug it in.
  3. Open Imager. Click the operating system picker, navigate to Other specific-purpose OS → Home automation → Home Assistant.
  4. Choose the Home Assistant OS image for Raspberry Pi 5 (64-bit) — or the Pi 4 image if that's what you have. There is no 32-bit image any more; HA OS dropped 32-bit (armv7) support entirely in HA OS 17.0, released May 2025.
  5. Select the SSD as the target. Double-check this — Imager will warn you, but it will happily wipe whichever drive you point it at.
  6. Click Write and wait. A few minutes on a half-decent connection.
  7. Eject the drive cleanly when it finishes.

For NVMe, seat the SSD into the HAT, mount the HAT under the Pi, and close the case. For USB, plug the SSD into one of the USB 3.0 ports — there are two of each on the Pi 5, with the USB 3.0 pair typically marked in blue on the connector — not the USB 2.0 ports. The speed difference matters for a drive. Connect ethernet, then connect power last.

First boot

The Pi will come to life, the LEDs will flicker, and then it gets on with first-boot setup. The onboarding page is usually reachable within a minute or two — Home Assistant's own docs say to allow up to 5 minutes. If nothing's up after 5 minutes, something went wrong on the flash and re-flashing is the answer 90% of the time.

Once it's ready, open a browser on any device on the same network and go to http://homeassistant.local:8123.

If that doesn't resolve — some routers and mesh systems handle mDNS poorly — find the Pi's IP address in your router's device list and use that instead, e.g. http://192.168.1.42:8123.

You'll land on the onboarding screen. Create your account, give the instance a name, pick your time zone and ZIP for sunrise/sunset automations, and let it scan for devices on your network. It'll usually find more than you expect on the first pass — most modern smart-home stuff in a US home announces itself via mDNS or SSDP.

Bare minimum hardening

This isn't a security course. Two things to do on day one:

Use a long, random password for your Home Assistant user. This account will eventually control your thermostat, your locks and your cameras. Treat it accordingly. A password manager is your friend.

Turn on automatic backups to somewhere that isn't the Pi. HA supports backup add-ons for Google Drive, OneDrive, Nextcloud, Samba and S3. Pick one, point it at cloud storage you control, and schedule a daily backup. SSDs are far more reliable than SD cards, but hardware still dies eventually — and "restore from yesterday" is an evening of grumbling; "restore from never" is a weekend of tears.

The alternative — Home Assistant Green

If you'd rather skip the parts-list step entirely, Home Assistant Green is Nabu Casa's pre-built option for the US market. RRP $199, 32 GB eMMC storage, no built-in Zigbee/Thread radio (add a Connect ZBT-2 separately if you need one), plug-and-play. Available from Amazon US, ameriDroid, CloudFree and Seeed Studio.

Home Assistant Yellow — the older, more flexible CM4-based box — is no longer in production per Nabu Casa's own page. The pre-assembled Standard variant is discontinued; only kit versions requiring a separately-purchased Raspberry Pi Compute Module 4 remain available, and Nabu Casa now redirects buyers to Green. Third-party resellers (ameriDroid in particular) still list assembled Yellow units with newer compute modules as aftermarket builds — those work, but they're not the official path any more. For new US buyers in 2026 the choice is Green or a self-built Pi 5; Yellow is not the practical middle ground it once was.

Either route — Green or self-built Pi 5 — is bit-for-bit compatible with habbb's BYOHA managed service. We adopt whatever you've got running.

Or skip the maintenance entirely

If you've read this far and you're starting to wonder whether you really want to spend a Saturday on flashing screens and onboarding wizards — and then more Saturdays, every few months, on Core updates, integration breakages, and backup restores when something goes sideways — that's where habbb comes in.

habbb is a managed Home Assistant service. The US tier is BYOHA — $60/month plus state sales tax, no contract. You buy or build the hardware (this guide, or HA Green); you install Home Assistant OS and complete onboarding; we take over from there. Daily backups to our infrastructure, secure remote access via Cloudflare Tunnel, monitored updates that we test on a bench unit before deploying to yours, and a real person who responds when something misbehaves. No reflash, no migration downtime — we adopt your running instance.

We don't sell hardware in the US (yet — the UK kit isn't economical to ship internationally), so this guide is the build half. The managed half lives over here.

Common questions

Can I use a Pi 4 instead? Yes — and if you already own one, do. The SD-card-vs-SSD argument is identical, and a USB-booted Pi 4 with a quality SSD will run HA for years. Pi 5 is a faster machine with a cleaner NVMe story; Pi 4 is the pragmatic choice if you already have one in a drawer.

Is 2 GB of RAM really enough? For a typical household with a few dozen devices, yes. If you plan to run Frigate (camera AI) or several heavy add-ons, go for 4 GB or 8 GB.

NVMe HAT or USB-attached SSD — which is better? Functionally, they're the same once Home Assistant is running. NVMe is faster on paper and tidier in a case; USB is cheaper and easier if you already have an external SSD lying around. Pick whichever you'll actually finish building this weekend.

What about the Home Assistant Connect ZBT-2? It's the Zigbee/Thread USB radio — successor to the older SkyConnect / ZBT-1, available from Nabu Casa's store. You only need it if you have direct-Zigbee devices (Aqara sensors, naked Hue bulbs without the Hue Bridge, IKEA Tradfri) or Thread devices. If your home is Wi-Fi-led (Ecobee, Ring, Nest, Sonos), you can skip it. Pick the radio mode that matches your devices — one protocol at a time per dongle.

How often will I need to replace the SSD? Honestly, probably never. A quality SSD under HA's write workload should last many years. Keep your cloud backups healthy and you won't need to care.

What if I want zero setup and zero ongoing work? That's exactly what habbb's $60/month BYOHA tier covers — you do this guide's hardware step once, we run the operational layer forever. See the US managed service guide for the full breakdown of what's covered.