Raspberry Pi Home Assistant SSD Setup UK 2026

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

Do this in 5 steps

1. Buy the parts (table below — if you already own a Pi 5, you only need the SSD).
2. Plug the SSD into your main computer and flash Home Assistant OS (64-bit) using the Raspberry Pi Imager.
3. Plug the SSD into one of the Pi's USB 3.0 ports, plug in ethernet, plug in power last.
4. Wait 1–5 minutes for first boot.
5. Browse to http://homeassistant.local:8123 on any device on the same network and complete onboarding.

That's the whole job. The rest of this guide explains the parts choices, the SD-card death problem, the Pi 4 EEPROM gotcha (if you're using a Pi 4), and the day-one settings worth doing.

At-a-glance: parts list for a reliable UK build

If you already own a Pi 5, the SSD is the only essential purchase (~£125). Full new build, all-in: ~£221.

Add the optional ZBT-2 (~£38) and a new build totals ~£259. UK external-SSD pricing is high in 2026 — Samsung T7 Shield and Crucial X9 Pro 1 TB land in the same band as the Kingston XS1000, so there's no cheaper drop-in. Our pre-configured habbb kit covers Pi 5, internal NVMe SSD, NVMe-carrier case and the 27W PSU for £150 inc VAT (ZBT-2 is a £60 add-on if needed) — see the bottom of this guide.

Already own a Pi 4? Everything below still works — the SD-card problem is identical, and a USB-booted Pi 4 with a decent SSD will run HA for years. The only Pi 4-specific step is a one-time bootloader update; details in the Pi 4 sidebar below.

This guide walks you through the whole thing: the parts you need, the one-time EEPROM update most tutorials skip, flashing Home Assistant OS to a USB SSD, and getting through first boot without losing an afternoon. It assumes you already know you want Home Assistant — you just want to install it on hardware that won't eat itself.

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. On a home with twenty or thirty devices, that's thousands of small writes an hour, every hour, forever.

Consumer SD cards are not built for that. They're designed for cameras and phones, where writes happen in bursts and then stop. Each cell in the flash has a finite number of write cycles, and cheap cards wear through those cycles faster than the marketing suggests. Worse, when an SD card starts to fail it rarely warns you. The failure mode is usually silent file system corruption — Home Assistant just stops booting one morning, and the last clean backup you have is from whenever you last remembered to make one.

The common death window is 18 to 24 months. Sometimes sooner. The Reddit horror stories about HA installs dying overnight are real, and they're almost always SD card corruption. The good news: it's entirely avoidable.

Why a USB SSD is the right answer

A proper SSD is built for the kind of sustained write workload Home Assistant produces. It's faster to boot, faster to restore backups, faster when the recorder database grows past a few gigabytes, and — crucially — it doesn't silently rot under constant logging.

SSD prices have come down to the point where the cost difference between a decent SD card and a proper USB SSD is maybe £20. For a machine you plan to leave running 24/7 for years, that's not a decision worth agonising over.

Our house pick is the Kingston XS1000. It's small, cool-running, reliable, and fast enough that the Pi's USB 3.0 bus is the bottleneck long before the drive is. Any reputable alternative from Samsung (T7 Shield), Crucial (X9 Pro) or SanDisk in a similar form factor will do the same job in the same price band — the important thing is that it's a real SSD in a USB enclosure, not a USB stick dressed up as one.

What you need

Keep the parts list tight. Buying the right kit once is cheaper than buying the wrong kit twice. This list assumes a Pi 5; if you're on a Pi 4, see the Pi 4 sidebar further down.

• Raspberry Pi 5 — 2 GB is enough for a typical Home Assistant install; 4 GB if you'll run Frigate or other heavy add-ons.
• Kingston XS1000 USB SSD — 1 TB is the entry size Kingston ships and it's far more than Home Assistant will ever need. 2 TB if you want to stop thinking about it. Samsung T7 Shield or Crucial X9 Pro in the same capacity work just as well at similar UK prices.
• Official Raspberry Pi 27W USB-C PSU — not a random phone charger, and specifically the 27W (5V/5A) supply for the Pi 5. The older 15W brick used with the Pi 4 will undervolt a Pi 5 and cap downstream USB peripherals at 600 mA total, which can starve an attached SSD.
• Argon NEO 5 case — Pi 5-specific. The original Pi 4 NEO physically does not fit. A Pi running HA 24/7 will throttle in a plastic case with no heatsink.
• Ethernet cable — use wired for the Pi if you possibly can. Wi-Fi works, but a cabled hub is one fewer thing to debug.

The Pi 5 boots from USB natively. No spare SD card, no EEPROM update, no keyboard or monitor required for the install — everything happens from your main computer.

Pi 4 sidebar — the one-time EEPROM update

Skip this section if you're on a Pi 5. The Pi 5 boots from USB and NVMe natively with no bootloader configuration; the section below only applies to a Pi 4.

Raspberry Pi 4s shipped for years with an older bootloader EEPROM that doesn't boot from USB by default. Newer ones do, but unless you know your unit is recent, assume you need to update it. It's a five-minute job, you only do it once, and you'll need a spare SD card (any old 8 GB card from a drawer is fine).

1. Download Raspberry Pi Imager from raspberrypi.com and install it on your main computer.
2. Plug your spare SD card into your computer.
3. In Imager, click the operating system picker and navigate to the Misc utility images section, then Bootloader (Pi 4 Family), and pick USB Boot. This writes a tiny image whose only job is to update the Pi's EEPROM. Make sure you pick the Pi 4 family option specifically — there's a separate Pi 5 entry that will not do what you want.
4. Write that image to your spare SD card.
5. Pop the SD card into the Pi (no SSD attached yet), connect power, and wait. After about ten seconds the green activity LED will start blinking rapidly and continuously — that's the success signal. (If you instead see a repeating pattern of four flashes and a pause, that's the failure code; try the update again.)
6. Power off the Pi, remove the SD card, and you're done. The Pi will now boot from USB by default, forever.

If you skip this step and your Pi 4 has old firmware, the Pi will simply sit there doing nothing when you plug the SSD in later, and you'll waste an hour wondering why. Do the EEPROM update first.

Flashing Home Assistant OS to the SSD

Now the main event. This bit is genuinely quick.

1. Plug the Kingston XS1000 into your main computer using its USB cable.
2. Open Raspberry Pi Imager.
3. Click the operating system picker and navigate to Other specific-purpose OS, then Home automation, then Home Assistant.
4. Choose the Home Assistant OS image for your Pi (Raspberry Pi 5 64-bit, or Raspberry Pi 4 64-bit). 32-bit (armv7) images no longer exist — Home Assistant dropped 32-bit support entirely in HA OS 17.0, released May 2025, so the 64-bit image is the only option.
5. Select the SSD as the target. Double-check this. Imager will warn you before wiping the drive.
6. Click Write and wait. On a half-decent USB connection this takes a few minutes.
7. When it finishes, eject the drive cleanly.

Now plug the SSD into one of the USB 3.0 ports on the Pi — the USB 3.0 pair is typically marked in blue on the connector, the USB 2.0 pair in black. You paid for the speed, use it. Connect the ethernet cable. Connect power last.

First boot

The Pi will come to life, the LEDs will flicker, and then it'll quietly get on with first-boot setup. On a Pi 4 or 5 the onboarding page is normally reachable within a minute or two — Home Assistant's own docs say allow up to 5 minutes. If nothing's showing after 5 minutes, something's gone wrong and a re-flash is usually the answer. (Old tutorials talked about 20–30 minute first boots; that hasn't been true for several HA OS releases.)

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 home routers don't handle mDNS cleanly — find the Pi's IP address in your router's device list and use that instead, for example http://192.168.1.42:8123.

You'll land on the onboarding screen. Create your account, give the instance a name, pick your timezone and location for sunrise/sunset automations, and let it scan for devices already on your network. It'll usually find a surprising number of them immediately.

Bare minimum hardening

This isn't a security course. But two things are worth doing on day one, before you forget.

Use a long, random password for your Home Assistant user. This is the account that will eventually control your heating, 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. Home Assistant supports backup add-ons for Google Drive, Nextcloud, Samba and others. Install one, point it at cloud storage you control, and schedule a daily backup. The SSD is far more reliable than an SD card, but hardware still dies eventually, and a restore from yesterday is an evening of grumbling. A restore from never is a weekend of tears.

Or skip all this

If you've read this far and you're starting to wonder whether you actually want to spend a Saturday on EEPROM updates and onboarding screens — that's fair, and that's where we come in.

habbb ships a pre-configured Home Assistant hub for £150 inc VAT, then manages it for £30/month. Same idea as the build above but tidier: a Raspberry Pi 5 with an internal NVMe SSD inside a NVMe-carrier case, the official 27W USB-C PSU, all pre-flashed with Home Assistant OS. ZBT-2 Zigbee/Thread radio is an optional £60 add-on if your devices need it. Remote access is set up, daily backups are running, and the unit is tested on our bench before it leaves us. You plug it in, it connects, you get on with your life.

We think of the subscription as a boiler service contract. We keep what you have working — updates tested before they're deployed, 24/7 monitoring, active support when something misbehaves, tweaks to your existing automations. Adding a brand-new integration or a big new automation is a separate quoted job, same as a plumber fitting a new radiator.

If that sounds more your speed, leave us your email and we'll be in touch.

Common questions

Pi 5 or Pi 4? Pi 5 is the current recommendation and what habbb ships in its kit — faster, native NVMe support, no EEPROM step, and the 2 GB variant is barely more than a Pi 4 in 2026. Pi 4 is still a perfectly fine HA host if you already own one; everything in this guide except the Pi 5-specific 27W PSU and NEO 5 case still applies.

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

Do I still need the SD card after the EEPROM update? No. Once the EEPROM is updated, the Pi will boot from the USB SSD and the SD card slot can stay empty forever. Put the SD card back in the drawer.

What about the Home Assistant Green? The Green is a tidy all-in-one and Nabu Casa's official entry-level box, and it's a perfectly reasonable choice if you want zero setup. You give up the flexibility of standard Pi hardware, though, and there's no built-in Zigbee/Thread radio (you'd add a Connect ZBT-2 separately). A Pi 5 with an internal NVMe SSD is what habbb ships to its own customers — we like the replaceable parts, the thermal headroom, and the NVMe IO.

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

Do I need a Zigbee stick straight away? Only if you have Zigbee devices you want to control directly (Hue without the bridge, Aqara sensors, IKEA Tradfri). You can always add one later — the Home Assistant Connect ZBT-2 is the current pick and supports Zigbee or Thread on one dongle (one protocol at a time — see the dedicated guide for the nuance).