## 2026-09-16 Home MCP / Home Developer MCP September 2026 We've launched two new MCP servers. Home MCP lets personal agents interact with your smart home safely, while Home Developer MCP makes documentation from the Home Developer Center and other smart home resources available for your favorite agents to search and query. See the [MCP Servers](https://developers.home.google.com/mcp) page to learn more. ## 2026-09-10 Google is transitioning third-party smart home account linking to be handled fully and independently within the Google Home app (GHA), retiring legacy dependencies on the Google Search app and Google Assistant settings.
Core backend OAuth 2.0 infrastructure, credentials, and fulfillment webhooks remain unchanged. Partners need to update in-app and web deep links, App Flip allowlists (if supported), and customer-facing setup instructions. Review your integrations to verify whether the following changes are needed. If your integration relies on in-app deep links or App Flip, these updates must be completed by October 30, 2026 to avoid failures with in-app linking attempts. For more information, see the [Account linking migration guide](https://developers.home.google.com/cloud-to-cloud/account-linking-migration). ## 2026-08-12 Updated EXECUTE response guidance and examples for commands requiring PENDING status.
To better represent device state transitions and improve responsiveness, we've updated the [Cloud-to-cloud Device Type guides](https://developers.home.google.com/cloud-to-cloud/guides) and schemas with guidance for commands that have naturally longer processing or physical operation times (such as opening/closing, locking, starting/stopping, cooking, dispensing, or docking). For these commands, integrations should return `status: "PENDING"` in the initial `EXECUTE` response and follow up by reporting the final state asynchronously using the [Report State and Notification API](https://developers.home.google.com/cloud-to-cloud/integration/notifications#send-notification) once the operation completes. Updated `EXECUTE` response snippets and new command examples have been added across device type guides to illustrate this pattern.
## 2026-03-04 New guidance on optimizing your integration to reduce latency. To help you improve the responsiveness of your integration, we've added new guidance on reducing latency. See [Latency reduction options](https://developers.home.google.com/cloud-to-cloud/analytics/home-vitals#latency_reduction_options) for details on geo-routing and application-layer optimization strategies. ## 2026-02-03 We've updated our Google Home Vitals page with more details on metrics and how they are calculated. In addition to the updated [Google Home Vitals](https://developers.home.google.com/cloud-to-cloud/analytics/home-vitals) page, we've also improved troubleshooting content for common Cloud-to-cloud integration errors. ## 2025-04-08 Updated security guidance for camera streaming OAuth tokens
Security is a priority when building with Google Home. We've recently implemented a change to the Smart Home [CameraStream](https://developers.home.google.com/cloud-to-cloud/traits/camerastream) Trait Schema and OAuth token requirements to better target devices. When getting a camera stream, `cameraStreamAuthToken` is mandatory if `cameraStreamNeedAuthToken` is true, and the token needs to be scoped to just the target device.
## 2024-11-20 Cloud-to-cloud on the Google Home Developer Console The Google Home Developer Console is now your one-stop shop for managing and launching Cloud-to-cloud integrations, including essential test tools and analytics. The Actions on Google console has been deprecated. See [Smart home Actions migration overview](https://developers.home.google.com/cloud-to-cloud/project/migration) for more information on the upcoming project migration. ## 2023-08-30 Released a new version of the Google Home Extension for VS Code. [Minor bug fix](https://developers.home.google.com/tools/vs-code) to improve sign in security. ## 2023-06-06 Released a new version of the Google Home Playground. The [Google Home Playground](https://developers.home.google.com/tools/google-home-playground) simulate a smart home project by creating and modifying a virtual home with configurable device types and traits. ## 2023-05-31 Released a new version of the Google Home Extension for VS Code The [Google Home Extension for VS Code](https://developers.home.google.com/matter/tools/vs-code) is an extension to give you access to tools to simplify your Matter and smart home development process. ## 2023-05-08 Implement CameraStream with WebRTC codelab published.
Learn how to stream from a webcam to a Google Nest display device with the [CameraStream trait and WebRTC](https://developers.home.google.com/codelabs/smarthome-webrtc).
## 2022-11-21 Smart home docs now live in Cloud-to-cloud.
All smart home documentation on the [Assistant developer site](https://developers.google.com/assistant) have migrated to the Cloud-to-cloud section on the Home Dev Center. See [Get started](https://developers.home.google.com/cloud-to-cloud/get-started) to learn more. Note that you'll continue to use the [Actions console](https://console.actions.google.com) to build Actions. ## 2022-11-09 Trait-level sample utterances added. Moved all sample utterances from [device type reference pages](https://developers.home.google.com/cloud-to-cloud/guides) to [device trait reference pages](https://developers.home.google.com/cloud-to-cloud/traits). ## 2022-10-04 Secondary User Verification has been added to the Google Home Playground.
See [Google Home Playground page](https://developers.home.google.com/tools/home-playground#add_a_secondary_user_verification_to_virtual_device) for more information.