First time Home Assistant setup: what to buy, what to skip, and how not to waste money

This is the guide we wish existed when we started. Not a Home Assistant installation tutorial (there are plenty of those). This is the buying and planning guide that comes before installation: what hardware to run it on, which protocol to start with, what devices to buy first, and how to avoid the mistakes that send people back to the store or into forum rabbit holes.

Pick your controller first

Home Assistant needs a computer to run on. The three realistic options in 2026:

Home Assistant Green (~$99)

The official plug-and-play box from Nabu Casa. You plug it in, connect Ethernet, and you’re running Home Assistant in minutes. No OS installation, no terminal commands, no fiddling.

The Green is not the most powerful hardware you can buy, but that isn’t the point. It removes the biggest barrier for beginners: getting HA actually running. Rockchip RK3566, 4GB RAM, 32GB eMMC storage. Enough for a solid smart home with dozens of devices, automations, and integrations.

It does not include any radios. You’ll need a USB coordinator for Zigbee, Thread, or Z-Wave. That’s fine. Most setups need one anyway.

Buy the Green if: you want the lowest-friction path into Home Assistant and your ambitions are “automate my house well,” not “run a homelab.”

Home Assistant Green product notes

Intel N100 Mini PC (~$100–$180)

The community’s emerging favorite, and for good reason. An N100-based mini PC gives you dramatically more headroom than the Green for a similar (sometimes lower) price. 8–16GB RAM, 128–500GB SSD, and enough CPU to run Frigate NVR for camera AI, Node-RED, Grafana, and anything else you want alongside Home Assistant.

Popular models include the Beelink EQ13/S12 Pro, GMKtec G3, and Trigkey G4. These draw about 10W, run silent, and are small enough to tuck behind a TV or on a shelf.

The catch: you need to install HAOS yourself. It’s not hard (flash it to a USB stick, boot from it, done), but it’s one more step than the Green’s out-of-box experience.

Buy a mini PC if: you think you might run cameras, want more processing power, or already know your way around a BIOS menu.

Beelink EQ13 product notes · GMKtec G3 product notes

Raspberry Pi 5 (~$100+ with accessories)

Still works, but no longer the default recommendation. Once you add a case, proper power supply, NVMe HAT or SSD adapter, and active cooling, you’re spending as much as a mini PC with less performance. The Pi 5 is a fine choice if you already own one or have specific reasons to use it, but for new buyers starting from scratch, the Green or a mini PC is a better deal.

Avoid: running HA from an SD card. Corruption is a matter of when, not if. Use eMMC (Green) or SSD (mini PC, Pi with NVMe) storage.

What about Home Assistant Yellow?

Yellow was discontinued in October 2025. It had a built-in Zigbee/Thread radio, which was its key selling point. If you see one for sale, it still works and will receive software updates, but Nabu Casa is no longer manufacturing it. Don’t pay a premium for old stock.

Choose your first protocol

This is the decision that shapes which devices you can buy. Don’t overthink it. Any of these will work. But Zigbee is the default for a reason.

Start with Zigbee

Zigbee is the best starter protocol for most people. The device selection is enormous, prices are low, Home Assistant support is deep, and the mesh networking means your devices relay signals to extend range automatically.

You need a USB coordinator to use Zigbee. The top choices:

Home Assistant Connect ZBT-1 (~$30), the official Nabu Casa coordinator. Silicon Labs chip, decent antenna, supports both Zigbee and Thread (one at a time). Easiest option if you want to keep things simple.
Sonoff Dongle Plus MG24 (~$20-$25), with strong community support, good range, and a lower price than the official option.
SMLIGHT SLZB-06 (~$40-$50), which connects via Ethernet/PoE instead of USB. Best for VM setups or when you want to place the coordinator in an optimal location away from your server.

Critical tip: always use a USB extension cable (1–2m) with a USB coordinator. The electrical noise from your computer’s USB ports degrades Zigbee performance significantly. This is the single most common source of “my Zigbee network is flaky” posts.

Software choice: Home Assistant offers two Zigbee integrations: ZHA (built-in, easier) and Zigbee2MQTT (broader device support, more configuration options). Pick one and commit. Switching later means re-pairing every device. For beginners, ZHA is the easier start. If you care about supporting obscure devices or want more granular control, Zigbee2MQTT is worth the extra setup.

Best Zigbee coordinators for Home Assistant · Zigbee vs Z-Wave vs Matter vs Thread

Add Z-Wave when it makes sense

Z-Wave runs on sub-1 GHz frequencies, which means it punches through walls better than Zigbee and doesn’t compete with your Wi-Fi for airspace. Certification requirements are stricter, so devices tend to “just work” with fewer compatibility surprises.

The tradeoff: Z-Wave devices cost more (a single Z-Wave plug runs ~$36 vs a 4-pack of Zigbee plugs for ~$39), the device ecosystem is smaller, and devices are region-locked to specific frequencies.

When Z-Wave is the better choice:

Locks, garage doors, and security-critical devices where reliability matters most
Large homes where you need range through multiple walls
Outdoor sensors where the sub-1 GHz signal carries further

Many serious setups run both Zigbee and Z-Wave. That’s completely fine and sometimes the smartest approach.

Matter over Thread: the cleanest new option

Thread is a low-power mesh protocol. Matter is the interoperability standard that rides on top of it. Together, they’re the most modern local-first path: IP-based, multi-platform (Home Assistant, Apple Home, Google Home, Alexa simultaneously), and designed for battery-powered sensors from the ground up.

What you need: A Thread border router. The Connect ZBT-1 can serve as one (but must choose Thread OR Zigbee firmware, not both simultaneously). If you already own an Apple HomePod Mini, Google Nest Hub (2nd gen+), or Amazon Echo (4th gen+), those already function as Thread border routers that Home Assistant can leverage.

What’s available in Matter-over-Thread today:

Sensors: Aqara Door/Window Sensor P2, Aqara Motion Sensor P2, Aqara FP300 presence sensor, Aqara Climate Sensor W100, Eve Door & Window, Eve Motion, Eve Weather, Heiman smoke and CO alarms, IKEA VALLHORN motion (~~$9), IKEA PARASOLL contact (~~$10), IKEA BADRING leak (~$10)
Lights: Aqara LED Bulb T2, Nanoleaf Essentials bulbs and lightstrips
Switches: Eve Light Switch, Eve Dimmer Switch, Aqara Light Switch H2
Locks: Aqara Smart Lock U200/U300, Nuki Smart Lock Go/Pro/Ultra
Climate: Eve Thermo radiator valve
Covers: Eve MotionBlinds, MotionBlinds motors

Thread/Matter doesn’t have the ecosystem depth that Zigbee has yet, but the device selection is growing fast, especially for sensors. Use it when a Thread/Matter device is the best option in its category. Don’t force it as your only protocol.

Matter over WiFi: local Matter without a mesh

Some Matter devices use your existing Wi-Fi network instead of Thread. They still speak the Matter protocol (so they work across platforms and integrate locally with HA), but they connect over WiFi instead of forming a mesh.

What’s available in Matter-over-WiFi today:

Smart plugs: Meross MSS315 (with energy monitoring, ~~$13 each in 4-packs), TP-Link Tapo P125M (~~$17 each)
Switches: TP-Link Tapo S505, SwitchBot Relay Switch 1PM, ELTAKO dimmers and impulse switches (EU)
Air purifiers: SwitchBot Air Purifier
Covers: MotionBlinds motors (via Matter bridge), SwitchBot Curtain 3 and Roller Shade (via Hub 2/3)
Robots: SwitchBot K20+ Pro (vacuum, basic Matter on/off only)

The key difference from regular WiFi devices: Matter-over-WiFi devices communicate locally using a standard protocol. They don’t need a vendor cloud to function, and they don’t need a vendor-specific integration in Home Assistant. The Matter integration handles them all. That said, they still use WiFi bandwidth and can’t run on batteries efficiently, so Thread is the better choice for sensors.

Local WiFi devices: no Matter, but still local

Not all good WiFi devices use Matter. Some have their own local APIs or protocols that Home Assistant talks to directly, without any cloud involvement. These are perfectly fine, and sometimes better than Matter, because the native integrations expose more features.

The best local WiFi devices:

Shelly relays and plugs are the gold standard for local WiFi control. Native HA integration (used by ~24% of all HA installations), no hub needed, no cloud dependency. Supports MQTT for advanced users. Officially “Works with Home Assistant” certified. Their Gen4 devices also support Zigbee and Matter.
ESPHome devices use fully open-source firmware that talks to Home Assistant over your local network. Apollo Automation, Everything Presence, and Konnected all build ESPHome-certified devices. Zero cloud dependency by design. Note: while ESPHome has a native API that other platforms can use, the simplest path is Home Assistant.
HomeWizard energy monitors include P1 meters, energy sockets, and water meters. All local WiFi, all “Works with Home Assistant” certified. EU-focused.
Reolink cameras offer local RTSP/ONVIF streaming and work with Frigate NVR. “Works with Home Assistant” certified.

When local WiFi makes sense: mains-powered devices where WiFi battery drain doesn’t matter, such as smart plugs, in-wall relays, thermostats, cameras, and energy monitors. Avoid WiFi for battery-powered sensors (it kills batteries fast) and avoid deploying more than ~20 WiFi devices without considering network congestion.

How to spot and avoid cloud-dependent WiFi devices

This is the trap. Most cheap WiFi smart home devices look the same on the shelf, but some work locally and some are cloud-dependent junk that stops working when the vendor decides it should. Here’s how to tell them apart:

Before you buy:

Check the Home Assistant integrations page. Look for the device’s integration and check the “IoT class” badge. You want “Local Push” or “Local Polling.” Avoid “Cloud Polling” and “Cloud Push” for anything important.
Look for “Works with Home Assistant” certification. Every certified device is verified to work locally.
Search the HA community forums. If people are complaining about “cloud dependency” or “API changes breaking things,” walk away.
Check if the device requires an account to set up. If you can’t use the device without creating a vendor account and connecting to their cloud, that’s a red flag for long-term reliability.

Brands to avoid for local control:

Ring requires Amazon’s cloud for camera streams. No local streaming, no Frigate compatibility.
Chamberlain/MyQ actively blocks Home Assistant integration.
Arlo is cloud-dependent with short-lived API tokens.
Eufy has decent hardware but integration support is still limited.
Stock Tuya/Smart Life devices are cloud-dependent unless you flash custom firmware (which voids warranty and requires technical skill).

The graveyard of cloud devices:

Google bricked every Revolv smart home hub remotely in 2016
Belkin discontinued Wemo cloud services
Insteon’s cloud went offline overnight in 2022 when the company folded

The rule: if a device needs the manufacturer’s servers to function, it will eventually stop working or get worse. Local control isn’t a luxury. It’s insurance.

Devices that work when the internet dies

What to buy first

Don’t buy everything at once. This is the number one mistake beginners make. Start with one room, one use case, and learn how HA works before scaling.

The starter kit (~$50–$80 on top of your controller)

A Zigbee coordinator such as Connect ZBT-1 or Sonoff Dongle Plus (~$20-$30).
2-3 smart plugs like the ThirdReality Zigbee 4-pack (~$39) or Shelly Plus Plug. Smart plugs are the gateway drug of home automation. They also act as Zigbee mesh routers, which strengthens your network.
1 motion sensor such as the Aqara P1 Motion Sensor (~$15). This enables the quintessential first automation: “motion detected after sunset, turn on the lamp.”
1 door/window contact sensor from Aqara or ThirdReality (~$10-$12). Enables “front door opened, send notification” and security-style automations.

That’s enough to learn the basics: pairing devices, creating automations, understanding triggers and conditions, building a Zigbee mesh.

The second wave (when you’re comfortable)

Temperature and humidity sensors for climate automations and monitoring
Smart switches or in-wall relays like Lutron Caseta for bulletproof mainstream reliability, Shelly relays for behind-the-switch local control, or Zooz for Z-Wave
Smart bulbs such as IKEA TRADFRI bulbs, which are cheap and act as Zigbee routers. Philips Hue is excellent but expensive.
A smart lock once you trust your setup enough to put it on your front door

Your first automation

Start here: “When motion is detected in the living room AND it’s after sunset, turn on the lamp via smart plug.”

This teaches you triggers (motion sensor), conditions (time of day), and actions (turn on a device). Once you understand that pattern, every other automation is a variation.

The household acceptance test

A smart home that only works for the person who set it up is a failed smart home. The Home Assistant community calls this the “Home Approval Factor,” and Home Assistant’s own development roadmap explicitly prioritizes it.

Rules for a home that everyone can live with:

Physical switches must always work. If someone flips a light switch and nothing happens, your smart home has failed. Smart switches (Lutron Caseta, Shelly relays behind existing switches) beat smart bulbs for this reason. Nobody wants to be told “don’t use that switch.”
The best automations are invisible. Lights that turn on when you walk into a room. Climate that adjusts when you leave. A notification when the dishwasher finishes. Nobody needs to know HA is doing it.
Create simplified dashboards for family members. The full HA dashboard can be overwhelming. Make a simple view with just the controls they need.
Set up separate user accounts with the HA mobile app on each family member’s phone.
Automate something your partner cares about early. The coffee notification, the porch lights when they arrive home, the kids’ bedtime routine. Build goodwill before building complexity.
Expose devices to platforms they already use. If your household uses Alexa or Google for voice control, expose relevant HA entities there instead of forcing everyone to learn a new interface.
Never break the basics. If an automation fails, the fallback should be normal operation, not darkness or confusion.

Budget tiers

Budget: ~$200–$300

Home Assistant Green ($99)
Connect ZBT-1 coordinator ($30)
ThirdReality Zigbee plugs 4-pack ($39)
2x Aqara door/window sensors ($22)
2x Aqara motion sensors ($30)
A few IKEA TRADFRI bulbs ($30–$50)

Enough for one or two well-automated rooms.

Mid-range: ~$500–$1,000

Everything above, plus:

Upgrade to an N100 mini PC instead of the Green
Smart thermostat (Ecobee, ~$180–$250)
Shelly relays or Lutron Caseta switches for key rooms
More sensors throughout the house
A Nabu Casa Cloud subscription ($6.50/month) for easy remote access

Covers most of a typical home’s automation needs.

Premium: ~$2,000+

Everything above, plus:

PoE security cameras with Frigate NVR for local AI detection
Z-Wave coordinator and devices for critical infrastructure (locks, garage)
Motorized blinds
Whole-house smart switches
UPS for your HA server
Local voice assistants (Wyoming Satellite project)

Mistakes that cost the most time and money

Buying too much at once

The number one mistake. You end up with 30 devices, three protocols you don’t understand, and a half-configured system that frustrates everyone. Start with 5 devices. Get them working perfectly. Then expand.

Not using a USB extension cable

Every Zigbee troubleshooting thread eventually arrives at “are you using a USB extension cable?” USB 3.0 ports generate interference on the 2.4 GHz band. A $5 USB extension cable solves most Zigbee stability complaints.

Choosing cloud-dependent devices

That cheap Tuya plug works great until the company changes their API, shuts down their cloud, or starts charging for features. Local control is not a luxury. It’s insurance.

Not naming devices properly

When everything is light.kitchen_2 and switch.plug_93719, managing automations becomes miserable. Name and organize from day one. Use rooms and areas in HA. Future you will be grateful.

Ignoring backups

HA’s backup system is good now. Configure automated backups before you have 50 devices and a year of automation work to lose.

Choosing the wrong Zigbee integration

ZHA and Zigbee2MQTT each have tradeoffs, and switching later means re-pairing every device on your network. Research this choice before you pair your first sensor.

Brands to approach with caution

These brands have known friction with Home Assistant:

Ring requires Amazon’s cloud for camera streams. No local streaming, no Frigate compatibility.
Chamberlain/MyQ actively blocks Home Assistant integration.
Arlo is cloud-dependent with short-lived API tokens.
Eufy has decent hardware but integration support is still limited.

Check the HA integrations page for any device before buying.