ha-google-home is an MIT-licensed, Python-based Home Assistant custom component that brings Google Home and Nest speakers and displays into Home Assistant so their alarms and timers can be read, deleted and automated.

What it is

The project is a community integration for Home Assistant, the open-source home automation platform, and it is distributed through the default HACS repository rather than through Home Assistant's built-in integration list. It is written in Python under the MIT licence, carries topics such as homeassistant-integration, hacs, sensor and google-home, and was generated from @oncleben31's Home Assistant custom component cookiecutter, with code templates taken from @Ludeeus's integration_blueprint. Under the hood the integration relies on the glocaltokens Python package.

The concrete problem it solves is visibility. Alarms and timers set on a Google Home or Nest speaker or display live inside Google's own app and are otherwise invisible to Home Assistant, so they cannot be shown on a dashboard or used to drive an automation. This component surfaces them as Home Assistant entities and adds actions to delete them, which is the gap the project was created to fill: it began from a community discussion about reading Google Home alarms and timers in Home Assistant. It deliberately does not replace the rest of the Google Home app — lights, thermostats and the other devices listed there are out of scope and the README points elsewhere for them.

Key capabilities

• Alarms and timers from Google Home and Nest speakers and displays are exposed as Home Assistant entities.
• Do Not Disturb can be turned on or off from Home Assistant.
• Alarm volume is exposed as an entity alongside the devices themselves.
• Actions are provided to delete alarms and timers, reboot devices and refresh them.
• The integration is listed in the default HACS repository, so it is installed by searching for Google Home.
• It depends on the glocaltokens Python package under the hood rather than reimplementing Google's authentication flows.
• Full documentation is published separately at ha-google-home.pages.dev, with dedicated pages for entities, actions and troubleshooting.

Who uses it and how

• Home Assistant users running HACS who want alarm and timer state on their dashboards; the documentation's community page collects dashboard cards contributed for this purpose.
• Households that automate around spoken alarms: the project grew out of a community discussion on tracking Google Home alarms and timers and triggering different Home Assistant events from them, and the same community page gathers Node-RED flows.
• Homes equipped with either Google Home and Nest speakers or the equivalent displays, since the integration covers both form factors.
• Self-hosters who are willing to sign in with their Google account during setup; the Getting Started page covers prerequisites, installation and sign-in.
• A mid-sized community: 567 stars, 110 forks and 22 open issues, with questions directed to GitHub Discussions and bugs and feature requests to the issue tracker.

Getting started

The integration is installed from the default HACS repository by searching for Google Home. Manual installation, prerequisites and the sign-in process are documented on the Getting Started page at ha-google-home.pages.dev/installation/.

How it compares

No paid products and no comparable integrations are named in the facts provided for this entry, so this project stands alone in this registry rather than being contrasted with alternatives. The only related project the README references is glocaltokens, which is the Python package it depends on rather than a competing tool.

When to use it — and when not

A self-hoster needs a Home Assistant instance and a Google account to sign in with; no database, object storage or SMTP service is mentioned in the facts. It is the wrong choice if what you want from the Google Home app is lights, thermostats or other devices, because the integration explicitly does not add them. It is also a custom component whose real documentation lives off-GitHub at ha-google-home.pages.dev, so the README alone is thin and the documentation site is effectively required reading.