Hi everyone,
I’m Alex – the original poster from this thread about mobile presence suddenly stopping on our Galaxy S22 Ultra.
We’ve now gone over five weeks without SmartThings being able to trigger any presence-based automation. After years of consistent performance, this feature just died, and nothing I’ve done has brought it back.
Here’s what we’ve tried (spoiler: everything)
Reinstalled SmartThings app
Cleared cache + wiped phone cache partition
Reset permissions (location: always on, precise location on, no battery optimization)
Toggled ‘Get location from this phone’ repeatedly
Changed geofence radius & map location
Deleted and re-added presence devices in SmartThings Advanced Web App
Downgraded to older versions of the SmartThings app (1.8.28.21)
Tried brand new Samsung account + new phone to isolate the issue
Presence still fails on both S22 Ultra and an additional test phone
Tried Samsung Find, which does see the phone’s location (but SmartThings doesn’t use it reliably)
Created and tested virtual presence sensors (these work with routines manually)
Current State
presence attribute in the SmartThings Web UI shows as null for both original and new test devices
Routine works only when triggered manually or by using the virtual presence sensor
All phones are running the latest Android & SmartThings versions
SmartThings notification often shows “Updating location info…” indefinitely – this never used to happen
Samsung support has been… let’s just say, unhelpful. I’ve been bounced between TV, soundbar, and washing machine departments ![]()
Ask to the Community & Samsung Engineers
Can someone from the SmartThings team PLEASE help us understand if:
Mobile presence is broken globally?
This is a backend bug introduced in May?
Is there a fix coming?
Can someone from Samsung acknowledge this and escalate it?
Also: Anyone else still affected?
If you’re seeing broken mobile presence on your device(s), PLEASE comment below to get this some visibility. Let’s make some noise so we can get a proper response and a fix!
Thanks to everyone who’s offered support so far — but this is way past the “try rebooting” stage. Hoping someone with technical access sees this ![]()