To support our growing smart home ecosystem and provide more development tools and resources, we've launched the Google Home Developer Console, a unified console for building all things smart home.
To provide a single destination for all your development needs, your smart home Cloud-to-cloud account and projects will start migrating to the Developer Console around mid November 2024. Once migrated, your projects in the Actions console become view-only.
This document provides key dates and details to ensure a seamless migration to the Google Home Developer Console.
Migration timeline
The following table defines the terms and timelines related to the migration. You'll receive a reminder email prior to migration, which will take place in batches.
| Dates | Details |
|---|---|
Starting in early-November 2024 |
|
Mid November 2024 |
Migration begins.
|
Who is impacted by this deprecation?
All developers who have built the following in the Actions Console:
- Cloud integrations (both Conversational Actions and Direct Actions).
- Local Home integrations.
- Seamless Setup integrations.
- App Flip or App Discovery features.
- Directory information used for the Google Home app (GHA).
What's changing?
Your existing projects will be migrated to, and managed exclusively in the Developer Console going forward.
Seamless Setup and App Discovery will stop onboarding new use cases in the Actions Console.
In the Developer Console, local execution is an add-on to your Cloud-to-cloud integration, not a separate integration type.
What's not changing?
The feature set you're familiar with in the Actions Console is fully supported in the Developer Console, with the exception of Seamless Setup and App Discovery capabilities.
Your user and product experiences aren't changing.
How will this help my development process?
The Google Home Developer Console supports your development journey from learning to launching. In addition to the ability to manage all of your smart home integrations in one console, the Developer Console offers:
A suite of new features, including an automated and streamlined certification review process.
An improved end-to-end workflow with quick access to relevant technical documentation.
What can I do with my smart home projects and Actions until the migration date?
When must I stop creating, updating, and launching smart home Actions in the Actions console?
Starting in early-November 2024, you can no longer create new projects in the Actions Console. After this date, all new projects must be created in the Developer Console. Your existing project data will migrate to the Developer Console a few weeks later.
You can update an existing project on the Actions Console until the project migration starts.
Do I need to modify my smart home projects or Actions to prepare for the migration?
Generally, your smart home projects and Actions will be migrated over as-is. There is no action required on your part and the product experience of launched Actions won't be impacted. If you'd like to have your un-launched Actions migrated as seamlessly as possible, we recommend going to the Actions Console and saving the Draft again.
Also, there are two scenarios to be aware of:
If the Simulator in Actions Console uses the version of your Action that's not in Draft, that version will be migrated instead and you might lose the latest data stored in Draft. To avoid this, make sure to use a draft version in the Simulator before the migration begins.
If there is invalid data before the migration starts, including missing fields or entries formatted incorrectly, this data won't be migrated. Instead, these fields will be replaced with the last known valid data. To avoid this, make sure that all fields are completed and correct before the migration starts.
What will happen to my smart home projects and Actions on the migration date?
Will all smart home features in the current Actions Console be available in the Google Home Developer Console?
Yes, all current features and capabilities that are available in the Actions Console will be available in the Developer Console, and new customizations will be available. The Company Profile has added capabilities so you may need to revisit this area in the new console.
I have a live smart home Action. Will it be affected?
No, your launched smart home Actions won't be affected by the migration and your users won't be impacted.
Do I have to delete my smart home Actions or projects?
No. After your smart home Actions and projects are migrated to the Developer Console, they will still exist in the Actions Console but they will be view-only. No edits can be made.
Will I still have access to the Actions Console?
Yes, you can still access the Actions Console but all smart home content and data will be view-only.
How do I get started in the Developer Console after my projects are migrated?
What do I need to do to start building?
After your projects are migrated, sign in to the Developer Console, accept the Terms of Service for Google Home Developers, and you'll be able to access all of your existing projects!
I don't see "Actions" in the Developer Console. Have they been renamed?
Yes, your smart home Actions on Google projects are now called 'Cloud-to-cloud integrations' to support our expanding ecosystem. This change doesn't affect your current Actions on Google or product experience.
Where is the technical documentation?
All technical documentation, codelabs, and tools are available here in the Cloud-to-cloud documentation section of this site. You'll also see relevant documentation in the console as you move through the different development phases.
How do I get help?
If you find a bug or need help with the migration, please submit feedback using the Google Home issue template. For general Cloud-to-cloud information, take a look at our support channels and FAQ.