📱 Bluetooth presence and smarter alarm automations

Use your Google speakers to detect whether your phone is home and react to alarm and timer events in automations. You can also choose which Google homes to include, inspect firmware and Wi-Fi details, and troubleshoot problems with new diagnostics and quieter logs.

⚠️ Before you update

• Removed devices are cleaned up automatically, usually 20–40 minutes after Google stops listing them. After a factory reset, check the new device's entity IDs and any automations that use them.
• Entity names now follow Home Assistant's language. Existing entity IDs stay the same; new ones may use translated names.
• Turning off polling now stops all automatic checks, including Bluetooth scans. Refresh devices still updates device data, but does not run Bluetooth scans.
• An update interval of 0 no longer stops regular checks. If your saved interval is below 1 second, the integration uses 15 seconds while polling is enabled. A repair lets you save the default or turn polling off instead.

✨ Highlights

📱 Bluetooth tracking with your speakers

Turn off the lights when everyone leaves, or use your phone's presence in other automations. Enable Bluetooth tracking in the integration's options, then select Track a Bluetooth device.

To track a phone, you'll need its Identity Resolving Key (IRK), which lets the integration recognize it as its Bluetooth address changes. See Add a device to track for instructions. Devices with a fixed Bluetooth address can use that address instead.

Under good scan conditions and with no additional departure delay, a phone can show home within about a minute of arriving and not_home about 60–90 seconds after leaving. Each tracker also shows which speakers hear it and how strongly. Tracking reports presence at home, without identifying rooms, and a speaker can hear a phone just outside. If scans can't establish presence, the tracker can show unknown or unavailable.

To reduce brief false departures, set an Additional departure delay of up to 120 seconds for an individual tracker. You can change it later through Reconfigure, without adding the device again. It delays real departures too, while arrival detection stays unchanged.

Tracking is off by default. Whether scanning affects Bluetooth audio playback hasn't been tested. See Bluetooth tracking for setup and limitations.

Thanks to @Lash-L (#891) and @marcusds (#964) for their earlier work on Bluetooth tracking! 🙏

📟 More about each device

When a speaker keeps dropping off, you now have more clues:

• Firmware version on the device page, plus an update sensor showing whether the device reports an update waiting.
• Wi-Fi network and signal strength sensors to help investigate connection problems.
• Uptime, showing the estimated time of the device's last boot, to help investigate unexpected restarts.

Wi-Fi and uptime sensors are disabled by default; enable the ones you need on the device page. These values normally refresh about every 20 minutes, and some devices don't report them all. The update sensor relies on the device's own report; an available update hasn't yet been observed in testing. See Device entities for details.

🏠 Choose which Google homes to add

If your account belongs to several Google homes, you can now choose which ones to include during setup or later in Configure. Existing installs keep every home until you change the selection. A new home attribute on each device sensor also helps distinguish speakers with the same name.

Thanks, @jazzyisj, for asking in #363!

🔔 React to alarm and timer events

Turn on a light when an alarm stops ringing, or react when it's snoozed. The new Alarm events and Timer events entities let you select these events in the automation editor, including changes to items beyond the speaker's next alarm or timer.

Ringing updates are faster too. For alarms and timers the integration already knows about, the end of ringing now usually shows within about 10 seconds while the speaker keeps answering, even with a long update interval.

Events reflect changes seen during checks: they can miss a short ring, and stopped doesn't prove someone dismissed it. For precise timing at a known due time, keep using the sensor's time trigger. The automation examples show both approaches, plus a script to announce timers from all your speakers.

⏸️ Stop checking individual devices

Disable a speaker that's unplugged or out of use in Home Assistant to stop checking it while your other speakers keep updating. Disabled speakers also stop Bluetooth scanning and no longer prevent trackers from confirming that you're away. Enable the device again when you want to use it.

🩺 Easier troubleshooting, quieter logs

Download diagnostics from the integration's menu to see device status and Bluetooth scan coverage. System information also has a Google Home section showing whether Google's servers and your devices are reachable.

Repeated failures no longer fill the log with the same error: it records the problem when it starts and reports when it clears. Sign-in and device errors describe what actually failed, with recovery guidance that also accounts for polling being off.

🏆 Platinum on the quality scale

The integration now meets all applicable rules through Platinum on Home Assistant's integration quality scale, covering setup, recovery, documentation and code quality. This is our own assessment: Home Assistant awards tiers only to built-in integrations, so the integration page still says Custom integration.

🐛 A few fixes worth mentioning

• Bluetooth trackers can restore a recently confirmed state after a restart while fresh scans resume. A speaker that stops returning scan results no longer blocks away detection indefinitely: after five minutes, it drops out of the required scanners. At least one active scanner must still confirm absence.
• Speakers keep updating when Google's device list is temporarily unavailable, and one speaker failing its first update no longer prevents the others from setting up.
• Unexpected alarm and timer replies no longer make a speaker's entities unavailable. Unknown statuses show as unknown; unreadable replies keep the previous values.
• Refresh devices can bring unavailable sensors back, including when polling is off. Devices that reject every token from Google also cause far fewer repeat requests.

There are translation improvements throughout, and the docs have shorter guides, more automation examples and clearer troubleshooting steps.

Requires Home Assistant 2026.11.0 or newer.

Thanks to everyone who reported problems, suggested improvements or shared feedback. ❤️

📋 All changes

117 merged pull requests since v1.16.0. Full comparison.