Home Assistant, honestly: what you get and what you take on

The only platform where the cloud is optional, and the only one where you are the administrator.

The mental model#

Home Assistant is not a hub. It is software that turns a small computer into a controller, and it treats every protocol as a plug-in. Zigbee, Z-Wave, Thread, Bluetooth, Wi-Fi devices, cloud APIs and your printer all become entities in one state machine, and automations act on that state machine rather than on any vendor's app.

That design explains both the strength and the cost. The strength is that a Z-Wave lock, a Zigbee button and a Matter light are the same kind of object to an automation, so you can write a rule that no ecosystem app would let you write. The cost is that the abstraction has to be assembled. Nothing arrives pre-integrated, and updates land monthly.

Hardware: the part people get wrong#

The single most common budgeting error is assuming the box includes the radios. It does not.

PiecePrice (US, Sept 2026)What it gives you
Home Assistant Green$199The computer and the operating system. Ethernet and Wi-Fi. No Zigbee, no Thread, no Z-Wave, no Bluetooth radio.
Home Assistant Connect ZBT-2$49Zigbee or Thread. One at a time, not both.
Home Assistant Connect ZWA-2$69Z-Wave 800 series, including Z-Wave Long Range.
BluetoothVariesA USB adapter, or ESPHome Bluetooth proxies scattered around the house.
Infrared and 433 MHzVariesESPHome devices you build or buy.

Green went from $99 to $199 in 2026, with the vendor citing memory costs, so it is no longer the cheap on-ramp it was. Home Assistant Yellow is discontinued (production ended 15 October 2025) and Connect ZBT-1 production has also ended, though existing ZBT-1 units remain supported.

USB 3.0 ports emit broadband noise across 2.4 GHz. Nabu Casa ships a 1.5 meter USB extension cable with the ZBT-2 specifically so you can move the radio away from the host. Use it. It is the cheapest reliability upgrade in the box.

Running Home Assistant on your own mini PC or a virtual machine is entirely normal and often cheaper, but you then own the backup strategy and the USB passthrough problems yourself.

Matter: ahead of the spec, behind the certificate#

Home Assistant adopts Matter faster than any other consumer platform, and the version story has a wrinkle worth understanding.

Matter Server 9.0, released 23 June 2026, moved the controller off the C++ SDK onto a matter.js implementation and brought Matter 1.5.1. Matter Server 9.1.0, released 17 July 2026, added Matter 1.6.0 along with device time sync and better Thread diagnostics. That put Home Assistant on the current specification within a month of the Matter 1.6 release, at a point when the mainstream ecosystems were still working through 1.3 to 1.5 device types.

The wrinkle: that new implementation has not been re-certified by the Connectivity Standards Alliance. Certification-based comparisons therefore still list Home Assistant at an older Matter version, and both statements are true at the same time. In practice you get the newer behavior; on paper you do not get the newer badge.

Joint Fabric, the Matter 1.6 feature that lets several controllers co-administer one fabric, has no shipping user-facing implementation on any consumer platform as of September 2026. Sharing devices still means multi-admin, one fabric per controller.

Thread#

Home Assistant runs the OpenThread Border Router add-on on Yellow, Connect ZBT-1 or Connect ZBT-2. OTBR 1.4 left beta in Home Assistant 2026.6 (3 June 2026), and that release replaced the previous mDNS responder with OpenThread's own mDNS handling, which fixed a long-running class of Thread discovery failures on certain home routers.

That matters because most Thread problems are not radio problems. They are multicast problems on your LAN, which is the argument made in full in Thread troubleshooting. Home Assistant also exposes far more Thread diagnostics than Apple, Google or Amazon do, including which nodes are acting as routers, so it is the easiest platform on which to actually diagnose a split Thread network.

The directory of what else can act as a border router is in Thread border routers.

Local control, scored#

The Local Control Index, September 2026. Each platform is scored on eight criteria worth 100 points: full points where the vendor documents the behavior, half where it works with a documented caveat, zero where the cloud is required. Method at /methodology/.
PlatformScore /100Local automation executionLocal voice controlSurvives a vendor shutdown
Home Assistant10020 / 2010 / 1015 / 15
Hubitat Elevation87.520 / 200 / 1015 / 15
Homey Pro62.520 / 200 / 107.5 / 15
Apple Home6020 / 200 / 107.5 / 15
Samsung SmartThings3010 / 200 / 100 / 15
Google Home150 / 200 / 100 / 15
Amazon Alexa50 / 200 / 100 / 15

Home Assistant is the reference implementation of the rubric rather than a strong performer within it. Automations execute on your box. State is stored on your box. There is a local voice pipeline, so "turn off the kitchen lights" can be processed without leaving the house, which no other platform on this list offers. If the company behind it disappeared tomorrow, your installation would keep running.

Home Assistant Cloud costs $6.50 a month and buys remote access without opening ports, bridging into Alexa and Google, cloud speech services and backups. It is optional in the literal sense: turn it off and the house still works. Most other platforms fail that test, and the ones that pass do so only partly.

The learning curve, described accurately#

The interface is no longer the barrier it was. Dashboards build themselves, most integrations are added through the UI, and Z-Wave lock PIN management moved into the UI in the 2026.6 release. The 2026.9 release added a Matter network map visualization, which is the kind of diagnostic tooling no other platform ships.

The real cost is different, and it is ongoing:

The clearest current example of that last risk: Samsung is ending free SmartThings API access in October 2026, moving individual developers to a $4.99 a month Personal Plan. Home Assistant's SmartThings integration falls under that plan, and as of September 2026 Home Assistant has not said how it will handle it. If you were planning to use Home Assistant as the brain and SmartThings as the radio layer, treat that arrangement as unsettled until it is resolved. The full comparison is in Home Assistant vs SmartThings.

Who should buy it, and who should not#

Buy it if you have devices on three or more protocols, you want automations that keep running during an outage, you care about not being switched off by a vendor decision, or you have already hit the automation ceiling in an ecosystem app.

Do not buy it if the honest answer to "who fixes this when it breaks at 11pm" is nobody. A household where one person maintains Home Assistant and everyone else depends on it is a household with a single point of failure that takes vacations. Hubitat gives you local execution with far less maintenance culture, and the mainstream platforms in the seven platforms compared ask nothing of you at all.

A middle path works well: keep Home Assistant as the automation engine and expose a curated set of devices to a voice assistant, which is exactly the pattern described in running two platforms on purpose.

What changes next#

Three things to watch through late 2026. Whether the matter.js implementation gets re-certified, which would close the paper gap. How the SmartThings API change is handled. And whether Joint Fabric appears anywhere user-facing, since Home Assistant is the most likely platform to ship it first.

Do I need Home Assistant Green, or can I use a Raspberry Pi?

Either works. Green is a supported appliance with the operating system pre-installed at $199, and it is the low-effort option. A Raspberry Pi or a small x86 mini PC is often cheaper and faster, and running Home Assistant OS on it gives you the same add-on system. Remember that neither includes radios, so add a ZBT-2 for Zigbee or Thread and a ZWA-2 for Z-Wave.

Can Home Assistant do Zigbee and Thread at the same time?

Yes, but not on one Connect ZBT-2. The dongle runs either a Zigbee coordinator or a Thread border router, so running both means two dongles at $49 each. Put them on different 802.15.4 channels and physically separate them, because they share the same 2.4 GHz band.

Does Home Assistant work without the internet?

Yes, more completely than any other platform. Automations, dashboards on the LAN, local voice, Zigbee, Z-Wave and Thread all keep working. What stops is remote access from outside the house, any integration that talks to a vendor cloud, and cloud speech if you use it. See what still works when the internet goes down.

Is Home Assistant really on Matter 1.6 when comparison charts say otherwise?

Both are accurate. Matter Server 9.1.0 added Matter 1.6.0 in July 2026, so the shipping code implements the current specification. The implementation has not been re-certified by the alliance, so certification-based lists still show an older version. Judge it on behavior if you care about features and on the certificate if you care about compliance.

Will the SmartThings API change break my Home Assistant setup?

It might change what it costs. Samsung ends free SmartThings API access in October 2026 and moves individual developers onto a paid Personal Plan at $4.99 a month, and Home Assistant's integration falls under that plan. Home Assistant has not published its approach as of September 2026. Devices connected directly to Home Assistant by Zigbee, Z-Wave, Thread or Matter are unaffected.

How much does Home Assistant actually cost to run?

The software is free. A realistic first build is $199 for a Green plus $49 for a ZBT-2, or about $270 with a Z-Wave stick as well. Home Assistant Cloud is $6.50 a month if you want remote access without configuring it yourself. There is no per-device fee and no feature paywall.

Is Home Assistant better than Hubitat?

They solve the same problem with different amounts of your time. Hubitat is an appliance: rules run locally, the interface is dated, and you rarely touch it. Home Assistant is a platform: more integrations, better diagnostics, local voice, and more maintenance. Both score high on local control. Pick by how much administration you want, not by feature count.

Can I use Home Assistant just as a bridge to Apple Home?

Yes. Home Assistant can expose its entities to Apple Home, and it is a common way to get Zigbee and Z-Wave devices into an ecosystem that has neither radio. Expect the usual Matter bridge losses in fidelity, and note that anything exposed this way still depends on Home Assistant staying up.

Primary sources

Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.