Hey everyone,
As the smart home industry evolves toward openness and collaboration, it's important to us that our users can build their ideal smart home, with Google products and a rich ecosystem of smart home devices. That’s why in late July, we’ll be making software updates to Nest Hub Max to make sure our users are ready for the upcoming Matter over Thread standard that will enable future compatibility with hundreds of partner devices.
This update will impact connectivity for a small number of Nest x Yale Lock and Nest Detect open/close sensor users that use a Nest Hub Max as the sole method to connect their lock to Wi-Fi, or as a range extender for either their lock or sensors.
Nest x Yale Locks and Nest Detects do not connect directly to Wi-Fi, but rather through a bridge. This enables these devices to last longer on batteries and enjoy extended range. The majority of Nest x Yale Lock and Nest Detect users have a Nest Connect or Nest Guard acting as that bridge, and these users will not be affected by the update.
Some users, however, may be using a Nest Hub Max as the bridge, or as a range extender between their Nest x Yale Lock or Nest Detect and other bridge devices such as a Nest Connect or Nest Guard.
Once this software update rolls out, Nest Hub Max will no longer support bridging or range extension. At that time, users whose locks are connected to Wi-Fi via a Nest Hub Max, or that are out of range of their Nest Connect or Nest Guard will not be able to lock or unlock their door with the Nest app. Users will still be able to lock and unlock the door using the keypad on the Nest x Yale Lock. Nest Detects that are out of range of Nest Connect or Nest Guard will not be able to connect to Wi-Fi and report their status in the Nest app.
If you’re affected by this change, here’s what you can do:
If you need further assistance, please feel free to give us a call or chat.
The Google Nest Team