Why migrate from Google Home?
- Google removed local API access in 2023, so all automations — even for local devices — now depend on Google's cloud.
- Google Home routines are limited to simple IF/THEN logic. Home Assistant supports conditions, templates, parallel actions, and wait steps.
- Google Home does not support Matter multi-admin well: sharing devices to other platforms requires a separate pairing code.
- Home Assistant exposes significantly more sensor data and entity attributes than Google Home for the same devices.
- Privacy: Home Assistant runs locally. Device states and automation history stay on your network.
What carries over
Matter devices
Recommission to Home Assistant via multi-fabric. Keep them in Google Home too if you want Google Assistant voice control — both platforms can control the same Matter device simultaneously.
Thread devices (with border router)
Google Nest Hub (2nd gen) and Google Nest WiFi Pro act as Thread Border Routers. If you are keeping any Google devices, the Thread network stays intact. If you are removing all Google hardware, add another border router (HomePod mini, Apple TV 4K, or Aqara Hub M3).
Wi-Fi devices (Philips Hue, IKEA, TP-Link, etc.)
Most have official HA integrations that connect locally. Philips Hue, IKEA Dirigera, TP-Link Kasa, and Tapo connect via LAN without a cloud account.
Google Cast (speakers and displays)
Home Assistant integrates with Google Cast out of the box — you can keep your Nest Audio, Nest Hub, and Chromecast devices and control them from HA dashboards and automations.
Nest Protect, Nest Thermostat, Nest Doorbell
Nest devices connect to HA via the Google Nest integration using the Smart Device Management (SDM) API. This requires a one-time $5 developer fee for access to the Google SDM API.
What you will need
Home Assistant instance
Home Assistant Green (€99) is the easiest starting point. Yellow (€99) adds built-in Zigbee and Thread if you have those devices.
Matter Server add-on
Required to commission Matter devices. Free, install from HA Add-on Store.
Thread Border Router (if keeping Thread devices)
If you are migrating away from all Google hardware, you need a replacement border router. Apple TV 4K and HomePod mini both work. Home Assistant Yellow has one built in.
Google SDM API access
One-time $5 Google fee to enroll in the Device Access Program. Required only if you want to control Nest Thermostat, Nest Protect, or Nest Cam from Home Assistant.
Migration steps
- 1
Set up Home Assistant
Flash HA OS to your chosen hardware. Complete the onboarding. Do not remove anything from Google Home yet. Confirm HA is reachable from your local network.
- 2
Install Matter Server and set up Matter integration
Settings → Add-ons → Matter Server → Install. Then Settings → Devices & Services → Add Integration → Matter. This prepares HA to accept Matter device pairing codes.
- 3
Add Matter devices to Home Assistant (keep them in Google Home too)
In the Google Home app: open the device, tap Settings → 'Link apps and services' or 'Share with another platform' to generate a Matter pairing code. In HA: Settings → Devices & Services → Matter → Add Device. Enter the code. The device now responds to both Google Home and Home Assistant simultaneously.
- 4
Add Wi-Fi device integrations
Settings → Devices & Services → Add Integration. Most brands are auto-discovered on your local network. Accept the auto-discovery prompt or search manually for Philips Hue, IKEA, TP-Link Kasa, Tuya, etc.
- 5
Set up Google Cast integration (optional, keep Nest speakers)
Settings → Devices & Services → Google Cast → Configure. HA auto-discovers Cast devices on the network. You can now trigger TTS announcements and play media on Nest Audio and Nest Hub from HA automations.
- 6
Set up Google Nest integration (optional, for Nest devices)
Follow the Home Assistant Google Nest documentation to enroll in the SDM API. Requires a $5 one-time fee and a Google Cloud project. After setup, your Nest Thermostat, Nest Protect, and Nest Cam appear as HA entities.
- 7
Rebuild Google Home routines as HA automations
Open Settings → Automations. Each Google Home routine becomes an HA automation with a trigger and action. If your routine says 'When I say Good Morning → turn on lights and set thermostat', create an HA automation with a time-based or voice-based trigger and those actions.
- 8
Test for one week, then decide which Google Home routines to retire
You do not need to remove devices from Google Home. You can keep Google Home for voice commands and remove it from automations that now run locally in HA. Retire routines one at a time after verifying the HA equivalent works.
Common mistakes to avoid
- Google Assistant voice commands still work even after adding devices to HA — Matter multi-fabric means both platforms control the same device. You do not need to choose.
- Thread devices paired through Google Nest border routers may temporarily lose connectivity if you remove all Google devices from your network. Replace the border router first.
- The Google Nest SDM API (for Nest Thermostat and Cam) requires a one-time $5 developer fee. This is a Google policy, not an HA limitation.
- Devices that only work via the 'Works with Google' cloud integration (no local protocol, no Matter) will connect to HA via a cloud-based HA integration. Check the HA integration catalog — some brands have maintained local-only HA integrations even if they use cloud for Google Home.
- Google Home app presence detection (geofencing) should be replaced by HA Companion App location tracking before removing Google Home routines that use it.
FAQ
Can I keep Google Home and Home Assistant running at the same time?
Yes, and for most setups this is the best outcome. Matter devices can be controlled by both platforms simultaneously. Keep Google Home for voice commands (Google Assistant) and run automations in HA for local reliability and more complex logic.
Do I need to factory reset my Thread/Matter devices to add them to HA?
No. Use the 'Share to another platform' flow in Google Home to generate a pairing code, then add it to HA. The device joins HA without leaving Google Home.
My Wi-Fi light bulbs work via Google Home — will they work in HA?
Usually yes, if the brand has an HA integration. Check Home Assistant's integration catalog. Brands like Philips Hue, IKEA, TP-Link Kasa, Govee, and Tuya all have integrations. If the brand is cloud-only with no HA integration, you may need a Tuya-based local integration or a Matter firmware update.
What happens to my Google Home automations during the migration?
Nothing — Google Home routines keep running until you manually delete them. Rebuild each routine as an HA automation and test it before removing the Google Home version.
Next step
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.
Save the setup path, missing hubs, limitations, and next steps for later.
Tell us which device, hub, or ecosystem should be added to the compatibility library.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Tell us if you would pay for a one-time setup diagnosis report, and what device or hub is blocking you.