Explainer Protocols
Does Google Home have Zigbee?
No Google or Nest device has ever spoken Zigbee, though several carry the radio chip Zigbee and Thread share. Here is where that confusion starts, and what to do if you already own Zigbee gear.
No. Zigbee has never been part of Google Home, and no device Google or Nest has sold has ever spoken it. Both halves of that matter, because the names Google uses get collapsed constantly: Google Home is the platform and the app, Google Nest is the hardware brand, Gemini for Home is the voice layer, Google Home Premium is the subscription, and Works with Google Home is the certification programme Google runs for other manufacturers' devices. Zigbee is absent from all five.
The radio is real. The protocol is not.
Here is where nearly everyone goes wrong, including people being careful. Several Nest devices genuinely do carry an 802.15.4 radio. 802.15.4 is the IEEE standard for low-power short-range radio, and it is the radio layer that Zigbee and Thread both sit on top of. Sharing that layer does not make two protocols compatible, any more than sharing a phone line made a fax machine and a modem compatible. What Google put on top of the radio was Thread, or Weave, its own in-house protocol. Never Zigbee.
| Device | Radio on board | What it actually speaks |
|---|---|---|
| Nest Hub Max | 802.15.4 at 2.4 GHz (FCC ID A4RH2A) | Thread. Certified by the Thread Group on 11 September 2019. |
| Nest Guard | 802.15.4 (FCC ID ZQAH10) | Weave |
| Nest Connect | 802.15.4 (FCC ID ZQAH17) | Weave |
| Nest Detect | 802.15.4 (FCC ID ZQAH11) | Weave |
| Nest Learning Thermostat (2nd gen) | Ember EM357, a chip its maker sold as a "ZigBee/802.15.4" SoC (from a teardown, not a Google spec) | Weave |
| Nest Protect | 802.15.4, per Google's own description of Weave | Weave |
Nothing was hidden, and nothing was switched off
The other half of the myth is that Google quietly disabled a Zigbee radio it had already shipped, usually pinned on the Nest Hub Max. That did not happen. The Nest Hub Max's 802.15.4 radio was documented from launch and certified by the Thread Group in September 2019 as the first certified, publicly available Built on Thread device, and it did a job from day one, though a narrow one: pairing with a Nest x Yale lock, and extending the range of a Nest Secure system. General-purpose Thread came years later. A radio that is documented, certified and working is not a disabled one, and the honest statement is that Google never shipped a Zigbee integration, not that it hid one.
A Nest Hub is not a Zigbee hub
Anyone describing a Nest Hub as a Zigbee hub is picturing a SmartThings-style device and putting a Google name on it. What a Nest Hub actually is, is a Matter controller. Several Google devices do that job, and only some of them carry a Thread radio, which is a trap worth understanding on its own terms: we have set out which is which. None of it involves Zigbee.
What to do if you already own Zigbee devices
This is the useful half, and the news is good. You do not need Google to speak Zigbee. You need a Matter bridge.
A bridge is a hub that speaks Zigbee on one side and Matter on the other, and Google documents both the pattern and the behaviour precisely. In Google's words, all devices behind a Matter bridge appear as normal for a user in the Google Home ecosystem, while the bridge itself appears as an inert Control Bridge device type. So your Zigbee sensors and bulbs show up in the Google Home app as ordinary devices, and the bridge sits there doing nothing visible.
Most people who own Zigbee gear already own the bridge. A Philips Hue Bridge, an Aqara M2 or M3, or an IKEA Dirigera will each present the Zigbee devices paired to it into Google Home over Matter. Know the limit before you count on it: a brand bridge carries the devices it was built for, not every Zigbee device in the house. If yours are spread across brands, the tidier answer is a bridge that pools them onto one network, rather than three brand hubs sitting side by side.
What you give up is the brand-specific layer. Matter carries standard device behaviour, so a light still dims and changes colour, but gradient effects, entertainment sync and a brand's own scenes generally stay in the brand's app. Philips Hue is the clearest case: Hue's own Matter guide reserves gradient lighting and dynamic scenes for the Bridge. For most people that is a fair trade for having everything in one place.
Buying into Google Home from here
Two situations, two answers. If you already run Zigbee, keep it and bridge it. Nothing about Google Home asks you to throw it out. If you are starting fresh and Google is your platform, the shortest path is Matter, over Wi-Fi for mains-powered devices and over Thread for battery ones, with a Thread-capable Google device in the house. Either way, do not go shopping for a Google device with a Zigbee integration. There isn't one, and there never has been, whatever the silicon inside is capable of.
Frequently asked questions
Does Google Home have Zigbee?
No. Zigbee has never been supported by Google Home, and no Google or Nest device has ever run a Zigbee stack. Some Nest hardware carries an 802.15.4 radio, which Zigbee and Thread share as their radio layer, but Google ran Thread or its own Weave protocol over it.
How do I add Zigbee devices to Google Home?
Through a Matter bridge. Pair the Zigbee devices to a bridge that supports Matter, such as a Philips Hue Bridge or an Aqara M2, then add the bridge to Google Home as a Matter device. The Zigbee devices behind it appear in the Google Home app as normal devices, and the bridge itself shows up as an inert Control Bridge.
Do any Google Nest devices have Zigbee?
None run Zigbee. Several older Nest products carry 802.15.4 radios, among them the Nest Hub Max, Nest Guard, Nest Connect, Nest Detect, Nest Protect and the 2nd gen Nest Learning Thermostat, and the thermostat's chip was even sold by its maker as a "ZigBee" part. Every one of them ran Thread or Weave. Zigbee-capable silicon is not a Zigbee device.
Is the Nest Hub a Zigbee hub?
No. A Nest Hub is a Matter controller, and the 2nd gen and the Max are also Thread border routers. Anyone describing a Nest Hub as a Zigbee hub is thinking of a SmartThings-style hub, which is a different kind of product.
Did Google disable the Zigbee radio in the Nest Hub Max?
No, and there was nothing to disable. The Nest Hub Max's 802.15.4 radio was documented at launch, certified by the Thread Group in September 2019, and used from day one to pair with a Nest x Yale lock and extend a Nest Secure system. It ran Thread, not Zigbee.
Still need a hand?
We answer most messages within one business day. If your question is about an existing order, have your order number ready. It speeds things up.
Contact us