Network technician helping fix WiFi mesh restarting issues

Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: presence sensor false occupancy, home/away detection drift, phone-based geofencing checks, smart home hub status sync, motion vs presence logic review.

What to check first when home occupancy stays stuck on “someone is home” after everyone left

Technician avatar Technician
Let’s start with the safest checks first, because “someone is still home” can mean a few different things in smart home systems.

I do not want you changing every automation at once. The best first step is to find out whether this is a real sensor reading, a phone location issue, or a delayed home/away status in the app.

When did it start, and what type of system is deciding that someone is home: a dedicated presence sensor, a smart hub, phone geofencing, or a mix of those?
Customer
It started this week. We use Home Assistant with presence based on our phones and one room sensor. After everyone leaves, it still says one person is home for hours.
Technician avatar Technician
That helps, because now we know this may not be the room sensor alone. A lot of false “someone is home” cases come from phone tracking not clearing properly after an app change, battery setting, or network handoff.

Two things matter first:
1) Is it always the same person shown as home?
2) Did anything change recently, like a phone update, app permission change, router change, or battery-saving setting?
Customer
Yes, it is usually my wife’s phone that still looks home. Her iPhone updated a few days ago, and I think low power mode has been on more often too.
Technician avatar Technician
That timing is important. This is common after updates, but we should rule out risks before blaming the phone completely.

Let’s separate the sources of “home” status:
• Does the room presence sensor itself still show motion or occupancy after you leave?
• Or is the house marked occupied only because that one phone never fully changes to away?
Customer
The room sensor looks normal. It clears. The home status stays occupied because her phone still reports home.
Technician avatar Technician
Good, that narrows it down a lot. If the room sensor clears but the person stays home, the problem is probably in location tracking, app background access, or a delayed device tracker state.

Trust moment: I would not delete and rebuild the whole presence setup yet. That often creates more confusion and hides the original cause.

When she leaves home, does her phone disconnect from Wi-Fi right away, or does the app still show it on the home network for a while?
Customer
I checked once today, and it looked like the phone stayed connected in the app longer than expected. Not forever, but longer than normal.
Technician avatar Technician
That can matter. Some home/away logic blends Wi-Fi presence with GPS or app location, and if one source lags behind, the person may remain marked home even after leaving.

Another simple check: after she leaves, does the map location in the phone app update correctly, but the person entity still stays home? Or is the location itself stale too?
Customer
The map seems stale sometimes. It can show near home for a while even when she is already across town.
Technician avatar Technician
Then the issue may be upstream from the presence sensor label itself. A stale phone location often points to app refresh limits, reduced location permission, low power mode, or background updates not running when the phone leaves the geofence.

Let’s check the safe basics before touching automations:
1) Is location access set to Always, or only While Using?
2) Is precise location allowed?
3) Does low power mode stay on most of the day?
Customer
I think it is set to While Using, not Always. Precise location may be off too. And yes, low power mode is on a lot lately.
Technician avatar Technician
That combination fits the pattern very well. The app may not be getting enough background location updates to tell the house she has left, especially after an iPhone update changed or tightened permissions.

I also want to rule out a misleading network clue: does the status usually get stuck only when she leaves quickly, like driving away, or even when she walks out and stays nearby for a few minutes?
Customer
It seems worse when she drives off quickly. If she is outside a bit longer, it sometimes updates sooner.
Technician avatar Technician
That is a strong clue. If a phone leaves the Wi-Fi area fast and background location is limited, the system can miss the clean handoff from “home network” to “away.” Then the person entity hangs in a home state longer than it should.

Let’s not assume it is only the phone, though. Do you use any Bluetooth beacons, router-based trackers, or another app that also feeds presence into Home Assistant?
Customer
No Bluetooth beacons. Just the companion app and Wi-Fi-based tracking from the router integration.
Technician avatar Technician
That makes sense. With those two inputs, one stale source can keep the house occupied even if the room sensor is already clear.

Trust moment: do not change both the router integration and the phone settings at the same time. One change at a time will tell you which source is really keeping the home status stuck.

In your history view, do you see the person entity stay home first and then the router tracker finally drop later, or is it the phone app location that lags first?
Customer
Looking back, the phone app location lags first. Then the router tracker clears later, and only after that the person finally changes to away.
Technician avatar Technician
That is a very useful pattern. It suggests the stuck “someone is home” state is not a ghost occupancy problem inside the house. It is more likely delayed phone location plus a second tracker that also takes time to clear.

The safest next step is to review permissions and background behavior on that phone, then compare one leave-home test with careful notes. If the phone location updates cleanly, you can see whether the router tracker is still adding extra delay or whether the person logic itself needs review.
Customer
That makes a lot more sense now. I was thinking the sensor was broken, but it sounds more like the home/away sources are disagreeing after the phone update.

Quick answer: the accepted fix

Accepted first approach when a presence sensor keeps saying someone is home after everyone already left:
• Separate room occupancy from person tracking to confirm whether the problem is a sensor reading or a delayed home/away source
• Check recent changes such as phone updates, low power mode, background app limits, or location permission changes
• Compare Wi-Fi presence, app location, and person entity history to see which source lags first
• Change only one tracking source at a time so you can tell whether the false home status comes from the phone, router, or combined logic
• Keep one short leave-home test with notes instead of rebuilding all automations at once


Why home occupancy can stay stuck after everyone leaves

False “someone is home” status often comes from delayed phone location updates, Wi-Fi presence that clears late, or combined person logic that waits for more than one tracker to agree. This can become more noticeable after a phone update, battery-saving changes, or app permission changes. A room sensor may be working normally while the home status is still wrong.

What to check first without breaking your automations

Start with simple checks: which person stays home, whether the room sensor clears normally, and whether the app map or router tracker lags after leaving. Review location permissions, precise location, and background behavior on the affected phone before changing the whole setup. Small controlled tests give better answers than resetting everything at once.

Tip: don’t rebuild presence tracking until you know which source is stuck

A wrong home status is often one delayed tracker, not a fully broken system.

If the person entity stays home but the room sensor already cleared, the problem is usually in phone location, Wi-Fi presence, or the logic that combines them. A careful history check often shows which source lags first. That saves time and avoids creating new automation problems.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by smart home platform, phone settings, and router integrations. For exact instructions for your setup, consult the manufacturer’s support site.

Understand what these prompts mean


Getting Started Is Easy

Low-risk diagnosis first

Focus on safe checks (Ethernet comparison, Wi-Fi re-join, and roaming/security review) before resets or major network changes.

Identify what changed

Updates on the TV or router can change Wi-Fi behavior. Notes on timing and symptoms help you isolate the real trigger.

Avoid “random fixes”

Changing one variable at a time prevents new problems and makes it clear which step improved stability.

FAQ

Why does my presence sensor say someone is home when nobody is?

This often happens when phone location, Wi-Fi presence, or person logic updates late. The house can stay marked occupied even after everyone leaves. A room sensor may not be the real problem.

Did this happen after a phone update or settings change?

It can. App permissions, precise location, and low power mode can all affect home and away tracking. This is especially common after phone updates or battery-saving changes.

Is this a sensor issue or a tracking issue?

It depends on which source stays active. If room occupancy clears but one person still shows home, the issue is usually tracking rather than the sensor itself. History logs help show which source is lagging.

Can this be checked safely at home?

Yes. Start by comparing the room sensor, person entity, and phone location history after a simple leave-home test. Make one change at a time so you can see what really affects the result.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant