Hey! We’ll figure out why your Nest isn’t saving settings and stop them from reverting. Quick questions so we hit the real cause (app sync, permissions, or thermostat features):
• Which Nest device: Nest Thermostat, Nest Learning Thermostat, or something else? And are you changing settings in the Google Home app or the Nest app?
• What exactly won’t stick: temperature schedule, Eco temps, fan schedule, Home/Away (Presence Sensing), notifications, or “Away” toggles?
• Do you see an error like “Unable to save settings”, or does it save, then silently changes back later (schedule keeps reverting)?
• iPhone or Android? Any recent update to the Home app, Nest app, or thermostat firmware?

Once I know that, we’ll do a complete fix: check internet/app sync, confirm the right “Home”, fix permissions (location/background), and turn off features like Auto-Schedule that can override your changes.

Got it — when Nest settings won’t save in the Google Home app, there are a few repeat offenders, and the symptoms you described match them well:

Common reasons Nest settings revert or don’t stick
• Auto-Schedule / Nest Sense is learning and quietly rewriting the schedule (it can “undo” your manual edits).
• Presence Sensing / Home & Away has conflicting signals (phone location permissions, multiple home members, or old devices still deciding if you’re home).
• The thermostat is online “sometimes” — Wi-Fi drops, DNS issues, or a weak 2.4 GHz connection → the app looks like it saved, but the device never receives the update (classic app sync problem).
• The Home app doesn’t have the right permissions (location “always”, Bluetooth, background data) or the phone is battery-optimizing it, so changes don’t push reliably.

We’ll fix it in a clean order: confirm the thermostat is truly online, force a fresh sync, then lock down the features that override your edits.

Perfect — first we make sure changes can reliably reach the thermostat. Even if the screen says “connected”, a flaky network can cause Nest app changes not saving because the cloud sync doesn’t complete.

Step 1 — Confirm the thermostat is truly online (not “partially connected”)
1) In the Google Home app, open the thermostat → check if it shows “Offline” at any point or if controls lag.
2) On the thermostat itself, go to Settings → Network and confirm it’s on your main Wi-Fi (not a guest network).
3) If you have mesh/extenders, keep the thermostat on a stable node. Nest thermostats typically behave best on a consistent 2.4 GHz signal (not bouncing between bands).

Step 2 — Force a clean app sync on Android
• Settings (phone) → Apps → Google Home → Storage → Clear cache (cache only first).
• Reopen Google Home, then try changing one setting (like Eco temp) and wait 30–60 seconds before backing out.

After this, we’ll handle the #1 reason schedules “revert”: Auto-Schedule / Nest Sense.

That’s the key. If Nest schedule keeps reverting, it’s often because “learning” features are still enabled. Depending on model, you’ll see names like Auto-Schedule, Nest Sense, or “Learning”.

Step 3 — Turn off Auto-Schedule (prevents settings from changing back)
1) Open Google Home app → Thermostat → Settings (gear).
2) Look for Auto-Schedule (or Nest Sense / Learning). Turn it OFF.
3) Also check for features that can override temps:
  • Eco (Eco temps can trigger when Home/Away says “Away”)
  • Home/Away routines (presence-based changes)
  • “Early-On” / “Sunblock” (model-dependent) if they affect comfort targets

Step 4 — Rebuild your schedule once learning is off
After disabling Auto-Schedule, edit the schedule again (set a few points), then wait a minute and reopen Schedules to confirm they stayed. This prevents the “I saved it, but it reverted later” loop.

Yep — when Nest not saving Home/Away settings or it flips to Away unexpectedly, it’s usually not the thermostat at all; it’s the Presence Sensing signals (phone location, other members, or an old device still “deciding”). Let’s lock it down so it stops overriding Eco and schedule behavior.

Step 5 — Fix Presence Sensing / Home & Away (Google Home app)
1) Google Home app → Settings → Home features → Presence sensing.
2) Make sure only the correct phones are allowed to contribute location for this home (remove old devices).
3) Confirm each phone has permissions:
  • Location: Allow all the time
  • Precise location ON (if available)
  • Background data allowed for Google Home

Step 6 — Android “battery optimization” can break saving/syncing
On Android: Settings → Apps → Google Home → Battery → set to Unrestricted (or “Don’t optimize”). If the OS puts the Home app to sleep, presence updates lag, and your home can flip to Away even while you’re home — which then triggers Eco temps and makes it feel like your Nest settings won’t stick.

After this, Home/Away should behave consistently. Next we’ll fix the mesh/Wi-Fi angle so the thermostat sync stays stable.

Absolutely — unstable Wi-Fi is a top cause of Nest settings not syncing. A thermostat can look “online” but still struggle to maintain a clean cloud connection, especially on busy mesh networks.

Step 7 — Make Nest connectivity boring (that’s what we want)
• If your mesh uses a single SSID for 2.4/5 GHz, try to keep the thermostat on a consistent connection (many users stabilize Nest by ensuring it stays on 2.4 GHz, since range is better through walls).
• Avoid guest networks, AP isolation, or “client isolation” features — they can interfere with device control and discovery.
• If your router has DNS filtering or “family safety” DNS, test turning it off briefly. DNS issues can cause delayed settings sync and make it seem like “changes won’t save.”
• Reboot the main router/primary node (not every node at once) and then power-cycle the thermostat (restart, not factory reset yet).

If you tell me your mesh brand (Eero/Deco/Orbi/Google Wifi/UniFi), I can name the exact toggles to look for (band steering, fast roaming, WPA3-only, etc.).

Yes — you can “clean rebuild” the schedule without wiping the whole thermostat. Duplicates or old setpoints showing up usually come from partial sync history or mixing edits between apps (Home vs Nest) when an account is mid-migration.

Step 8 — Clean schedule rebuild (without a full factory reset)
1) Pick one app to manage schedules (prefer the Google Home app if that’s what your model uses). Avoid editing schedules in multiple places because that can reintroduce old points.
2) In the Schedules view, delete extra/duplicate points for a single day first (keep it simple: 2–3 setpoints). Save, then reopen to confirm it stuck.
3) Copy that day to other days (if your model supports copy) instead of manually recreating 7 separate schedules — fewer edits = fewer sync conflicts.
4) Give it a minute after saving. With cloud devices, immediately backing out and making rapid changes can look like “not saving” when it’s really still syncing.

If duplicates keep returning, the next step is a light reset: restart the thermostat + sign out/in of the Home app (and only then consider deleting/re-adding the thermostat to the Home).

Totally fair — here’s the safest “last resort ladder,” from least disruptive to most disruptive, so you don’t jump straight to a factory reset unless it’s truly needed.

Last resort ladder for settings that won’t save
1) Restart the thermostat (not factory reset): on most models, you can restart from the device settings menu. This clears temporary glitches after firmware/app updates.
2) In Google Home app: clear cache again, then force stop the app and reopen (Android). Confirm permissions still allow background location.
3) Remove and re-add the thermostat to the correct “Home” (only if it’s clearly tied to the wrong home or multiple homes). This often fixes weird ownership/sync issues where settings apply but don’t persist.
4) Factory reset the thermostat only if it’s stuck in a corrupted state (settings revert instantly, repeated duplicates, or the device won’t take any changes). After reset, set it up fresh in one app (Google Home) and keep Auto-Schedule off if you want manual control.

If you tell me your exact thermostat model, I can give the exact restart/reset path and what settings to screenshot before you do it.

Great outcome — and it makes sense: most “Nest not saving settings” cases are actually Auto-Schedule overrides plus Presence Sensing + permissions (and Android battery optimization) causing Home/Away to flip and trigger Eco changes.

Summary: confirm the thermostat is truly online, clear the Google Home app cache, turn off Auto-Schedule / learning, fix Presence Sensing permissions (location always + background), disable battery optimization, and keep edits in one app. If schedules still duplicate or revert, restart the thermostat, then re-add it to the correct Home as a last resort.

Want me to tailor this to your exact Nest model + mesh router? Open the chat and we’ll lock it down step by step.