Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Search "Home Assistant" and within five minutes you'll have three different products in your head, no idea whether any of them cost money every month, and a vague sense that you need to learn Python. None of that is true, and most of the confusion comes down to one thing: "Home Assistant" is not one product. It's three, and they get conflated constantly.
Home Assistant is free, open-source software. It runs entirely on hardware you own, on your own network, with no cloud dependency and no subscription required to function. Home Assistant Green is a physical box Nabu Casa sells that has that software pre-installed — a convenience purchase, not a requirement. Home Assistant Cloud is an optional paid add-on from Nabu Casa that makes remote access and voice assistants easier to set up. You can use Home Assistant fully, forever, without ever touching the second or third item on that list.
That distinction matters because it changes the two questions almost every beginner actually has: what do I need to buy, and is there a monthly bill waiting for me. The honest answer is that you need one small computer to run the software on, optionally a radio dongle later if you want cheap battery-powered sensors, and no subscription at all unless you specifically want easy remote access or Alexa/Google voice control without configuring it yourself.
This guide walks through the decision in the order it actually needs to happen: what the software is and how it's installed, which hardware makes sense for a first-timer versus a tinkerer, when — if ever — you need a Zigbee, Z-Wave, or Thread dongle, and what Matter changes about all of this in 2026. It's written for someone who hasn't installed anything yet and wants to make one good decision instead of five bad ones.
Quick Reference: The Three Things Named "Home Assistant"
| Term | What it actually is | Cost |
|---|---|---|
| Home Assistant (the software) | Free, open-source smart home platform. Runs locally, works offline, no account required. | Free, forever |
| Home Assistant Green | A small pre-built box from Nabu Casa with the software already installed | One-time hardware purchase |
| Home Assistant Cloud | Optional Nabu Casa subscription for remote access, voice assistants, and cloud backup | Optional monthly/annual fee |
If you only remember one thing from this guide, make it this table.
How Home Assistant Actually Works
Home Assistant ships in four installation flavors, and picking the right one up front saves a lot of backtracking later.
Home Assistant OS (HAOS) is the one almost everyone should run. It's a dedicated appliance operating system that bundles the Home Assistant Core software with a Supervisor and an add-on store, and it auto-updates. It's what powers Home Assistant Green out of the box, and it's what you'll install yourself on a Raspberry Pi or a mini PC. Unless you already run Docker for other projects and specifically want to manage the host OS yourself, HAOS is the right call.
Home Assistant Container runs Home Assistant as a Docker container on a Linux system you maintain yourself. You lose the add-on store and manage updates and the underlying OS on your own. This is for people who already have a Docker habit.
Home Assistant Core and Home Assistant Supervised are the manual, contributor-oriented paths — a Python virtual environment or a hand-built Debian install with no GUI installer. Both were officially deprecated in mid-2025 and represented a small fraction of installs even before that; there's no reason for a new user to start here.
One practical note: as of 2025, Home Assistant moved to 64-bit only. If you're looking at older tutorials that mention 32-bit ARM builds, they're describing a path that no longer exists. Stick to current documentation for anything install-related.
The takeaway for a first setup: choose HAOS, choose a 64-bit device, and don't overthink Container/Core/Supervised — they solve problems you don't have yet.
Choosing Your Hardware: The 2026 Buying Ladder
This is the decision that actually matters, and it comes down to three realistic options plus one you should skip.
Home Assistant Green — The Easiest Start
Home Assistant Green is Nabu Casa's official plug-and-play hub, built around a quad-core ARM processor with 4 GB of RAM and 32 GB of onboard storage. It ships with the software pre-installed, connects over Gigabit Ethernet, and draws very little power — it's fanless and silent. There's no built-in Zigbee, Z-Wave, or Thread radio, so if you want those protocols you'll add a USB dongle later; Wi-Fi and Matter-over-Wi-Fi devices work with it from the first boot.
Specs
- Quad-core ARM Cortex-A55 @ 1.8 GHz
- 4 GB RAM / 32 GB eMMC storage
- Gigabit Ethernet, 2x USB-A
- Fanless, near-silent operation
- HAOS pre-installed
Pros
- Genuinely plug-and-play — realistic first automation inside about 30 minutes
- No assembly, no flashing, no command line required
- Backed directly by the team building the software
Cons
- No built-in wireless radio for Zigbee/Z-Wave/Thread — that's an added purchase
- The onboard eMMC storage sees real wear under default settings; moving your history database and backups to an external USB drive early on is worth doing from day one rather than after a scare
- Costs more than assembling your own Raspberry Pi in some configurations
Verdict: The right choice if you want to plug something in, follow the app, and have Home Assistant running today without touching a terminal.
Perfect for: first-time users who want the official, supported path with zero assembly.
Raspberry Pi 5 — Best Value for Tinkerers
If you're comfortable flashing an SD card once and want more flexibility — or you simply already own a Raspberry Pi — the Pi 5 is the community's default recommendation in 2026. It's a meaningful jump over the Pi 4, with a quad-core Cortex-A76 processor running at 2.4 GHz, delivering roughly two to three times the CPU performance. It boots natively from NVMe or USB storage with no extra setup step, unlike its predecessor.
Specs
- Quad-core ARM Cortex-A76 @ 2.4 GHz
- 4/8/16 GB RAM options (8 GB recommended if you're running camera AI or 100+ devices)
- Gigabit Ethernet, dual-band Wi-Fi
- Single-lane PCIe for NVMe storage via a HAT
- Needs a 27W USB-C power supply
Pros
- Best raw performance per dollar in the Home Assistant hardware lineup
- Native NVMe/USB boot removes the old SD-card reliability headache entirely
- Handles Frigate camera AI and larger device counts (50+) comfortably at 8 GB
Cons
- Requires you to source and assemble a case, power supply, and (ideally) an NVMe hat and drive yourself
- You're responsible for flashing HAOS and maintaining the hardware — no official support line
- Community consensus is clear: skip microSD for anything beyond initial testing; SD cards fail without warning under sustained write loads
Verdict: The best pick if you're willing to spend twenty minutes assembling a kit in exchange for more headroom and lower long-term cost.
Perfect for: DIY-comfortable users who want more performance and don't mind sourcing their own storage.
If you already own an older Raspberry Pi 4, it still runs Home Assistant capably for a modest setup — just budget for a USB SSD rather than relying on a microSD card long-term, and note it needs a one-time EEPROM update before it will boot from USB.
Home Assistant Yellow — Skip This One New
Home Assistant Yellow was the previous official hub, built around a Raspberry Pi Compute Module with a built-in Zigbee and Thread radio, NVMe storage, and optional Power over Ethernet. It's a genuinely capable piece of hardware — but Nabu Casa discontinued new manufacturing, and stock of new units is effectively gone. Existing owners still get software updates, so if you already have one, keep using it. If you're starting fresh, Nabu Casa's own recommendation is Green plus a separate Zigbee/Thread dongle, or a mini PC with a dongle if you want more power.
Verdict: Not a new purchase in 2026 — buy Green or a Pi 5 instead and add a dongle for the same functionality.
Perfect for: existing owners only; not a recommendation for new buyers.
Search current listings on Amazon
Do You Need Zigbee, Z-Wave, or Thread on Day One?
No. This trips up a lot of beginners who assume a dongle is mandatory before they can start. It isn't. Wi-Fi devices and Matter-over-Wi-Fi devices connect straight to Home Assistant with no additional radio hardware. A dongle becomes worth adding once you want cheap, battery-powered sensors (door sensors, motion sensors) that sip power for years, or you want a mesh network that doesn't add load to your home Wi-Fi.
Zigbee is the most common add-on protocol for beginners moving past Wi-Fi-only setups. It's cheap, has a huge device ecosystem, and mains-powered Zigbee devices act as repeaters that strengthen your mesh — a practical tip is to pair mains-powered devices (plugs, bulbs) before battery sensors, so the mesh is solid by the time you add battery-powered nodes. The current official adapter is the Home Assistant Connect ZBT-2, the successor to the original SkyConnect/ZBT-1 dongle, which is being phased out. Whichever one you use, plug it into a USB extension cable rather than directly into the hub — USB 3.0 ports generate 2.4 GHz interference that causes real dropouts on the radio.
Z-Wave operates on a different, less congested frequency band and offers better wall penetration and range, at a higher per-device cost. The official Home Assistant Connect ZWA-2 supports the current 800-series Z-Wave standard and Z-Wave Long Range, and it's the adapter to buy new. Aeotec also makes well-regarded controllers; their current flagship, the Z-Stick 10 Pro, combines Z-Wave and Zigbee radios in a single dongle, while their older Z-Stick 7 has been discontinued and is best avoided for new purchases.
Check the ZBT-2 on Amazon
Check the official Z-Wave adapter on Amazon
Check the Aeotec Z-Stick 10 Pro on Amazon
Thread is different again — it's a low-power mesh networking protocol, not a device ecosystem of its own, and it's most relevant because it's how many newer Matter devices communicate. A Thread-based Matter device needs a Thread Border Router nearby; the ZBT-2 dongle can serve as one, as can many existing Apple TV, HomePod, and Google/Nest devices already sitting in your home.
Practical starting rule: if your first few devices are Wi-Fi smart plugs or Matter-over-Wi-Fi bulbs, skip the dongle entirely for now. Add a Zigbee/Thread adapter when you're ready to buy your first battery sensor.
Matter in Home Assistant: What It Actually Does
Matter is the industry's attempt at a universal smart home standard, and Home Assistant has certified support for it. As of the current release cycle, the underlying Matter server was rebuilt on a modern open-source implementation, bringing faster recovery after restarts, more reliable firmware updates for Matter devices, and a visual map of your Thread mesh. A recent update also added the ability to add Matter devices without pulling out your phone, using low-cost proxy hardware — historically, commissioning a Matter device required a companion app.
The detail that catches people out: Matter is not the same thing as Thread. Matter can run over Wi-Fi, Ethernet, or Thread, and a "Matter device" box doesn't tell you which one you're getting. If it's Thread-based, you need a Border Router in range, same as above.
In practice, Matter in 2026 is promising but not flawless — pairing still fails often enough to be annoying, especially from Android, and some categories (energy-monitoring smart plugs, for instance) expose fewer details over Matter than they would through a brand's own native integration. For a device like a Philips Hue bulb, where Home Assistant already has a mature direct integration, that native integration will typically give you more control than going through Matter. Zigbee remains the more dependable and often cheaper choice for beginners building out a first mesh, with Matter growing into a genuinely universal layer over time rather than replacing everything overnight.
Extending Home Assistant with HACS
Once the basics are running, most users eventually hear about HACS — the Home Assistant Community Store. It's worth understanding what it is before installing it: HACS is a community-built tool, not an official Home Assistant feature, and it lets you browse and install custom integrations, dashboard cards, and themes built by the community, authorized through a free GitHub account.
The important caveat: HACS code runs directly inside Home Assistant, unlike official add-ons which run in isolation. A poorly maintained custom repository can genuinely break your system. The sensible approach is to treat HACS as an intermediate step rather than a day-one install — get comfortable with core automations first, back up before installing anything through it, and stick to popular, actively maintained repositories once you do start using it.
Which Setup Should You Choose?
| Your situation | Recommended path |
|---|---|
| You want it working today, no assembly | Home Assistant Green |
| You're comfortable flashing an SD card and want more performance for less | Raspberry Pi 5 + NVMe storage |
| You already own a Raspberry Pi 4 | Use it — just add a USB SSD, skip microSD long-term |
| You want cheap battery sensors from the start | Green or Pi 5 + a Zigbee/Thread dongle (ZBT-2) |
| You want long-range, low-interference devices (locks, water sensors) | Add a Z-Wave adapter (ZWA-2 or Aeotec Z-Stick 10 Pro) |
| You want remote access without configuring a VPN yourself | Consider the optional Nabu Casa Cloud subscription |
| You're comfortable with networking tools | Set up Tailscale, WireGuard, or a Cloudflare Tunnel for free remote access instead |
If you want the single lowest-friction answer: Home Assistant Green, no dongle, add Zigbee later once you know what you're automating first.
→ Check the current price of Home Assistant Green on Amazon
Frequently Asked Questions
Q: Is Home Assistant really free?
Yes. The core software is free and open-source, and it runs fully offline with no account required. You only pay for the hardware it runs on, and optionally for the Nabu Casa Cloud subscription if you want managed remote access, voice assistant integration, and cloud backup without configuring those yourself.
Q: Do I have to buy Home Assistant Green, or can I use hardware I already own?
Green is a convenience purchase, not a requirement. Home Assistant runs on a Raspberry Pi, most mini PCs, and virtual machines. If you already own a compatible device, you can install Home Assistant OS on it for free and skip buying anything.
Q: What's the difference between ZHA and Zigbee2MQTT?
Both let Home Assistant talk to Zigbee devices through a coordinator like the ZBT-2. ZHA is built directly into Home Assistant and is the simpler starting point. Zigbee2MQTT supports a wider range of devices but requires setting up an separate MQTT broker. Beginners can start with ZHA and move to Zigbee2MQTT later if a specific device needs it.
Q: Do I need a Zigbee or Z-Wave dongle to get started?
No. Wi-Fi devices and Matter-over-Wi-Fi devices work immediately with no additional hardware. Add a Zigbee/Thread dongle when you want inexpensive, battery-powered sensors, and consider Z-Wave for longer range or interference-free devices like smart locks.
Q: What is Home Assistant Cloud, and do I need it?
It's an optional Nabu Casa subscription that adds easy encrypted remote access, one-click Alexa and Google Assistant integration, cloud voice processing for the built-in Assist feature, and automatic cloud backup. Home Assistant works completely without it — remote access can be set up for free using a VPN tool like Tailscale or WireGuard, or a Cloudflare Tunnel, if you're comfortable with a bit more configuration.
Q: Is Home Assistant hard to learn?
The initial setup — especially on Green — is genuinely quick, often under 30 minutes to a first working automation. The learning curve shows up later, once you start writing more advanced automations, managing YAML configuration, or adding community integrations through HACS. The practical approach is to start with one device and one automation, get comfortable, then expand gradually rather than trying to automate the whole house in week one.
Conclusion
The confusion around Home Assistant almost never comes from the software itself — it comes from not knowing that "Home Assistant," "Home Assistant Green," and "Home Assistant Cloud" are three separate things with three separate price tags, two of which are actually optional. Once that's clear, the decision tree is short: pick Green if you want the easiest possible start, pick a Raspberry Pi 5 if you're comfortable with light assembly and want more performance for less money, and skip a Zigbee or Z-Wave dongle entirely until you have a specific device that needs one.
Everything after that — Matter, HACS, automations — is genuinely worth exploring, but none of it needs to be decided on day one. Get one device connected, build one working automation, and let the rest of the ecosystem unfold from there.
