The routes
- Matter. The device is commissioned into Google Home as a Matter device. Control is local on your network. Google Home needs a compatible Google hub (Nest speaker or display) acting as the Matter controller, and Thread devices also need a Thread border router (some Google hubs act as one).
- Cloud-to-cloud. The long-standing route: a manufacturer (or you) builds an integration where Google's cloud calls your cloud, and you link the account in the Google Home app. Google's cloud-to-cloud docs list 80+ device types. Great coverage, but control goes via two clouds.
- Local Home SDK (local fulfilment). An add-on to cloud-to-cloud: once a device is linked, a Google hub can send commands to it directly over your LAN (discovery via mDNS, UDP broadcast or UPnP), falling back to the cloud if local fails. Needs a developer to implement; as a hobbyist you will mostly benefit from vendors that already support it.
- Home APIs. Google's newer developer APIs for building your own apps that control a user's Google Home devices (an Android SDK is generally available; as I write the Android release notes show version 1.11.1, dated 22 October 2026, with Matter 1.4.1 support and some experimental 1.5 support). These are for building apps, not for adding devices to Google Home.
- Hub bridges and clouds: Home Assistant Cloud can expose Home Assistant to Google Home through its cloud, covered in the companion Home Assistant post. Philips Hue and similar bridges use their own Google integration or Matter.
Google has been moving speakers and displays from Google Assistant to Gemini for Home. Some commands, routines and device behaviours change when this happens, and availability depends on your region and hardware. If you rely on specific voice commands, test them after the update rather than assuming they carry over.
Choosing
- New devices: buy Matter-certified where you can (look for the Matter logo and, for Thread, check the box). Make sure you have a suitable Google hub in the house.
- Existing Wi-Fi or cloud gear: the manufacturer's Google integration is the default route; check whether it supports local control.
- DIY: a Matter-capable device, or a hub that publishes your entities as Matter (see the companion post), keeps things local. Writing your own cloud-to-cloud integration is a big job: it needs OAuth account linking, a public HTTPS endpoint and Google's approval process.
- IPv6 and mDNS matter. Matter devices find each other over IPv6 and mDNS. Isolated VLANs, mDNS blocking and IPv6 disabled are common causes of "can't set up device" errors. Put the hub, phone and Matter devices on the same network while commissioning.
- Android: Matter setup in Google Home depends on Google Play Services on Android. Home Assistant's docs say to keep Play Services up to date and use a standard Google-account Android setup.
- Naming and rooms: short, unique names and rooms make voice control work.
- Cloud dependency: cloud-to-cloud devices stop responding to voice when the vendor cloud or your internet is down. Keep a physical switch for anything critical.
- Voice exposure: think twice before exposing locks, garage doors, alarms and heating to voice. Use confirmation and PIN options where offered.
- Clean up: after removing a device from its hub, delete it in Google Home too.
Question for the group: how are your devices connected to Google Home right now (manufacturer integration, Matter, Home Assistant), and have you noticed any changes since Gemini for Home arrived on your speakers or displays?