Home Assistant 101: The Local Hub, Explained

Prices in this article are typical U.S. retail, checked October 2026.

Section 1: What does it mean to own your hub? (Introduction)

Home Assistant is a local hub you own: software that runs on your hardware, talks to devices over your network, and keeps automations working without a vendor cloud. The trade-off is setup time, updates and the occasional breaking change to fix.

Most smart homes run on someone else’s computer. The app talks to a server, the server talks to the device, and the automation happens somewhere you have never seen. Home Assistant flips that: the automation runs on a small box in your house, on software you own, and the vendor’s cloud becomes optional.

That is the appeal, and it is a real one. When the internet drops, the lights still respond to the button. When a manufacturer discontinues a product line, the device usually keeps working. When you want a rule that spans brands — a Hue bulb, an Aqara sensor, a Shelly relay, and a thermostat from a fourth company — Home Assistant is the place where they can all be in the same automation.

A concrete example: the hallway light turns on when the Aqara door sensor opens after sunset, but only if the Hue bulb is not already on, and it sends a notification to a phone that is not home. Four brands, one rule, no cloud in the path. The cost is not the hardware. It is the time. Home Assistant is a platform, not a product: it asks you to install it, update it, back it up, and occasionally read a log. This guide covers what it is, what hardware to run it on, what it costs in money and hours, and the honest line between a weekend project and a second job. For the wider picture, start with the Foundations hub.

Section 2: What is Home Assistant?

Home Assistant is open-source home automation software, and it speaks the standards covered in Matter and Thread 101. It runs on your own hardware, connects to devices through integrations, and gives you one interface for automations, dashboards, and voice.

The official description is short: open-source home automation that “puts local control and privacy first,” with more than 1,500 integrations. It is developed by the Open Home Foundation, a non-profit, which matters for the longevity argument: the software is not a product line that can be discontinued.

How it differs from a vendor hub

A vendor hub — SmartThings, a Hue Bridge, an Aqara hub — is a product with a support line, an app, and a roadmap. Home Assistant is a platform with a community, a release cycle, and no one to call. The vendor hub is easier; Home Assistant is more capable. The two can coexist: Home Assistant can control the vendor hub through an integration and expose its devices alongside everything else. Those integrations are the point. A single automation can read a Zigbee sensor, a Wi-Fi plug, a cloud thermostat, and a phone’s location, and act on all of them without caring who made them.

The parts

• Integrations connect devices and services. Some are local (Zigbee, Z-Wave, Thread, Matter), some are cloud (a thermostat’s API), and some are both.
• Automations are the rules: trigger, condition, action. They run on the box, not in a vendor’s cloud.
• Dashboards are the interface: a wall tablet, a phone page, or a browser tab.
• Add-ons are extra services — a backup tool, a database, a local voice assistant — that run alongside Home Assistant.
• Voice can be local or cloud, depending on the assistant you attach. A fully local voice assistant can run on the same box, though it is a project of its own.

What it is not

• A device brand. Home Assistant does not make bulbs. It coordinates the ones you own.
• A replacement for every app. Some devices only work through their vendor’s cloud, and the integration inherits that limitation.
• A supported product with a phone line. The community forum is excellent, and there is no one to call at 2 a.m.
• A zero-maintenance appliance. Updates, backups, and the occasional breaking change are part of the deal.

Section 3: What hardware do you need to run it?

Home Assistant runs on almost anything: a Raspberry Pi, a mini PC, a virtual machine, or a purpose-built box. The right choice depends on how much you want to tinker.

The official route: Green

Home Assistant Green is the easiest starting point. It is a small, fanless box with the software preinstalled, sold by the project, and it is silent and low-power enough to live in a hallway closet, priced at $199 MSRP, and it comes with the software preinstalled. You plug it into power and Ethernet, open a browser, and follow the setup. It is the option to recommend to someone who wants Home Assistant without building a server.

Green has no Zigbee or Thread radio built in. For those devices you add a USB radio — the Connect ZBT-2 at $49 MSRP handles both Zigbee and Thread, and it is also the path to Matter-over-Thread devices.

The tinkerer route: Pi or mini PC

A Raspberry Pi with an SSD is cheaper and more flexible, but you supply the storage, the power supply, and the patience. A used mini PC is more powerful and better for a large install with cameras or a local voice assistant. Both run the same software.

The other hardware routes

A Raspberry Pi 4 or 5 with an SSD is the classic budget build: cheaper than Green, more work to assemble, and fine for a modest install. A used mini PC is the better choice for a large house, a local voice assistant, or a camera pipeline; it has more CPU and storage headroom. A virtual machine on an existing server works if you already run one and understand the backup story.

What you actually need

• The box: Green at $199, or a Pi/mini PC you already own.
• Storage: an SSD for anything beyond a toy install. SD cards fail.
• Network: Ethernet is strongly preferred; Wi-Fi works but adds a failure point.
• Radios: a ZBT-2 at $49 if you have Zigbee or Thread devices.
• A backup target: a USB drive, a NAS, or the paid cloud backup.
• A Z-Wave radio if you have Z-Wave devices; the ZBT-2 covers Zigbee and Thread only.

Do not run it on an SD card. The database writes constantly, and cards fail; an SSD is the difference between a hobby and a repair project.

A realistic first order is Green plus a ZBT-2: about $250 before storage or subscription.

Section 4: What will it cost you in money and time?

The money is predictable; the time is not. Neither is the subscription: the box works without it, and many people never pay.

Money

• Hardware: $199 for Green, $49 for the radio, plus an SSD or a Pi if you go the other route.
• Subscription: Nabu Casa’s Link service (formerly Home Assistant Cloud) is optional. It adds remote access, offsite backups, and voice processing, with a free trial and regional pricing; the European price shown is €7.50 a month or €75 a year. You can run Home Assistant without it, using your own VPN or a reverse proxy.
• Devices: the same devices you would buy anyway. The hub does not make them cheaper.

Time

Budget a weekend for the first setup and an evening a month after that. The weekend is install, integrations, names, one automation, one dashboard. The monthly evening is updates, a backup check, and the release notes. If a major version lands, add an hour.

The first weekend is setup: install, add integrations, name devices, build one automation, make one dashboard. The first month is discovery: you find the device that needs a template, the integration that needs a token, the automation that needs a condition you did not know existed.

After that, it is maintenance. Updates arrive monthly; most are uneventful, some change a service call or a YAML key. Backups matter. A broken update without a backup is a bad evening.

The honest comparison: a cloud ecosystem asks for money and gives you a supported product. Home Assistant asks for time and gives you control. Neither is free.

Section 5: What does it do better, and what does it do worse?

Better

• Cross-brand automation. A single rule can use a Hue bulb, an Aqara sensor, a Shelly relay, and a cloud thermostat. No other consumer platform does this as openly.
• Local control. Automations run on the box. With local devices, the internet can go down and the house still works.
• Dashboards. You can build the interface you want, on a wall tablet or a phone, instead of accepting the vendor’s layout.
• Templates and add-ons. A template can turn a raw sensor value into something useful; an add-on can run a local database, a backup service, or a voice assistant on the same box.
• Energy and history. The built-in energy dashboard and long-term statistics are more detailed than most vendor apps.
• Data ownership. The history database is yours. You decide what leaves the house.
• Longevity. A device that still speaks its protocol usually keeps working, even if the vendor’s app disappears.

Worse

• Setup. There is no onboarding wizard for the whole house; you add integrations one at a time.
• YAML and templates. The visual editor covers a lot, but advanced rules still drop into code.
• Breaking changes. Updates occasionally rename a service or change a behavior. Read the release notes.
• No support line. The community forum is fast and generous; it is not a warranty, and the answer may be a link to a release note.
• Decision fatigue. Every choice is yours: hardware, database, backup, remote access, voice. That is the feature and the tax.
• Security is yours too. Remote access, accounts, and updates are your responsibility. The network security guide is not optional reading if you expose the box.

Section 6: How do you start in three steps? (Conclusion)

1. Start with Green and one integration. Plug it in, add the devices you already own, and build one automation that runs locally. Do not migrate the whole house on day one.
2. Add a radio only if you need it. The ZBT-2 at $49 covers Zigbee and Thread. If all your devices are Wi-Fi or Matter-over-Wi-Fi, skip it.
3. Set up backups before you customize. A USB drive or the subscription, scheduled and tested. Then build the dashboard and the second automation.

Set a backup schedule and test a restore before you invest a weekend in dashboards. The first restore is the one that teaches you whether the backup works.

Try one local automation first: a button that turns on a lamp through the hub with the internet unplugged. If that works, the platform is doing the thing you bought it for. Some homes should skip Home Assistant. If you have a dozen devices from one ecosystem and the app does what you need, the local hub buys complexity you will not use. If you rent and cannot leave a box running, or you want a product with a support number, a mainstream hub is the better fit. And if the idea of reading release notes makes you tired, believe that feeling.

Home Assistant is the most capable option in the category, and capability is a cost. The right question is not “is it better?” but “do I want to run this?” If the answer is yes, it is the last hub you will buy. If it is no, that is a valid answer too.

Where to buy

Related reading

• Matter and Thread 101 — the standards the hub speaks.
• The Smart Hub Blueprint — where the hub sits and why.
• Automation Fail-Safes — the outage case for local control.
• Choosing a Smart Home Ecosystem — the platform decision underneath.

Sources

• Home Assistant — Open Home Foundation, open-source, local control and 1,500+ integrations checked October 2026
• Home Assistant Green — Home Assistant, $199 MSRP and preinstalled setup checked October 2026
• Connect ZBT-2 — Home Assistant, $49 MSRP and Zigbee/Thread radio checked October 2026
• Home Assistant Link — Nabu Casa, subscription benefits, free trial and regional pricing checked October 2026