Best Hardware for Home Assistant in 2026: Green, Raspberry Pi, Mini PC or Unraid
If you want the easiest path and don’t already own the hardware, I’d start with Home Assistant Green. It comes with Home Assistant OS installed, so you plug in power and Ethernet and finish setup. If you already have a Raspberry Pi 4 or 5 sitting around, try that first. A used mini PC dedicated to Home Assistant OS gives you more room to grow. And if you already run an Unraid or Linux server, you can run Home Assistant there, but that’s the option where your update and uptime habits matter most.
I’ve used Home Assistant in a container, compared notes with Mike Wieger about running it on Unraid, and learned the hard way what happens when a working installation falls behind on updates. I don’t think buying a faster CPU is the first decision. I’d ask who is going to maintain the installation, how I’ll restore it if something fails, and which radios I’ll actually need.
Home Assistant hardware comparison
| Option | Best for | Setup | Apps? | Main trade-off |
|---|---|---|---|---|
| Home Assistant Green | New users | Low | Yes | Fixed capacity, radios extra |
| Raspberry Pi 4 or 5 | Existing Pi owners | Medium | Yes, with HAOS | Whole-kit cost; reliable storage |
| Used mini PC | Dedicated system | Medium | Yes, with HAOS | Verify UEFI, SSD, power and noise |
| Existing Unraid / VM host | Home-server owners | Medium–high | Yes with HAOS VM; no with Container | Shared uptime |
| Linux with Docker | Experienced self-hosters | High | No | Maintain OS, images and companion services |
Home Assistant OS includes apps, previously called add-ons. Home Assistant Container does not. Home Assistant OS is the recommended installation for most users.
Raspberry Pi 4 or 5 | Anyone who already owns one | Medium: flash Home Assistant OS | Yes | Full kit cost; storage and power supply; official Pi minimum is 2 GB RAM
Used mini PC / NUC | Dedicated installation with room to grow | Medium: UEFI and installation media | Yes with HAOS | Validate boot compatibility, network, noise and power draw
Unraid or other VM host | Existing home-server owners | Medium/high | Yes with HAOS VM; no with Container | Shares host maintenance and uptime
Linux + Docker (Container) | Experienced self-hosters | High | No | You maintain host, container images and companion services
Home Assistant Green: the easiest starting point
Home Assistant Green is the machine I’d point most new users toward if they haven’t already got a computer to reuse. It has Home Assistant OS installed, which removes the need to choose a Linux distribution, organize Docker updates or work through an operating-system installation.
Green is a fixed appliance with 4 GB of RAM, 32 GB of eMMC storage, Gigabit Ethernet and two USB 2.0 ports. You cannot simply upgrade its RAM. It also has no built-in Zigbee, Z-Wave or Thread radio, so you’ll need appropriate additional hardware if your devices depend on those protocols.
Home Assistant says the initial setup needs an Internet connection. Afterward, Home Assistant itself can operate on your local network, although integrations tied to a cloud service still need Internet access.
Price check — November 21, 2026: Nabu Casa’s suggested US retail price for Green is $199 (€179 in Europe). Actual retailer pricing can differ; check the official Home Assistant Green page before buying. I wouldn’t use an old $99 listing as an assumed current price.
I’d choose Green because the installation and maintenance path is straightforward, not because it wins a processor benchmark. If my plan included video recording or demanding local AI models, I’d run those workloads separately rather than assuming Green should do everything.
Raspberry Pi 4 or 5: start with what you own
If a Raspberry Pi 4 or 5 is already sitting in a drawer, use it. There’s no reason to buy a new computer before discovering whether the existing one handles your automations, dashboards and sensors.
Home Assistant’s install guide for Home Assistant OS on a Raspberry Pi lists a Pi 4 or 5, a suitable power supply, at least 2 GB of RAM, a microSD card and an Ethernet connection. That’s the official Pi minimum, not my recommended specification for every setup.
For a new purchase, add up the whole cost: board, power supply, case, storage, and any adapters. It’s easy to compare a Pi’s board price to Green’s complete appliance price and forget the rest of the kit.
Storage matters because Home Assistant maintains a database, history and other files. The official Pi instructions describe microSD, and I’d also investigate a suitable SSD arrangement for a Pi model where it makes sense. I wouldn’t call SSD boot universally necessary or imply that every adapter and boot method is supported.
My advice: reuse a Pi you own; compare complete system costs before buying one specifically for Home Assistant.
Used mini PCs: a dedicated system with room to grow
This is the category I like for a technology enthusiast who wants a dedicated Home Assistant machine. Small retired Intel and AMD office computers can offer SSD storage, wired Ethernet and more room to grow without taking up much space.
A dedicated Home Assistant OS installation needs a compatible 64-bit computer that boots in UEFI mode. Before buying a used office PC, check its UEFI boot support, whether the proposed SSD works as a boot drive, wired networking, power use and fan noise. Not every retired machine is a clean fit.
I’d shop for roughly 8 GB of RAM and a reliable SSD, with an appropriate amount of space for my history and backups. That’s my buying preference, not an official Home Assistant minimum. I don’t see a compelling reason for a powerful gaming CPU if the machine is only running normal home automations.
One benefit of a mini PC is the choice to install Home Assistant OS directly or put it in a VM on a host you already understand. That’s flexibility, but the installation takes more effort than unpacking Green.
Unraid, virtual machines and Docker
I wouldn’t buy a large Unraid server just to run Home Assistant. If you already own one, however, it may be a sensible place to host the software. The important distinction is that Unraid is the host; Home Assistant OS in a VM and Home Assistant Container are different installation approaches.
A VM running Home Assistant OS includes Home Assistant’s apps experience (historically called add-ons). A Container installation doesn’t include that apps system, and you manage the Docker image and supporting services yourself. Those differences affect how much maintenance lands on your desk.
Back in Home Gadget Geeks 472 in 2020, Mike Wieger and I were both experimenting with Home Assistant on Unraid. Mike moved from a container to a VM in part because he wanted the add-on workflow. I was running a container. That’s a useful example of two choices that both work but feel different to administer; it is not a modern benchmark or a current step-by-step installation procedure.
HGG472 — Home Assistant on Unraid
Home Assistant installation options
If Home Assistant shares a server with media, storage or experimental containers, it can be interrupted by that server’s maintenance. I would decide whether that is acceptable before choosing the shared-host route.
My Home Assistant Container update lesson
While Phil Hawthorne was previewing Home Assistant 2026.10 in HGG691, I checked my own version. It said 2026.5. I run Home Assistant Container, and nothing was refreshing the container image, so it had quietly fallen several releases behind even though it kept working.
Phil’s point was that waiting means you may face months of changes at once, potentially including breaking changes, instead of dealing with releases gradually.
After the show I moved the installation into a cleaner Docker Compose-based workflow and upgraded from 2026.5.0 to 2026.9.4, with a backup and rollback ready. I also added an update check to my Jimbot status report. I still apply the upgrades by hand, on purpose.
Don’t forget the radios
The computer runs Home Assistant, but not every smart-home device communicates the same way. Wi-Fi and Ethernet devices may use your existing network; Zigbee, Z-Wave and Thread devices require a compatible controller or border-router arrangement. Bluetooth devices introduce their own coverage concerns.
The Home Assistant Connect ZBT-2 runs Zigbee or Thread, not both at the same time. If you need both supported as separate networks, plan for the necessary separate hardware. ZBT-2 isn’t a Z-Wave or Bluetooth adapter. Z-Wave needs appropriate compatible hardware for your region’s frequency.
Where the server sits matters too. A USB radio buried behind a metal rack may provide poor coverage. Plan radio placement and extension options with the adapter’s instructions instead of assuming the nearest USB socket is the best location.
Phil Hawthorne explained ESPHome Bluetooth proxies in HGG686. This is particularly interesting to me because I have a Bluetooth-connected air-conditioner soft-start device that barely reaches my Home Assistant host. I’d try an ESPHome Bluetooth proxy to improve that range.
How much computer does Home Assistant need?
For typical lighting, sensors, dashboards and automations, I would prioritize reliability over processor performance. A computer that runs reliably on Ethernet with dependable storage is more useful than an oversized workstation you don’t maintain.
Capacity becomes more important when you run additional demanding applications such as large history databases, video analytics or local voice/AI workloads. Those can be placed on a separate machine. For example, Frigate can analyze camera streams on another host and feed useful events into Home Assistant. Don’t size the Home Assistant controller as though it must also do every camera-processing task.
Plan how you’ll recover Home Assistant
Before I choose the machine, I want to know how I would recover its configuration after a disk failure or a bad update. Make a backup, store a copy somewhere other than the original device, and understand how to restore it onto compatible replacement hardware. It’s better to discover a missing step before the system breaks.
Ethernet, reliable storage and a suitable power supply matter. If losing Home Assistant during a short power outage would be a problem, think through whether a UPS should cover both its host and the networking devices it depends on. That doesn’t make the system fail-proof, but it makes the failure modes easier to understand.
Which setup should you choose?
Starting from scratch and wanting the easy route: Home Assistant Green.
Already own a Raspberry Pi 4 or 5: try it first.
Have a compatible used x86-64 computer: dedicate it to Home Assistant OS after checking UEFI, storage, noise and networking.
Already run an Unraid/Linux host and enjoy maintaining it: choose an HAOS VM if you want the OS apps experience, or Container if your Docker maintenance habits are already solid.
Frequently asked questions
What is the best hardware for Home Assistant?
For most new users without existing hardware, I’d start with Green. Someone who already owns a suitable Pi or mini PC may have no reason to buy another computer.
Is Raspberry Pi still a good choice?
Yes, especially when you already have one. For a new purchase, compare the fully assembled system cost.
Does Green need the Internet?
An Internet connection is needed for initial setup. The local system can continue operating without the Internet, but cloud-dependent integrations cannot.
How much RAM should I buy?
The official Raspberry Pi installation guide lists 2 GB as a minimum. For a used mini PC, 8 GB and an SSD are my shopping preferences, not Home Assistant requirements.
What is the difference between Home Assistant OS and Container?
Home Assistant OS includes the OS-managed apps system. Container does not; you manage the container image and other supporting services.
Do I need a Zigbee or Z-Wave stick?
Only if your devices require those technologies. ZBT-2 does Zigbee or Thread, but not both simultaneously, and does not supply Z-Wave or Bluetooth.
Can I move Home Assistant later?
Often, yes, by using a suitable backup and migration process. Check compatibility and restore instructions for the specific installation type before changing hardware.
My recommendation
I would spend less time searching for the fastest Home Assistant computer and more time deciding who will manage it and how I’ll recover it. Green removes many setup decisions. A Pi you already own is a sensible experiment. A used mini PC offers flexibility. An existing server may save money, but ties the house to your server maintenance habits.
The best choice is the installation you’ll actually keep updated, backed up and available.



One thought on “Best Hardware for Home Assistant in 2026: Green, Raspberry Pi, Mini PC or Unraid”