Hey! We’ll figure out why SmartThings is not saving settings and why changes keep reverting. To fix this fast (without guessing), I need a few specifics because the cause can be app sync, account/location, hub firmware, or even a SmartThings cloud sync hiccup:
• What exactly isn’t saving: device settings (like switch behavior, dimming level, thermostat mode), automations/routines, scenes, or notifications?
• When you change it, does it “save” then revert after refresh, or does it fail immediately with an error?
• Are you on Android or iPhone? (permissions/background refresh/battery optimization can break syncing.)
• Do you have a hub (Samsung SmartThings Hub / Aeotec Smart Home Hub) or are devices cloud-to-cloud (Hue, Kasa, Ring, etc.)?
Share one example like: “I change X, tap Save, and it flips back after Y minutes.” That pattern tells us where the settings are getting lost.

Thanks — that “saves, then reverts” pattern is important. When SmartThings routines not updating and device settings reset, it usually means the change isn’t being committed to the correct place (cloud vs hub vs driver) or the app isn’t completing a sync cycle. Common triggers are:
• The app is running in a restricted mode (Android battery optimization, background data limits), so it looks like you saved, but the final sync never finishes.
• A location mismatch (multiple locations/homes, or you’re editing under one location and viewing another) — super common if you’ve ever migrated or created a second “Home.”
• Hub/driver layer: some Edge drivers and certain device options will display a value, but the device rejects it, so the UI snaps back on refresh.
• SmartThings cloud status issues can cause “ghost saves” where the UI accepts the change and then rolls it back later.

We’ll do a fast set of checks to narrow it down to the right bucket — but I’ll avoid making you do a long reset spiral unless it’s truly needed.

Perfect — we can test this quickly with “save verification” without fully rebuilding anything.
Fast check A — confirm the save actually reaches the cloud
1) Edit ONE routine (small change like rename it or toggle a simple condition). Tap Save.
2) Immediately force-close the app, reopen it, and check if the change is still there.
3) Then check the same routine from another device if you can (tablet / spouse’s phone / web view if you use it). If it differs across devices, that screams SmartThings app not syncing rather than the routine itself.

Fast check B — Android restrictions that silently break SmartThings sync
On Android, SmartThings can “look” fine while background activity is limited. Without changing your whole phone setup, just verify these are not blocking sync:
• Background data allowed for SmartThings
• Battery usage set to “Unrestricted” (or at least not “Restricted”)
• No VPN/ad-block DNS that might interfere with account calls (this can cause routine edits to roll back)

Don’t worry — I’m not asking you to nuke cache or reinstall yet. We just want to see if we’re dealing with a sync/permission issue versus a routine engine issue.

That’s a great clue: “simple edits stick, but presence/time conditions vanish” is a very specific SmartThings behavior pattern.
It often points to one of these (we’ll confirm, not assume):
• The condition is tied to a specific Location or Member permissions, and SmartThings later validates it and removes it if something doesn’t line up (presence sensor/account access).
• A presence source (phone presence, SmartThings Find, member location) is failing intermittently — so the routine engine discards the condition after validation.
• For time windows, the phone’s time/region settings or location services can cause a routine to “normalize” back if it can’t store it reliably (rare, but I’ve seen it).

For the device option (dimmer “ramp rate”) resetting: that’s often a device driver / Edge driver compatibility issue. The UI lets you pick the option, but the device rejects the command or doesn’t report it back, so it snaps back on refresh.

The fastest path is to identify whether your dimmer is using an official driver, a community Edge driver, or a migrated handler — because the fix depends on that layer. We can do that without changing your setup yet.

Two locations is *exactly* where I see “SmartThings automations not saving” confusion happen — because routines, members, and presence are all location-scoped.
Fast check C — confirm you’re editing the correct SmartThings Location
• In the SmartThings app, switch locations and confirm the Hub name and device list match your home (don’t rely on the home name alone).
• Open the routine and verify the devices referenced in the condition belong to the same location. If a routine references a device/presence source not valid for that location, SmartThings may “clean” the condition later — which looks like it didn’t save.

Fast check D — identify the driver layer (critical for “device settings reset”)
• Open the device in SmartThings → Device details → look for driver information (often under a “Driver” or “About” style area).
If it’s a community Edge driver, some preferences are UI-only or partially supported depending on firmware, so they revert after refresh.

I’m keeping this high-level on purpose because the exact steps differ by hub model, driver, and Android version. In chat, we can pinpoint the exact driver + presence source and tell you *why* it’s reverting in your case.

Yes — and you’re not imagining the “random” part. When people report SmartThings changes not saving right after an app update, it can be a mix of:
• Temporary SmartThings cloud sync delays (routine edits are cloud-based, so they’re sensitive to outages/latency).
• Token/session issues after an update (your app “saves” locally, but the session fails to commit the edit).
• Presence services failing to validate, causing presence-based conditions to be removed later.

Here’s the quickest non-destructive test without wiping anything:
1) Check whether SmartThings is showing any ongoing incidents on its status page.
2) Make a small routine change, then immediately test it with a manual run (if it runs differently than what the routine shows, you’re seeing a desync).

The reason I’m not giving a single “do X and you’re done” is that the *same symptom* (settings reverting) can come from three different layers. In chat we can identify which one you’re hitting in under 5 minutes with the right screenshots/details.

Totally fair — we’ll keep it minimal-risk and focused on SmartThings not saving routine settings.
Fastest “safe” path (no re-pairing, no factory resets)
• Make sure SmartThings can sync reliably: background data ON + battery restrictions OFF (you already started that).
• Confirm you’re editing the correct location AND that the presence members used in conditions belong to that same location.
• Avoid editing multiple routines back-to-back rapidly right after an update (sounds silly, but when sync is flaky, changes can collide and revert). Edit one, wait a minute, then verify it persists after a refresh.
• If the routine condition is presence-based, we should verify the presence source is healthy (phone permissions, location accuracy, and membership). This is the #1 reason “only if someone is home” disappears later.

If you want, open the chat and tell me:
1) the exact condition that disappears (presence/time/other),
2) your hub model (Samsung vs Aeotec), and
3) whether the routine is set to run “Local” or “Cloud” (if you see that option).
With that, I can tell you the precise cause without trial-and-error — and we can fix it without rebuilding your smart home.

Yes — notification toggles can be affected by both app permissions and account sync. On Android, if SmartThings can’t maintain background sync, it may revert notification preferences after a refresh (especially after an update). Also, some notification rules are tied to the location and to the member profile — so if you’re switching locations or profiles, it can look like settings “won’t save.”

The fastest way to nail it is to identify whether your revert is:
• UI-only (app shows it changed, then snaps back),
• account-level (different across devices), or
• rule-level (only certain triggers like presence/time vanish).

If you open the chat, I’ll ask for 2 screenshots (routine condition screen + your SmartThings location selector) and we’ll isolate the cause quickly — then you won’t have to keep redoing routines or device preferences.

Summary: when SmartThings is not saving settings, the “revert after refresh” usually means a sync/validation issue across app ↔ cloud ↔ location/presence ↔ hub/driver. The fastest way to solve it is to confirm the correct location, ensure Android isn’t restricting SmartThings, and identify whether the failing settings are routines/automations vs device preferences (Edge driver layer). Want the quickest answer for your exact setup? Open the chat and an expert will pinpoint the real cause and the safest fix.