Home Assistant vs Apple HomeKit vs Google Home: An Installer's Comparison (Australia 2026)

The three-second summary: what each platform actually IS

Home Assistant is an open-source, local-first automation hub. It runs on a small computer in your house — a Home Assistant Green appliance, a Yellow board, or any decent mini-PC — and talks directly to devices over Zigbee, Z-Wave, Thread, Wi-Fi and Matter. No monthly fee, no required cloud account, code on GitHub, governed by the non-profit Open Home Foundation. If the company behind it disappeared tomorrow, your house keeps running.

Apple HomeKit (now mostly branded Apple Home) is Apple's tightly-controlled smart-home framework. Devices must pass Apple certification, automations live in the Home app on iOS, and the hub role is filled by an Apple TV 4K, HomePod or HomePod Mini. The trade-off is straightforward: Apple decides what is allowed and you get a polished, privacy-respecting result inside those limits. Apple Home does not run on Android.

Google Home is the consumer-facing front for Google's Nest hardware and assistant ecosystem. Setup happens in the Google Home app, voice runs through Nest Mini, Nest Hub, Nest Hub Max or Pixel devices, and routines execute on Google's cloud. The strength is search-quality voice and tight Chromecast and YouTube integration. The weakness is that Google owns the relationship — devices, accounts, and the cloud paths the whole thing depends on.

Side-by-side capability matrix

The marketing materials for all three platforms say the same words. Here is what those words mean in practice, in a Central Coast house, in 2026:

Capability	Home Assistant	Apple Home (HomeKit)	Google Home
Local-only operation	Full. Zigbee, Z-Wave, Matter-Thread and LAN devices run with WAN unplugged. Cloud only needed for remote access (optional Nabu Casa $9 AUD/month) or Alexa/Google voice bridges.	Mostly. Apple Home stores state locally on the home hub (Apple TV 4K or HomePod). Siri voice needs internet in most cases; basic device control survives short outages.	Limited. Local fulfilment exists for a small set of Nest, Cast and Matter devices; most routines require Google's cloud. NBN outage equals dead automations.
Automation depth	Unlimited. Triggers, conditions, choose blocks, scripts, Python sensors, AppDaemon, Node-RED, blueprints. Multi-condition logic with timers, helpers, templates.	Moderate. Trigger plus optional conditions (time, presence, sensor state). No if/elif/else, no loops, no templating. iOS Shortcuts covers edges but lives outside Home.	Basic. Starters plus conditions plus actions. No nested logic, no loops, no helpers. A YAML "Script Editor" exists but is limited compared to HA.
Voice assistant quality	Optional. HA Assist runs locally on the Yellow or a Wyoming satellite. Decent for device control, weaker for general questions. Most clients use Siri or Google Voice over the HA façade.	Siri. Strong for HomeKit control, weak for general knowledge vs Google. iOS 17 and 18 brought meaningful Siri improvements.	Google Assistant. Best general-knowledge voice of the three. Strong for Cast, calendars and search. Follow-up routine quality varies.
Dashboard customisation	Total. Lovelace plus custom cards (mushroom, button-card, ApexCharts). We deliver wall tablets, phone dashboards and floor-plan views as part of a normal custom dashboards install.	Minimal. Rooms, scenes, favourites. No free tile arrangement, no theming, no floor plans. What Apple ships is what you get.	Minimal. Favourites and routines. Fixed widget set on Nest Hub. Closer to HomeKit than HA.
Third-party device breadth	~2,800 integrations as of HA Core 2026.4. Anything with an API; anything Zigbee, Z-Wave, Thread, Matter, ESPHome, Tasmota, MQTT.	Hundreds of certified accessories. Matter expanded the catalogue in 2024-2025 but coverage stays narrower than HA.	Several thousand "Works with Google" devices; the count fell after the 2023-2024 Works-With-Nest shutdowns. Matter is closing the gap.
Learning curve	Steep. We see roughly 60 hours of homeowner time to reach "comfortable" — meaning you can write your own basic automations and debug a misbehaving entity.	Shallow. Most users are productive within an hour. Adding a HomeKit accessory is a QR-code scan.	Shallow. Comparable to HomeKit for basic setup, slightly steeper if you want to use routines as YAML.
Monthly cost	$0 baseline. Optional Nabu Casa cloud at ~$9 AUD/month for remote access and Alexa/Google voice bridging. No subscription required for core function.	$0 for HomeKit itself. iCloud+ at $1.49–$14.99 AUD/month enables HomeKit Secure Video for cameras — effectively required if you use camera doorbells.	$0 baseline. Nest Aware at $11–$23 AUD/month for camera history. Free tier lost meaningful features in 2023.
What happens when the company pivots	Nothing. Open Home Foundation governs the project; code is forkable. Even if HA disappeared, your local install keeps running and a community fork would emerge in a week.	You wait. Apple's HomeKit record is stable but slow. iOS upgrades occasionally break integrations (the 2022 Home architecture rollback being the famous example).	You lose. Google has killed Works-With-Nest in 2019, Nest Secure in 2024, the original Nest x Yale support, and steadily stripped Nest Hub features. Plan for change.

What each platform actually FAILS at

Every comparison article tells you what each platform is good at. The honest comparison is the reverse — what breaks, where each one stops working, and what we end up rebuilding for clients who chose the wrong starting point.

Home Assistant's failure mode: the learning curve

HA is hard. The documentation is excellent, the community is helpful, the software is impressive — and a DIY install with ten Zigbee devices and a single multi-trigger automation still takes the average homeowner 40–80 hours to get comfortable with, based on the post-mortems we do with clients who ask us to take over a half-finished setup.

Setup is not the killer. The killer is the second month, when you want an automation that says "if it's after sunset AND someone is home AND the lounge motion sensor has been still for 15 minutes AND no media is playing, dim the lights to 30 per cent" — and you have to learn YAML, the difference between state triggers and template triggers, and how to debug a misfiring entity. Most homeowners hit that wall and end up with a $200 Zigbee hub running three timers. That is the gap we fill.

HomeKit's failure mode: automation depth

Apple Home is simple for the first 20 devices. The wall it hits is conditional logic. There is no proper if/elif/else. You set a trigger and an optional condition, but you cannot say "if it's a weekday AND between 6am and 8am AND temperature below 18°C, turn on the bedroom heater; else if weekend, do something different." You end up creating five separate automations, each with one path, and the result is unmaintainable within a year.

The second failure is that anything not certified to Apple's spec simply does not appear. Older Sonoff devices, generic Tuya gear, Shelly relays, ESPHome builds — all work fine in HA and are invisible to Apple Home unless bridged through HomeKit Bridge, which means running HA underneath anyway. At that point the obvious question is why you picked HomeKit as the primary platform.

Google Home's failure mode: privacy and platform churn

Google's data-collection model is the product. Routines run in Google's cloud, voice queries are logged, Nest cameras stream to Google's servers. It is all disclosed, but it is a different relationship with your home than HA gives you.

The bigger issue is platform churn. Google has shut down or downgraded a sequence of products customers paid real money for: Works With Nest in 2019 (hundreds of integrations broke overnight), the original Nest Secure in 2024 (hardware bricked, customers offered a non-equivalent ADT migration), Nest x Yale lock remote features paywalled in 2023-2024, and a slow Matter implementation where multi-admin handover, lock controller support and energy reporting only landed in the Google Home app in late 2024. If you are building a smart home you expect to keep for 10 years, that pattern is the data point we keep coming back to.

What we install for 90% of clients

The pattern we recommend for almost every Central Coast household is the same: Home Assistant doing the real work, Apple Home as the family-facing façade.

The hardware spine is a Home Assistant Green appliance (around $170 AUD) for typical homes, or a Home Assistant Yellow (around $300 AUD, plus an SSD) for larger installs where PoE and an on-board Zigbee coordinator help. Both run Home Assistant OS, sit next to your router, and need no Linux knowledge from the homeowner. We build the automations, write the YAML, set up the integrations and hand over a working system.

On top of that, we expose rooms, scenes and quick controls into Apple Home using HA's built-in HomeKit integration (or Homebridge when we need finer control over which entities cross the bridge). The family interacts with the house the way they already interact with their iPhones — Control Centre tiles, Hey Siri, the Home app on a wall tablet. Nobody has to learn HA's interface to turn off the kitchen lights.

This pattern survives the failure modes of the alternatives: the family gets Siri without locking the back end to Apple, automations run locally on HA so they do not break in an NBN outage, adding a non-HomeKit device is a five-minute task, and if a household member switches to Android the controls migrate to a Google Home bridge or a wall dashboard without changing the back end. For households in Terrigal, Avoca and the rest of the Central Coast where the homes are mostly Apple, this is the closest thing to a default we have.

Migration paths: from HomeKit or Google to Home Assistant

Most of our HA installs are not greenfield. The household already has 15–40 smart devices spread across HomeKit or Google Home, accumulated over five or six years. The reasonable question is what carries over, what gets rebought, and how long the cutover takes.

From Apple HomeKit to Home Assistant

Essentially everything survives. Almost every HomeKit-certified accessory also speaks Matter, Thread, Zigbee, Z-Wave or has a manufacturer API HA supports — Aqara, Eve, Meross, Tapo, Nanoleaf, Philips Hue all integrate directly. HomePod and HomePod Mini stay useful as Siri endpoints once HA is exposed back to Apple Home via the bridge. Rarely does anything need re-buying; the only exceptions are niche "HomeKit-only" novelty products. For a 25-device household, a typical HA migration takes us two days of on-site work plus a week of automation tuning. The homeowner spends maybe four hours total.

From Google Home to Home Assistant

Most Nest hardware integrates with HA via the Nest Device Access program (a one-off $5 USD developer fee plus a few config steps). Chromecast and Cast-capable speakers work via HA's media player integration. Nest Hub Max stays functional as a Google Assistant endpoint even after HA takes over automation logic. The re-buys are older Works-With-Nest accessories whose cloud integrations Google killed and discontinued Google-branded products with no local API — usually 5–10 per cent of the installed base for a long-standing Google home. Cutover time is comparable to the HomeKit path with slightly more effort unpicking Google account permissions.

The ecosystem-lock cost calculator

Five-year cost is where the platforms genuinely diverge. A representative four-bedroom Central Coast household running 40 smart devices, comparing all-in cost from year 0 to year 5:

• HomeKit-only: Apple TV 4K hub $269 AUD + iCloud+ 200 GB for HomeKit Secure Video at $4.49/month ($269 over 5 years) + accessory replacements as Apple deprecates older HomeKit versions (~$200) + a 20–40 per cent price premium on Apple-certified accessories vs generic (~$600 on a 40-device install). 5-year premium over open standards: roughly $1,300 AUD.
• Google Home: Nest Hub Max + 2-3 Nest Minis $600 AUD + Nest Aware Plus for 2 cameras at $14.50/month ($870 over 5 years) + 1-2 forced replacements from Google product changes (~$300). 5-year cost: roughly $1,200 AUD.
• Home Assistant: HA Green plus Zigbee coordinator ~$240 AUD + optional Nabu Casa cloud at $108/year ($540 over 5 years; some clients self-host instead) + open-standard devices at market median price. 5-year total: roughly $780 AUD with Nabu Casa.

To be fair to HomeKit: if your household is Apple-only and the brief is basic lighting, climate and security, HomeKit is simpler than HA and the price premium is the cost of not running a server. The calculator only matters when you want real automation depth. And HA's $780 figure does not include our install fee — a full automation design typically adds $2,000–$6,000 depending on scope. But the lock-in trajectory stays roughly flat where the others compound.

When HomeKit or Google Home actually is the right answer

We do not push every client toward Home Assistant. The HA-plus-Apple-Home pattern is the right answer for the 90 per cent that want real automation; the other 10 per cent splits between two cases. HomeKit-only is the right call for Apple-only households with no expected Android migration, a postcard-length automation list (entry lights at sunset, garage close at 10pm, AC on warm afternoons), a $2k–$4k installed budget cap, and an explicit "no server in the house" preference. Google Home-only fits households already heavily invested in Nest hardware where the primary use-case is voice and Cast media rather than complex automation, with the data-collection trade-off knowingly accepted. For everyone else — mixed devices, "I want it to learn", meaningful energy monitoring and tariff-shifting automations, or anyone who has been burned by a cloud product disappearing — the answer is HA with the appropriate façade.

What the install actually looks like

A typical HA-with-Apple-Home install runs over three appointments: a free site assessment where we walk the property, list every existing device and quote a scope; an install day with hardware mounted, network configured, devices migrated and baseline automations written; and a handover session two weeks later where we tune the automations against real weekday and weekend usage. For households adding a climate control layer, we integrate ducted zoning, Sensibo or Tado for split systems, and presence-aware fallback so the AC does not run on empty rooms — all from the same HA core. The same architecture handles energy work, which we cover in our energy monitoring guide.

The honest summary

Home Assistant bets that local control and open standards beat polished simplicity over a 10-year horizon. We agree, which is why it is the back end on 90 per cent of our installs. Apple Home bets that simplicity inside Apple's walls is worth the constraints — true for genuinely Apple-only households with light automation needs. Google Home bets that voice plus the broadest device catalogue, hosted in Google's cloud, is the winning trade. For most clients in 2026, after the Works-With-Nest pattern repeated itself enough times, we cannot recommend it as the primary platform.

Smart-home choices compound. Every device bought under one platform is harder to migrate later. The right call early saves a lot of rebuying later — which is the conversation we have in every free site assessment.