Google Wallet home keys are rolling out in Google Home's Public Preview, but the phone and lock must support the particular way you want to open the door. NFC tapping and hands-free arrival have different requirements; an ordinary Matter lock is not sufficient.
Google's November 11, 2026 release notes date the rollout. The originating Android Central report appeared on November 13. Google describes wider availability over the following weeks, so a current app alone does not establish that an account has the feature.
Match the hardware to the way you unlock
Google's announcement requires an Aliro-compatible, Matter-certified lock, a Matter-enabled Google hub with a Thread Border Router, and updated Home and Wallet apps. NFC tapping supports Android 9 or later. Wear OS watches are excluded at launch.
The launch examples show why checking individual features matters: Google lists Aqara U400 for NFC and UWB, while Schlage Sense Pro starts with NFC and has UWB support to follow. Nest Hub (2nd gen) is among the named compatible hubs. These are compatibility examples, not recommendations to replace working hardware.
For hands-free entry, both the phone and lock need compatible Aliro UWB support. Google's Wallet documentation specifies Android 17 or later for supported Pixel 10 Pro, Pro XL and Pro Fold models and their successors; consult the manufacturer for current device eligibility. The approach-unlock toggle appears only with a compatible combination.
Aliro 1.0, released by the Connectivity Standards Alliance on February 26, defines communication between a credential device and an access reader. It supports NFC and Bluetooth LE, with Bluetooth LE plus UWB for hands-free access. The distinction explains why the standard's name cannot substitute for the feature list of a particular installation.
Decide who can enter and how they verify
The Home integration associates a key with a home rather than an individual lock. Household members can add their own keys; Google describes guest passcodes for temporary visitors. Approach unlocking is opt-in, and Wallet provides a setting to require device unlocking for a tap.
Treat enrollment as an access decision: check household membership and the verification setting before relying on the convenience. Google's residential-key guidance explicitly says to retain a physical key as backup. That remains useful even when the digital setup works, because another compatible phone is not a substitute for a fallback you can actually reach.
Sources
Related Articles
WHOOP Humans brings direct following to fitness data, with small-team links carried over
WHOOP's new social feed lets members choose metrics and share photo Moments. Existing small-team connections can become follows automatically.
Bluetooth Core 7.0's 7.5 Mbps headline depends on optional HDT support
HDT raises Bluetooth LE's maximum radio bitrate, but both the feature and its highest rates are optional. Existing-device compatibility is not a speed upgrade.
IBM maps a 1,040-qubit Nighthawk system by connecting two planned r3 processors
IBM's next Nighthawk design expands programmable qubits and chip links. Developers can evaluate r2 today while treating the larger system as a 2027 plan.
KORA plans a 2027 Linux AI desktop with support for selected Windows apps
The announced system combines local models, optional cloud services and managed workspaces. A migration decision still needs evidence for the applications and data flows you use.