Nest App Not Working: How to Fix It in Order

Short answer

• Work in this order: check the Nest service status, check your home internet and Wi-Fi, check that you are signing in with the right account, update the app, then check device linking. Most Nest app failures are fixed by one of the first four steps, and skipping ahead to a factory reset usually wastes time.
• Start at the Nest status page, status.nest.com. If the service is down, nothing on your phone will fix it, and you need to wait for Google to restore the service.
• The most common sign-in cause is the wrong account. If you started using Nest before 19 August 2019 you may still have a separate Nest account, and if you migrated it, you must now sign in with the Google account you linked it to. Google's own sign-in help says to check the spelling of your email address first, because a mistyped address is the usual reason for an "incorrect email address or password" message.
• Do not factory reset a device until you have tried updating the app, clearing its cache on Android, and reinstalling it. A reset removes the device from your home and forces a full setup, while a reinstall only replaces the app on your phone.
• If you own a first or second generation Nest Learning Thermostat, the app will never work for it again. Google ended support for those models on 25 October 2025, and they were unpaired from the Nest app and the Google Home app on that date. The thermostat still works from its own controls, but no app fix will bring it back.

What “Not Working” Usually Means

“Nest app not working” covers at least five different failures, and each one has a different fix. The app may crash as soon as you open it. It may open and then sit on a spinning ring or a blank screen. It may refuse your sign-in. It may sign in but show no devices, or show devices as offline. Or it may work for the thermostat and fail for the camera, or the other way around. Treating all of these as one problem is how people end up factory resetting a thermostat that only needed an app update.

This guide works through the causes in the order Google’s own support pages suggest, from the service itself down to the device on your wall. The steps were checked against Google’s Nest and Google Home help pages on 11 November 2026. App menus change with updates, so where a step names a menu, the name given is the one current on that date, and the guide says so. If a menu has moved since then, look for the same words under Settings rather than assuming the step no longer applies.

Two things this guide does not cover. It does not cover account security beyond the app’s own password reset flow, and it does not cover the wiring or installation of any device. If a thermostat or camera has a hardware fault, no app step will fix it, and the guide says so at the point where that becomes the likely cause.

1. Diagnose the Failure Before You Fix Anything

Spend two minutes on diagnosis before changing anything. The symptom tells you where to start, and starting in the right place saves the most time.

First, note exactly what happens. Does the app crash, freeze on a loading screen, reject your sign-in, or open normally and show your devices as offline? A crash points at the app or the phone. A spinning ring after sign-in points at the account or the service. Devices shown as offline point at your home Wi-Fi or at the device itself. Write the symptom down, along with any error message word for word. Error codes matter: a Nest thermostat that cannot reach the app, for example, may show a TD error in the app, such as TD008 or TD013, and Google’s help pages give different steps for different codes.

Second, test on a second device. Open the Nest app on another phone or tablet, or sign in at home.nest.com on a computer. Google’s sign-in help makes this its key test: if you can sign in on one device but not another, the problem sits in the settings of the device that fails, not in your account. If the app fails on every device and the website fails too, the problem is your account or Google’s service, and reinstalling the app on one phone will not help.

Third, check whether the problem started after a change. Did you change your Wi-Fi password, get a new router, change internet provider, update the app, or update your phone? The Google Home and Nest community is full of reports where the app stopped loading the day the Wi-Fi settings changed, and the fix turned out to be updating the Wi-Fi details for the Nest products in the app, not reinstalling anything. If you changed your Wi-Fi network name or password, update the Wi-Fi information for your Nest products in the app before doing anything else. Our guide to building a smart home explains how the app, the network, and the devices fit together, which helps when you are deciding whether the fault is in one device or in the whole setup.

2. Check the Nest Service Status First

Before touching your phone or your router, check whether Google’s Nest service itself is down. A service outage produces exactly the symptoms people blame on the app: the app spins on loading, sign-in fails, and devices show as offline, all at once, on every device in the house.

Go to the Nest status page at status.nest.com. Google’s sign-in help lists this as the first check for a spinning ring or blank screen, and as the third check for a failed sign-in, after checking the email spelling and the password, and its thermostat troubleshooting pages repeat the same instruction. The page lists the current status of each Nest service. When this guide was checked on 11 November 2026, the page reported “Everything is running smoothly.” If it reports a problem instead, wait for the service to resume. No step in this guide will fix an outage, and resetting devices during one can make recovery slower, because the devices cannot complete setup while the service is down.

If the status page is healthy, the fault is on your side of the connection, and the next sections apply.

3. Check Your Internet and Wi-Fi

The Nest app needs two connections to work: your phone needs internet access, and your Nest devices need your home Wi-Fi. A fault in either one looks like an app failure.

Start with your phone. Open a browser on the phone and visit any website. If the site does not load, the phone has no working connection, and the Nest app is not the problem. If you are on Wi-Fi, try switching to mobile data, and if you are on mobile data, try Wi-Fi. Google’s thermostat help gives the same test in a stricter form: turn on airplane mode, then turn Wi-Fi back on, and visit google.com. That forces the phone onto Wi-Fi alone and rules out a silent switch to mobile data masking a dead home connection.

Next, check whether other devices in your home can get online. If no device can connect, the problem is your internet service or your router, and you should contact your internet provider. If other devices work but the Nest products do not, the problem is narrower: either the Wi-Fi network the Nest products use, or the products themselves.

Restart your modem and router. Google’s thermostat guide gives the exact sequence: unplug the power cords from the modem and router, wait 30 seconds, plug them back in, and wait a few minutes until the power and connection lights are steady. Restart any Wi-Fi range extenders or repeaters at the same time. This is the single most effective step for devices that show as offline, and it costs nothing, which is why it comes before any app step. If you want a sense of how much speed your connection should be delivering before you blame the app, our guide to what is good internet speed sets out the benchmarks, and our 100 Mbps internet speed guide explains what that common plan speed can and cannot support.

Wi-Fi band matters for Nest products. Standard routers use the 2.4 GHz band, the 5 GHz band, or both. Google’s router settings page states that some Nest products, including Nest Protect smoke alarms and first and second generation Nest Learning Thermostats, only work with the 2.4 GHz band. Most Nest products work with 5 GHz networks, but there are exceptions, and a device installed far from the router will usually hold a 2.4 GHz connection better than a 5 GHz one, because the lower band passes through walls more easily. If your router broadcasts one network name for both bands, and a device keeps dropping, try splitting the bands into separate network names and joining the device to the 2.4 GHz network. Google’s setup guidance for thermostats makes the same recommendation: when a router broadcasts separate network names, connect the setup phone to the 2.4 GHz band first, because it has better range and compatibility for setup.

Two more network details are worth checking. Captive portal networks, the kind that ask you to sign in on a web page, and enterprise networks that use 802.1x authentication do not work with Nest products, so a Nest device will never connect on a hotel or office network that uses them. And if your router has a setting called AP isolation or client isolation, turn it off: it stops devices on the same network from talking to each other, which can block the app from reaching a device during setup. If you changed your Wi-Fi password or network name recently, remember that every Nest product needs the new details entered in the app before it can reconnect.

4. Account and Sign-In Problems

If the app opens but will not let you in, the fault is almost always the account, not the app. Work through these checks in order.

Use the right account

Google’s sign-in help is blunt about the first check: make sure you are signing in with the email address you used to sign up for the account, spelled correctly. Passwords are case sensitive, so check capitalization too. Many people have more than one Google account on a phone, and the Nest app may be offering the wrong one. Sign out and sign in again with the account that owns the Nest home.

There is a second account trap that catches long-time Nest owners. If you started using the Nest app before 19 August 2019, you created a separate Nest account. Google later offered the option to migrate that account to a Google account. Migration is optional, and once completed it cannot be undone. If you migrated, you must now sign in with the “Sign in with Google” button and the Google account you linked, not with your old Nest email and password. If you never migrated, you still sign in with your Nest account details. Google’s migration page adds two limits: you can only link one Google account to one Nest account, and you cannot migrate to a Google account already linked to another Nest account. Migrating to a Google Workspace account is possible, but Google recommends a personal Google account for the best experience, and warns that a Workspace admin can access your home and possibly your linked devices. If the app offers a “Migrate to a Google Account” option under Settings, your account has not been migrated yet. If that option does not appear, it already has.

Family members hit a related problem. A person added to a home must accept the home invitation using the same Google account that is signed into the Google Home app on their phone. If they accept with a different account, or if they never accept at all, they will be asked to sign in again and again, or the app will spin when they tap a camera. Check the invitation first, before reinstalling anything.

The spinning ring or blank sign-in screen

A spinning ring, a spinning blue ring, or a blank screen after sign-in is one of the most reported Nest app failures, and Google’s help page gives it its own section. The page’s steps are: check the Nest service status, try a different browser or the Nest app to sign in, check browser add-ons or extensions for ad blockers or VPNs that may interfere, and try a different device. If you are signing in at work, try a different Wi-Fi network, or turn off Wi-Fi and sign in using mobile data. The same page adds a warning that matters: if you can sign in on one device but not another, check the settings of the device that fails, because a browser, network, phone, or router setting on that device may be blocking the sign-in.

Community reports add two practical checks that Google’s support staff repeat in their replies. First, make sure your phone’s date and time are set to automatic. Sign-in security depends on the phone’s clock matching real time, and a clock that is wrong by more than a few minutes can break authentication silently. Second, if you use a VPN, a private DNS setting, or a network filter on the phone, turn it off temporarily and try again. These tools sit between the app and Google’s servers, and they are a common cause of sign-in loops. Both of these come from Google community staff replies rather than from a help article, so they are reported here as staff guidance, not as documented steps.

“Incorrect email address or password”

If the app says your email address or password is incorrect, Google’s help gives four steps: check the email spelling, check the password and its capitalization, check the Nest service status, and reset the password. Tap “Forgot Password” in the app and follow the instructions. Google sends a reset email to the address on the account. If no reset email arrives, you probably typed a different email address from the one the account uses, so check the spelling again and check your spam folder. Do not create a new account to get around a failed sign-in: a new account has no home and no devices in it, and your products will still be linked to the old one.

Repeated sign-in requests

Some owners find the app asks them to sign in every time they open it, then circles back and asks again. Google community staff give the same short list for this loop on Android: update the Nest app from the Google Play Store, restart the phone, clear the app’s cache (Settings, then Apps, then Nest, then Storage and cache, then Clear cache), make sure the date and time are set automatically, and sign in with the same Google account originally used to set up the thermostat. Avoid “Clear storage” or “Clear data” at this stage, because that wipes the app’s saved state and forces a fresh sign-in from scratch. If the loop continues after those steps, try signing in on another device with the same account. If the other device works, the problem is the first phone, not the account.

5. App Version, Cache, and Reinstall

If the account is right and the service is up, the app itself is the next suspect. App problems divide into three kinds: an old version, corrupt temporary data, and a broken install. Each has its own fix, and they should be tried in that order, cheapest first.

Update the app

Open the App Store on an iPhone or the Google Play Store on an Android phone, search for Nest, and install any available update. Google’s sign-in help and its thermostat pages both list updating the app among the first steps, and community staff repeat it in nearly every reply. App updates fix bugs, restore compatibility with new phone software, and occasionally change menu names, so an update can also explain why a step you remember no longer matches what you see on screen. Check for a phone software update at the same time: an old operating system can leave the current app version unstable. Note the date you checked: the steps in this guide match the Nest app as published in November 2026, and a later update may move a menu or rename a setting.

Force close and restart the phone

Force close the Nest app completely, then restart the phone. On an iPhone, swipe up from the bottom of the screen and swipe the Nest app away, then power the phone off and on. On Android, open the recent apps view and swipe the Nest app away, then restart. This clears the app from memory and forces a fresh start, and it resolves the crashes and freezes that come from a stuck session. It is a small step, but Google’s community staff list it before any deeper fix, because a surprising number of “the app will not open” reports end here.

Clear the cache on Android

On Android, the app stores temporary data that can go stale and stop the app from loading. Go to Settings, then Apps, then Nest, then Storage and cache, then tap Clear cache. This deletes temporary files only. It does not sign you out and does not delete your home or devices. Google community staff specifically advise clearing the cache first and avoiding “Clear storage” or “Clear data” until the gentler step has been tried. On an iPhone there is no equivalent cache control, so iPhone owners should skip this step and go to the reinstall below.

Reinstall the app

If updating and clearing the cache do not fix it, delete the app and install it again from the App Store or Google Play. Reinstalling replaces every app file on the phone, which fixes installs damaged by an interrupted update or a corrupt download. It does not delete your Nest home, your devices, or your settings, because those live in your Google or Nest account, not on the phone. After reinstalling, sign in with the same account you used before, and check that your home and devices appear. If they do not, stop: you may have signed in with the wrong account, and the account section above is where the fix lies, not in another reinstall.

Reinstalling is also the point at which to check the phone itself. If the phone is short of storage, the app may fail to update or to save its data. Free space by deleting unused apps or files, then try the update again. If several apps on the phone are crashing, the problem is the phone, not Nest, and a phone repair or a software update is the fix.

6. Device Linking Problems

Sometimes the app works fine and the device is the problem. The app may show a device as offline, refuse to add a new device, or show a device in the wrong home. These are linking problems, and they need device steps, not app steps.

A device shows as offline

First, check whether the device itself is powered and within range of the router. A camera that has lost power, a thermostat that has lost its Wi-Fi connection, and a doorbell with a flat battery all show as offline in the app, and none of them is an app fault. Google’s camera help says to check whether other devices in the home can connect to Wi-Fi, and if none of them can, to call the internet provider. If only the Nest device is offline, restart the device itself, then restart the router using the sequence in section 3.

For cameras and doorbells, bandwidth can be the cause. Google publishes the upload bandwidth each camera model uses, and the figures are higher than most people expect. A Nest Cam (battery) or Nest Cam (wired) uses up to 700 Kbps at High quality, and about 2,000 Kbps, or 2.0 Mbps, during recorded events. At Max video quality the figures rise to 1,000 Kbps, and about 3,000 Kbps during events. A home with several cameras can use several megabits of upload bandwidth at once, and most internet plans offer far less upload speed than download speed. If cameras drop offline when several of them record at the same time, check the plan’s upload speed with the provider, and consider lowering the video quality setting in the app. For the wider picture on wireless security devices that lose connection, see our guide to common pain points in wireless and cellular home security systems, which covers the same failure from the security system side. That guide is a Wave 112 sibling article, so confirm it is live before relying on the link at build time.

A device will not add to the app

Adding a thermostat is the case Google documents in most detail. If the thermostat connects to Wi-Fi but cannot be added to the account, Google’s help gives a fixed sequence: confirm the internet service works, restart the thermostat, and restart the router and modem. For a third generation or earlier Learning Thermostat and for the Nest Thermostat E, the thermostat itself generates a 7-character entry key. On the thermostat, press the ring to open the Quick View menu, turn the ring to Settings, choose Nest app, then Get Entry Key. In the Nest app, tap Settings, then Add product, then Continue without scanning, select the thermostat model, and type in the 7-character key. If the code does not generate, Google’s help says to clear old account connections and make sure the device is on a 2.4 GHz Wi-Fi connection. For the fourth generation Learning Thermostat and the 2020 Nest Thermostat, the app uses a QR code or an alphanumeric key shown on the thermostat screen instead.

Before adding any device, check three phone settings. Turn on Wi-Fi and Bluetooth on the phone, and join the same Wi-Fi network the device should use. On an iPhone running iOS 14 or later, allow local network access for the Nest or Google Home app, or the phone cannot see the device during setup. And if the phone is connected to a VPN, turn it off for the duration of setup. If the app still cannot find the device, turn the phone’s Wi-Fi off and on again and try once more. If the device appears in the app but the setup never completes, move the phone closer to the device and the router, and try again from there. Our guide to how to organize smart home wiring covers the physical side of placement, including keeping hubs and routers where their signal reaches the devices that depend on them.

A device is in the wrong home or missing

If a device appears in the Google Home app but not in the Nest app, or the other way around, check which home is selected. Both apps can hold more than one home, and it is easy to look at the wrong one. Tap the home name at the top of the app and switch to the other home. If the device is genuinely missing, check whether someone else in the household removed it, or whether it was unpaired during the end-of-support change described in section 7. A device that was unpaired by Google cannot be re-added, and no amount of reinstalling will bring it back.

Motion alerts and notifications stop arriving

If the app opens and the devices show as online, but motion alerts or notifications stop arriving, the fault is usually in the phone’s notification settings rather than in the Nest app. Check that notifications are allowed for the Nest app in the phone’s settings, that the phone is not in Do Not Disturb or a focus mode that silences them, and that the app is allowed to run in the background. Battery optimization settings on Android can stop the app from checking for alerts while the phone is idle; exempting the Nest app from battery optimization is a standard fix. For motion detection itself, including sensor placement and false alerts, see our guide to motion sensor security systems, a Wave 112 sibling article, so confirm it is live before relying on the link at build time.

7. The Nest App and the Google Home App Are Not the Same

A common source of confusion is that Google now has two apps, and they do not cover the same devices. The Nest app is the older app. The Google Home app is the newer one, and Google has been moving devices across to it for years. Which app controls a device depends on the model and on when it was set up.

Newer Nest cameras and doorbells are managed entirely through the Google Home app. Google community staff confirm that a newer camera should not normally require the Nest app at all. The 2020 Nest Thermostat and the fourth generation Nest Learning Thermostat are set up in the Google Home app. Older models, including the third generation Learning Thermostat and the Nest Thermostat E, can still be set up in the Nest app, and they appear in the Google Home app only after the Nest account has been migrated to a Google account. If you are tapping a camera in the Google Home app and being sent to a Nest sign-in that spins forever, the likely cause is an account linking problem, not a broken app, and the account checks in section 4 apply.

The sharpest version of this problem is the end of support for the oldest thermostats. Google’s support page states that the Nest Learning Thermostat (first generation, 2011), the Nest Learning Thermostat (second generation, 2012), and the Nest Learning Thermostat (second generation, Europe version, 2014) no longer connect to or work in the Google Nest app or the Google Home app starting from 25 October 2025. From that date the devices were unpaired and removed from the apps, and they no longer receive software or security updates. The thermostat itself still runs its schedule and still changes temperature from its own controls, but remote control, notifications, Home and Away Assist, and voice assistant control are gone. If your app stopped working for a thermostat of this age in late October 2025, that is the reason, and no troubleshooting step will restore it. Google contacted eligible owners in the United States and Canada with an offer on a fourth generation thermostat. Check the model before spending any more time on app fixes: the model and year are printed on the thermostat itself.

The same pattern applies to other retired products. Nest Secure and Dropcam lost support in April 2024, and they no longer work in the app either. If a device vanished from the app around a known end-of-support date, check Google’s support pages for that model before assuming the app is at fault.

8. When to Reset and When to Reinstall

Reset and reinstall sound similar, and they are often confused. They do very different things, and choosing the wrong one wastes time or destroys a working setup.

Reinstall the app when the problem is the app on the phone: it crashes on opening, freezes, or shows a blank screen after sign-in works elsewhere. Reinstalling replaces the app only. Your home, devices, and settings are untouched, because they live in your account. Reinstall first, because it is quick and reversible.

Restart the device when the app works but one device does not respond. A thermostat restart refreshes its connection, and Google’s help lists it as the step before restarting the router. Restarting a device does not remove it from your home.

Factory reset the device only when Google’s help for that model says to, or when every other step has failed and you are prepared to set the device up again from scratch. A factory reset removes the device from your home, deletes its settings, and forces a full setup, including re-entering Wi-Fi details and re-adding it to the app. For a thermostat, the reset option sits in the device’s own Settings menu, and the exact path differs by model, so use the model’s own help page rather than guessing. Never factory reset a first or second generation Learning Thermostat in the hope of restoring app access: those models cannot be added to either app after a reset, because support for them has ended.

In short: reinstall the app for app problems, restart the device for device problems, and factory reset only as a last resort when you are ready to set up again. If you have reached the factory reset stage and the device still will not add, the fault is likely hardware, and the next section applies.

9. Still Not Working

If you have worked through the sections above and the app still fails, gather the facts before contacting support, because support will ask for them. Note the phone model and operating system version, the Nest app version, the exact error message or code, the Nest product models involved, and which steps you have already tried. Note whether the problem affects one device or all of them, and whether it started after a change such as a new router or an app update. Send feedback through the app as well: in the Google Home app, tap your profile picture, choose Feedback, and describe the problem with the date it started. Feedback reports go to Google’s support teams, and they are the route Google asks owners to use when an app failure affects every device in a home.

Contact Google Nest support through the Google Home and Nest Help Center at support.google.com/googlenest. Support can check whether your account has a linking fault that no user-facing step can fix, and can confirm whether a device is affected by an end-of-support decision. Do not pay any third-party service that offers to fix the app remotely. Google’s own troubleshooting is free, and no remote service can do more than the steps in this guide plus the account checks only Google can run.

FAQ

Why is my Nest app stuck on the loading screen?

The usual causes, in order, are a Nest service outage, a broken home internet connection, a sign-in session problem, or corrupt app data. Check the Nest status page first, then test your internet on another device, then force close the app and restart the phone. If the loading screen follows a change of Wi-Fi settings, the app may be waiting on products that can no longer reach the network, so update the Wi-Fi details for your Nest products in the app. Google community staff advise against factory resetting devices for a loading screen, because the fault is usually in the app or the account connection, not in the devices.

Why does the Nest app keep asking me to sign in?

Repeated sign-in requests usually mean the app’s saved session has broken, or you are signing in with the wrong account. Update the app, restart the phone, clear the app cache on Android, and make sure the phone’s date and time are set automatically. Then sign in with the same Google account originally used to set up the thermostat. If you migrated a Nest account to a Google account, use the “Sign in with Google” button and the linked Google account, not the old Nest email and password.

Why is my Nest camera offline in the app?

A camera shows as offline when it has lost power, lost its Wi-Fi connection, or cannot reach Google’s servers. Check the camera’s power and its distance from the router, restart the router, and check whether other devices in the home can get online. If several cameras go offline together, check the upload speed of the internet plan: a Nest Cam can use about 2.0 Mbps of upload bandwidth during recorded events at High quality, and several cameras recording at once can exceed a slow upload connection.

Can I still use the Nest app if I have an old thermostat?

It depends on the model. The third generation Nest Learning Thermostat, the Nest Thermostat E, the 2020 Nest Thermostat, and the fourth generation Learning Thermostat still work in the apps. The first and second generation Learning Thermostats do not: Google ended support for them on 25 October 2025, unpaired them from both apps, and they now work only from their own controls. Check the model and year on the thermostat itself before troubleshooting the app.

Should I use the Nest app or the Google Home app?

Use the app Google assigns to the device. Newer cameras and doorbells, the 2020 Nest Thermostat, and the fourth generation Learning Thermostat belong in the Google Home app. Older thermostats and Nest Protect still use the Nest app. If a device appears in one app and not the other, check that you are looking at the right home, and that the account has been migrated where migration is needed.

Will reinstalling the Nest app delete my devices?

No. Reinstalling the app only replaces the app on the phone. Your home, your devices, and your settings live in your Google or Nest account, and they reappear when you sign in again with the same account. A factory reset of a device is different: it removes the device from your home and forces a full setup, so it should only be used as a last resort.

What should I do if the Nest app works on one phone but not another?

Trust the phone that works: your account and your devices are fine. The fault is in the settings of the phone that fails. On that phone, update the app, check the date and time setting, turn off any VPN or private DNS, clear the app cache on Android, and reinstall the app. If the phone still fails while another phone works, check whether the failing phone’s operating system is out of date.

Sources & references

• Google Home and Nest Help, "Troubleshoot Nest app sign-in issues", support.google.com/googlehome/answer/10506621. Sign-in checks, the spinning ring and blank screen steps, the "Forgot Password" reset flow, and the test of signing in on a different device. Read 11 November 2026.
• Google Home and Nest Help, "Can't connect Nest thermostat to the app", support.google.com/googlehome/answer/9248705. Internet check, thermostat restart steps, the 7-character entry key for third generation and earlier models, and the router restart sequence (unplug, wait 30 seconds, plug back in). Read 11 November 2026.
• Google Home and Nest Help, "Update Wi-Fi network and router settings", support.google.com/googlehome/answer/9240155. Recommended router settings, the 2.4 GHz only limit for Nest Protect and first and second generation Learning Thermostats, and dual-band guidance. Read 11 November 2026.
• Google Home and Nest Help, "End of support for Nest Learning Thermostats (1st and 2nd gen)", support.google.com/googlehome/answer/16233096. Support ended 25 October 2025 for the 2011 first generation, 2012 second generation, and 2014 second generation Europe models; devices unpaired and removed from both apps; no further software or security updates. Read 11 November 2026.
• Google Home and Nest Help, "Migrate a Nest account to a Google Account", support.google.com/googlenest/answer/9297676. Migration optional and irreversible, one Google account per Nest account, a personal Google account recommended for the best experience (migrating to a Google Workspace account lets the Workspace admin access the home and linked devices), and the 19 August 2019 date after which new users are already on a Google account. Read 11 November 2026.
• Google Home and Nest Help, "Learn about internet bandwidth and speed requirements for Nest cameras", support.google.com/googlehome/answer/9245832. Nest Cam (battery) and Nest Cam (wired) upload bandwidth: High 700 Kbps, about 2,000 Kbps (2.0 Mbps) during recorded events; Max video 1,000 Kbps, about 3,000 Kbps during events. Read 11 November 2026.
• Google Home and Nest Help, "Fix Nest thermostat connection to Nest app or Wi-Fi (TD error codes)", support.google.com/googlenest/answer/9703157. TD error codes in the app and the hotspot test for isolating a home Wi-Fi fault. Read 11 November 2026.
• Google Home and Nest Help, "Fix issues with your Nest camera or doorbell Wi-Fi", support.google.com/googlehome/answer/9239727. Camera offline checks, bandwidth, restart, and router restart steps. Read 11 November 2026.
• Nest status page, status.nest.com. Current service status by service. Read 11 November 2026: "Everything is running smoothly" as of 3:54 PM PST.
• Google Home and Nest Help Community, staff replies on Nest app loading screen, sign-in loops, and spinning ring failures, support.google.com/googlehome. Clear cache path (Settings, Apps, Nest, Storage and cache, Clear cache), automatic date and time, and VPN and private DNS checks. Community content, used as staff guidance and flagged as such in the ledger.