Most “stuck” updates are actually staged rollout pauses — the thermostat just hasn’t been selected yet. Here’s how to tell the difference and what to do in each case.
Firmware updates are downloaded over WiFi. A signal that's adequate for normal thermostat operation can still be too weak for a sustained file download — especially if the thermostat is far from the router or separated by thick walls. Even a brief signal dropout mid-download can pause or corrupt the update.
Google releases Nest firmware updates in waves — rolling them out to small percentages of devices at a time before expanding. If your device hasn't received an update yet, it may appear 'behind' compared to other users. This is normal and not a malfunction. Most devices receive updates within 2–7 days of the initial rollout.
On systems without a C-wire, a firmware update can drain the thermostat's internal power reserve — especially if the HVAC system isn't cycling frequently enough to recharge it. If power drops mid-update, the download pauses or fails. Ensuring the thermostat has stable power (via C-wire or the Nest Power Connector) prevents this.
In rare cases, a previous failed update can leave partial files on the thermostat's storage that block a new installation. A soft restart clears temporary state and usually resolves this. If a restart doesn't help after multiple attempts, Nest support can push a recovery firmware.
On the thermostat: Settings > Wi-Fi. Look at the number of signal bars or the RSSI reading if shown. One bar or 'Weak signal' indicates a marginal connection that can interrupt downloads. Firmware files are typically 10–50 MB — a weak connection that works for normal thermostat operation may not sustain a file download.
If the signal is weak, consider a WiFi extender or mesh node positioned closer to the thermostat. Alternatively, if your router is in the same general area, temporarily relocating it a room closer can confirm whether signal is the issue. After improving signal, soft-restart the thermostat and check whether the update resumes.
If the signal is fine and the thermostat is connected but hasn't updated, the device may simply not have been selected for the current rollout wave yet. Google's staged deployment process means some devices receive updates days later than others. Check the current software version under Settings > About > Software version, and compare it to the version number in Google's Nest release notes.
On the thermostat: Settings > Reset > Restart. This reboots the thermostat's software without clearing any settings or schedule. After restarting, the thermostat reconnects to Nest's update servers, which can trigger a pending update to resume from the beginning or continue from where it paused.
If your thermostat runs without a C-wire, check whether your HVAC system has been running recently. Mild weather that doesn't trigger heating or cooling can drain the thermostat's charge. If a firmware download keeps stopping, a C-wire or the Nest Power Connector accessory provides continuous 24V power and prevents download interruptions from power drops.
If the update has been stuck for more than 3–5 days and the above steps haven't helped, contact Nest support through the Google Home app: tap your profile icon > Help & feedback > Contact us. Nest support can push a forced update to a specific device, bypassing the staged rollout queue. Have your thermostat's serial number ready (Settings > About).
Our AI can check whether the issue is WiFi signal, power, or a server-side rollout delay — and help you request a forced update push from Nest support.
Describe what the thermostat displays and how long it's been stuck — our AI will give you targeted next steps.
Start Free Diagnostic Chat →