The Nest to Google Account migration began strengthening 2FA security back in November, as well as offering “seamless app connectivity” between smart home and assistant apps. The Nest Protect was not included in that initial transition, but Google has promised in recent months that it will address the oversight.
Multi-user support is passed over to the Google Home app following migration. The Nest app is lacking the capacity to add / remove members of the team. It is a problem for Nest Protects, since the smoke alarms do not feature with other first-party cams and thermostats in the Home app.
Consequently, alarm / warning alerts from the Protect will only be obtained in the Nest app, which — again — does not require you to contact other users after the change. In most households this single consumer existence is extremely restricting.
Cross-device integrations are also not possible, which is unfortunate as the smoke alarm has “occupancy” and ambient light sensors to activate the Pathlight/night light feature where the Nest Protect brightens when somebody walks underneath it at night. There’s obviously also a temperature sensor.
Immediately after the migration, Protect owners started querying Google about this oversight, and continue to ask. Back in March, a Googler in the support forum provided a definite status update. The team wants to address this and provide a “more seamless solution.”
Moving forward any new integrations that are needed for your Nest Protect, will be controlled in the Home App which will be available in the coming months. Our team is also exploring additional third party integrations and we look forward to sharing those with you as they become available.
A “coming months” timeline is provided for the Nest Protect to appear within the Google Home app and work with other devices. As part of that, unspecified “third party integrations” are touted. At Made by Google 2019 in October, the company did tout a generic smoke alarm use case: