Home Assistant

Local-first home automation, honestly reviewed. No marketing fluff — just what you get when 85,000 GitHub stars and a non-profit backing meet your living room.

---

TL;DR

• What it is: Open-source (Apache-2.0) home automation platform that connects thousands of smart devices and keeps all the data on your own hardware — not a corporate cloud [README][website].
• Who it’s for: Technical homeowners and self-hosters who want control over their smart home infrastructure, and founders tired of watching their smart home stop working every time the internet goes down [1][3].
• Cost savings: Comparable commercial platforms (Homey Self-Hosted Server) cost $5/mo or $150 lifetime. Home Assistant self-hosted costs nothing except hardware — a Raspberry Pi you may already own, or the $99 Home Assistant Green [5][website].
• Key strength: 3,400+ integrations, runs locally with no cloud dependency, non-profit governance so it can’t be sold or shut down overnight [website].
• Key weakness: Complex enough to alienate non-technical household members. The “significant other approval rate” is a real concern that experienced users track as a formal metric [3][4].

---

What is Home Assistant

Home Assistant is a local-first home automation platform. You install it on a Raspberry Pi, a mini PC, a NAS, or dedicated hardware, and it becomes the brain of your smart home — connecting everything from Philips Hue bulbs to HVAC systems, door locks, energy monitors, cameras, and voice assistants, all under one interface that doesn’t require an internet connection to function.

The project lives at 85,407 GitHub stars as of this review, under Apache-2.0 license, which means no “fair-code” ambiguity — you can use it, fork it, embed it, without calling a lawyer [README]. It’s developed under the Open Home Foundation, a non-profit organization. The website is explicit about what that means: “We are a non-profit and can’t be sold or acquired.” That’s a rare and meaningful promise in a category where cloud platforms have a long history of acquisition-driven shutdowns and pricing pivots.

The platform ships in multiple forms. The recommended installation is Home Assistant OS (HAOS), a full operating system image you flash to hardware [4]. If you want purpose-built hardware, the Home Assistant Green is a $99 plug-and-play hub that reviewers describe as the easiest entry point [3]. The Home Assistant Yellow adds Matter support and hardware expandability for more serious setups [website]. Remote access is handled optionally through Nabu Casa, a $6.50/mo cloud subscription that provides secure remote tunneling, voice assistant connections, and helps fund development [2].

The pitch, stripped of marketing language: your smart home runs on your hardware, responds instantly because it’s local, keeps working when your internet dies, and the vendor cannot turn it off.

---

Why people choose it

The through-line across every review and community thread is the same two complaints about commercial smart home platforms:

1. Cloud dependency kills reliability. One XDA reviewer describes exactly why he rebuilt his entire home setup around Home Assistant: “My biggest issue with the cloud has always been that it doesn’t work when my Internet goes out. That’s less annoying when it’s backups of local storage, but when my smart home doesn’t work, my voice assistants won’t reply, and other services I consider essential are unreachable, it makes me angry.” [1] He now runs Home Assistant with local LLM voice control so that Alexa-style commands work without touching the internet.

2. Corporate risk. The How-To Geek reviewer [3] started on Samsung SmartThings, moved to Home Assistant for the right reasons, but ended up swapping back — not because HA was bad, but because the complexity introduced household friction. His original motivation for leaving SmartThings holds though: “from the beginning, I haven’t been fully comfortable with having our smart home dependent on an internet-connected service controlled by a corporation.” This is the recurring theme: Home Assistant exists because every major commercial smart home platform is a single acquisition away from sunset.

On the Nabu Casa question. A long community thread [2] debates the security tradeoff between Nabu Casa and pure self-hosting. The practical consensus: Nabu Casa is a transparent, trustworthy relay service that funds the project, handles SSL properly, and limits access to Home Assistant pages only. For non-DevOps users who would otherwise port-forward port 8123 to the internet without SSL — which multiple community members call out as genuinely dangerous — Nabu Casa is the safer option [2]. The key point: Home Assistant runs on your hardware either way; Nabu Casa is just the remote access tunnel, not the platform itself.

---

Features

Core automation engine:

• Visual automation editor plus YAML for power users [website]
• Trigger types: time, device state, sun position, presence detection, webhooks, calendar events
• Conditions, actions, scripts, scenes — full workflow logic [website]
• Blueprints: shareable, parameterizable automations the community publishes and reuses
• 3,400+ integrations covering devices and services [website]
• Automatic network scanning to discover supported devices on first setup

Voice and AI:

• Assist: the built-in voice assistant, runs fully locally on affordable hardware, supports wake words [website]
• Alexa and Google Assistant integration for households already bought into those ecosystems [website]
• Local LLM integration (via Ollama or similar) for natural language device control — one reviewer runs this so voice commands work offline [1]
• HA does not ship an LLM; you connect one yourself

Dashboard and monitoring:

• Fully customizable dashboards with drag-and-drop card builder [website]
• Mobile companion apps (iOS/Android) — location data sent directly to your instance, not through a third party [website]
• Home Energy Management: solar production tracking, consumption monitoring, cost optimization [website]
• Home Assistant Cast: push any dashboard to a TV screen
• NFC tag support for physical triggers

Hardware ecosystem:

• Home Assistant Green: $99 plug-and-play hub [website]
• Home Assistant Yellow: Matter-ready, upgradeable, more I/O [website]
• Connect ZBT-2: Zigbee and Thread USB dongle [website]
• Connect ZWA-2: Z-Wave USB dongle [website]
• Voice Preview Edition: dedicated hardware for local voice [website]

Protocol support:

• Zigbee, Z-Wave, Matter, Thread, Wi-Fi, Bluetooth LE, and more via USB dongles or dedicated hubs
• Matter multi-admin: a single device can be simultaneously managed by Home Assistant and another platform (SmartThings, Apple Home) [3]

Add-ons (apps):

• AdGuard Home (ad-blocking DNS)
• Node-RED (alternative automation engine)
• Spotify Connect target
• Many more installable through the add-on store [website]

---

Pricing: SaaS vs self-hosted math

Home Assistant self-hosted:

• Software: $0 (Apache-2.0) [README]
• Hardware options:
  • Raspberry Pi 4 (you may own one): ~$0 additional
  • Home Assistant Green: $99 one-time [website]
  • Home Assistant Yellow: ~$149–$199 one-time [website]
  • Any old mini PC or NAS you already run
• Nabu Casa (optional remote access): $6.50/month or $65/year

Commercial alternatives for comparison:

• SmartThings: Free app, but Samsung Cloud-dependent — hardware is cheap, lock-in risk is real
• Homey Self-Hosted Server: $5/month or $150 lifetime license, closed-source [5]
• Homey Pro hub: $399 hardware + free cloud
• Hubitat: ~$149 hub, local processing, no subscription — the closest pure competitor
• Wink Hub 2: cautionary tale — discontinued, cloud shut down in 2023, all devices bricked

Concrete savings over 3 years:

Option	Year 1	Year 2–3	3-Year Total
Home Assistant (own hardware)	$0	$0	$0
Home Assistant Green + Nabu Casa	$99 + $65	$65/yr	~$229
Homey Self-Hosted Server (sub)	$60	$60/yr	$180
Homey Self-Hosted Server (lifetime)	$150	$0	$150
Hubitat	$149	$0	$149

The math straightforwardly favors Home Assistant if you have any existing hardware. Even the Green + Nabu Casa combination at ~$229 over three years is the cheapest full-featured option with remote access included [website][5].

What the table doesn’t show: Home Assistant’s 3,400+ integrations versus Homey’s ~50,000 device count from 1,000+ brands [5][website]. Those numbers aren’t directly comparable — HA integrations include services and APIs, not just physical devices. But the breadth is real.

---

Deployment reality check

The beginner path is cleaner than it used to be. HAOS flashed to a Raspberry Pi or a Home Assistant Green gets you a working instance in under an hour if you’re comfortable with basic networking [4]. The community thread on “20 things I wish I knew” [4] is a good calibration for what’s actually required.

What can go sideways:

The “significant other approval” problem is real. The How-To Geek reviewer [3] documents this honestly and at length: he bought the Home Assistant Green, praised it, then switched back to SmartThings because his wife already knew SmartThings and the Matter multi-admin setup introduced confusion about which platform was “primary.” His conclusion: “Something complex or unreliable is the last thing I want to introduce, and unfortunately, Home Assistant can be both of these things.” This isn’t a knock on the software’s quality — it’s an acknowledgment that Home Assistant is a power user’s tool that requires one person to be the household’s de-facto sysadmin.

Community veterans recommend keeping physical fallbacks. The 20-things post [4] is emphatic: “Keep a physical button (or way of doing whatever you’re automating). This way, if your HA is down or malfunctioning, they don’t feel trapped.” This is real-world experience from someone running 88 automations for 7 years — hardware fails, updates break things, and your household should be able to turn the lights on regardless.

Add-on sprawl. The same poster warns about HACS (Home Assistant Community Store): “When I first entered HACS, I was like a toddler in a candy store and started to install everything. Next thing you know, 20 javascripts were loading and crushed my mobile APP.” [4] The ecosystem is rich and the temptation to install everything is real. Discipline matters.

Protocol choice has long-term consequences. The community strongly leans Z-Wave for reliability and standards compliance, with Zigbee for lighting where Z-Wave coverage is thin [4]. Wi-Fi-based devices work but need proper VLAN isolation from your main network. These decisions are made early and expensive to undo.

Local LLM voice control is possible but not automatic. One XDA reviewer [1] successfully integrated a local LLM for natural language device control and calls it fantastic — but notes it “needs to be on a faster computer, otherwise the responses can be slow.” You’re setting up Ollama separately; Home Assistant doesn’t ship it.

The “what happens if something happens to me” question. The How-To Geek reviewer [3] raises this: if you’re the only person who understands the setup and something happens to you, your family is left with a house full of devices controlled by software they don’t understand. This is the honest edge case that smart home enthusiasts rarely discuss publicly.

---

Pros and Cons

Pros

• Non-profit governance. The Open Home Foundation structure means no acquisition risk, no pricing pivot, no sunsetting on a CEO’s whim [website]. This is the single most underrated thing about Home Assistant relative to every commercial competitor.
• Apache-2.0 license. Clean open source — no fair-code restrictions, no commercial-use caveats [README]. You can embed it, fork it, build a product on it.
• True local operation. Runs without internet. Smart home keeps working during outages, which is exactly when you want your lights and locks to work [1][website].
• 3,400+ integrations. Broadest integration catalog in the self-hosted smart home category by a significant margin [website].
• Local LLM voice control. The combination of Assist + local LLM + Matterbridge for Alexa compatibility described in [1] is genuinely impressive — full voice control, zero cloud dependency.
• Matter and Thread support. Future-proof protocol support through dedicated USB dongles [website].
• Energy management. Solar production tracking, consumption visualization, and cost optimization built in — not an add-on [website].
• Active development. Monthly releases with changelogs, 85,000+ GitHub stars, top open-source project by contributors in 2025 [website].
• Hardware ecosystem. Purpose-built devices (Green, Yellow, Voice) for people who don’t want to manage hardware themselves [website].

Cons

• Steep for non-technical users. The learning curve is real. Protocol choices (Z-Wave vs Zigbee vs Matter), YAML automations, add-on management — this is a sysadmin hobby that happens to live in your house [3][4].
• Household friction risk. If others live in your home and weren’t consulted, Home Assistant can become a source of domestic conflict rather than convenience [3][4]. This is documented, not hypothetical.
• Maintenance burden. Monthly updates, occasional breaking changes, add-ons that stop working — you are the support team [3][4].
• No LLM included. Local AI voice control requires separately deploying Ollama on hardware fast enough to respond in reasonable time [1].
• Matter multi-admin is confusing. Running HA alongside another platform via Matter’s multi-admin feature creates management complexity that even technical users find hard to explain to household members [3].
• HACS can destabilize installs. Third-party integrations from the community store vary wildly in quality and update frequency [4].
• The “what if you’re unavailable” problem. If you’re the only person who understands the infrastructure, your household is one accident away from a house full of smart devices nobody can control [3].

---

Who should use this / who shouldn’t

Use Home Assistant if:

• You have at least basic technical comfort — you’ve used Docker, configured a router, or used a Linux terminal at least once.
• Everyone in your household is either onboard with the learning curve or content letting you manage it.
• You have strong opinions about cloud lock-in and data sovereignty — your smart home data should live on your hardware.
• You want the broadest possible integration support for unusual or legacy devices.
• You want to connect a local LLM for voice control that works offline.
• You’re a founder or technical operator who finds the $65/year Nabu Casa subscription a worthwhile tradeoff for remote access without building your own VPN.

Use Home Assistant Green specifically if:

• You want HA but don’t want to manage hardware — $99 for a plug-and-play hub that boots straight into HAOS.

Skip it (try Hubitat) if:

• You want local processing and no cloud dependency but Home Assistant’s complexity is too much. Hubitat is simpler, less powerful, and purpose-built for non-hobbyists.

Skip it (stay on SmartThings/Apple Home) if:

• You have non-technical household members who use the existing platform and are happy. Don’t fix what isn’t broken for others.
• You want a smart home that works without a household sysadmin. Home Assistant requires one.

Skip it (use Homey Self-Hosted Server) if:

• You want something closer to a polished commercial experience (Homey’s UI is significantly more consumer-friendly) and are willing to pay $5/mo or $150 lifetime for closed-source software [5]. The tradeoff is a smaller integration catalog and no open-source guarantee.

---

Alternatives worth considering

• Hubitat — local processing, no subscription, simpler than HA, narrower integrations. The honest “I want local control without the complexity” option.
• Homey Pro / Homey Self-Hosted Server — consumer-friendly UI, supports 50,000+ devices, closed-source, $5/mo for the self-hosted software [5]. Direct HA competitor now that Homey has a self-hosted tier.
• Node-RED — not a standalone platform but pairs with HA for more powerful automation logic. Many advanced HA users replace HA’s native automation engine with Node-RED [4][website].
• SmartThings — Samsung’s free platform, large device support, cloud-dependent. Fine until Samsung loses interest.
• Apple Home / HomeKit — tight ecosystem, works well on Apple hardware, extremely limited compared to HA’s integration breadth.
• openHAB — older, Java-based open-source alternative. Less active development, less polished UI than HA, but different architecture some prefer.
• Domoticz — lightweight, runs on very low-power hardware, older codebase. For specific hardware-constrained deployments.

---

Bottom line

Home Assistant is the most serious open-source smart home platform that exists, and it’s not close. 85,000 GitHub stars, non-profit governance that can’t be acquired, Apache-2.0 license, 3,400+ integrations, true local operation — no commercial alternative checks all of those boxes. The XDA reviewer who built his entire home cloud around it describes the result as working “whether they know it’s being used or not” [1]. That’s the goal.

The honest caveat comes from the How-To Geek reviewer who bought the Green, loved it, and then returned to SmartThings [3]. Not because Home Assistant is bad — because his household isn’t just him. Home Assistant asks you to be the sysadmin of your own home, and that’s a real commitment. If you live alone, or your household is fully onboard, the setup time pays off immediately. If you’re introducing complexity into a home where others depend on the lights just working, think carefully before replacing something that already works.

For the target reader of this site — a technical founder or self-hoster who wants to stop paying cloud subscriptions for devices they already own — Home Assistant running on a Raspberry Pi or a $99 Green is the obvious answer. The non-profit foundation, the open license, and the 3,400-integration catalog make it the only defensible long-term choice in this category. The monthly maintenance overhead is real, but so is the freedom.

---

Sources

1. Joe Rice-Jones, XDA Developers — “How I linked my NAS, Home Assistant, and self-hosted AI tools into a single ‘home cloud’” (Nov 9, 2025). https://www.xda-developers.com/linked-nas-home-assistant-self-hosted-ai-home-cloud/

2. Home Assistant Community Forum — “Nabu Casa va self host” (thread, Jun 2022). https://community.home-assistant.io/t/nabu-casa-va-self-host/435645

3. Bertel King, How-To Geek — “Self-hosting isn’t always the answer—why Home Assistant is no longer powering my home” (Feb 23, 2026). https://www.howtogeek.com/self-hosting-isnt-always-the-answer-why-home-assistant-is-no-longer-powering-my-home/

4. kameo4242, Home Assistant Community Forum — “20 things I wished I knew when I started with Home Assistant” (May 2023, updated Apr 2025). https://community.home-assistant.io/t/20-things-i-wished-i-knew-when-i-started-with-home-assistant/576359

5. Currently / Yahoo (original: The Verge / Engadget) — “Homey takes on Home Assistant with self-hosted server software”. https://currently.att.yahoo.com/att/homey-takes-home-assistant-self-150015912.html

Primary sources:

• GitHub repository: https://github.com/home-assistant/core (85,407 stars, Apache-2.0 license)
• Official website: https://www.home-assistant.io
• Open Home Foundation: https://www.openhomefoundation.org