Google Meet hardware updates itself automatically. Each device follows a release channel set in the Google Admin console: Stable (the default), Delayed stable (updates held about 30 days), Beta (early access for testing) or Test (internal testing only). Google publishes what changed in its "What's new in Google Meet hardware" help article and in Google Workspace Updates.
Release channels
| Channel | What it does | Use it for |
|---|---|---|
| Stable | Latest stable release | Most rooms |
| Delayed stable | Holds updates back about 30 days | Boardrooms, executive rooms, event spaces |
| Beta | Next stable release early | A small test group, roughly 2-5% of devices |
| Test | Earliest builds, may have bugs | Internal testing only |
Google recommends keeping beta off critical rooms and turning on logs and feedback for any device on beta.
How to change the update channel
- In the Google Admin console, create a child organizational unit for the rooms you want on a different channel. You can't change the channel at the top-level OU.
- Move the devices into that child OU.
- Go to Devices > Google Meet hardware > Settings.
- Select the child OU, open Release channel, choose the channel and click Save.
- Allow up to 24 hours for the change to apply. It's often faster.
Moving a device to a slower channel doesn't roll back its software. A device on a newer version stays there until the slower channel catches up.
Reboots and timing
Meet hardware applies updates with a reboot. Set the device time zone and a scheduled reboot time in the Admin console so updates land outside working hours. See Google Meet hardware setup.
Where to find release notes
- Google Meet Help: "What's new in Google Meet hardware" lists features by release.
- Google Workspace Updates blog announces new Meet hardware features and rollout timing.
- Admin console device list shows each device's current OS version, so you can confirm a rollout.
- Manufacturer notes: Logitech, Neat and other vendors publish firmware notes for peripherals and Android-based Meet devices.
Auto-update expiration
ChromeOS-based Meet hardware has an auto-update expiration date, after which Google stops sending updates. Google is also moving Meet hardware to Android-based devices. Check your fleet's dates before planning refreshes. See Meet hardware end of support.
Update troubleshooting
- Device stuck on an old version: Check its OU and channel, and confirm it can reach Google's update servers through your firewall.
- Feature missing after update: Some features roll out gradually or need a setting turned on in the Admin console.
- Device won't boot after update: See Meet hardware reset and recovery.
More: Google Meet hardware, certified Meet hardware, Meet hardware licenses, best Google Meet hardware.
Planning a Meet hardware refresh? Send us your room list and we'll match current devices.
Related guides
Outfitting several rooms, or reselling? Get a volume quote or apply for wholesale pricing →
