Geofencing issues after iOS update

[wenklaw]

So geo fencing had been working for well over a year and now it’s not, anyone else ??

I knew it was only a matter of time until Arlo broke something again, useless 

[dcollas]

Same for me in two locations/accounts. Driving me crazy trying to set up the app differently because I thought it was a bad update but nothing... Was an Arlo lover but things are working every update worst...!!

[Alouis]

Same here. Just posted a new message myself with the same problem. Geofencing broke since 22 May. 
Did a search on geofencing sorted by date but this thread didn’t show up in the search results. 

same iOS and Arlo app version as stated above

[lengoyeko]

Anyone else’s “Arrive/Leave” geofencing automations just stop working after the iOS 26.5 update?

I’ve tried all the suggested troubleshooting steps and it’s still not working… location settings, logging out and reinstalling app. Nothing…

Any fixes?

[StephenB]

---

@Ttonim wrote:

I don’t think the old iPhone is the issue. When I left the area, I either took the old iPhone with me or it was completely switched off.

---

The normal approach for geofencing is to switch the system to Arm Away when all the devices leave, and switch back to Arm Home when anyone arrives.  This requires only two automations.  The "Leave" automation is an "and" operation - triggering when all devices in the geofencing list have left.  "Arrive" is an "or" operation - triggering when any device on the list returns.  "Arrive" should only be enabled when the system is already in "Arm Away".  "Leave" can usually be enabled in all modes, but you can disable it in "Arm Away" if you like.

If the old phone is in the geofencing device list and switched off when home, then the system will never detect the old phone as leaving.  So this normal approach won't ever work.  So you really do want to keep the old phone off the list.

---

@Ttonim wrote:

I also created the automation separately for each iPhone. 

---

Can you explain what you did, and the "why" behind it?  I am thinking that might factor into the issues you are having. The only reason I can think of to have separate automations for each phone is if you want to have the system switch to "Arm Away" when anyone leaves (not waiting for everyone to leave). Then you'd need separate "Leave" automations for each phone.  Separate "Arrive" automations don't really accomplish anything, but would do no harm.

That said, several folks are reporting geofencing issues with iOS 26.5 

[AlexWhi]

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

[AlexWhi]

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

[AlexWhi]

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

[AlexWhi]

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

[wenklaw]

Mate Arlo are to blame, my settings have been working for months and now they don’t.  

Arlo clearly employ muppets and don’t test updates end of effing story.  I work in national infrastructure,

of anyone applies for a job and includes Arlo on their CV they can jog on

[StephenB]

---

@AlexWhi wrote:

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

---

FWIW, it similarly failed to switch for me yesterday and earlier today.  So there is something wrong with the combination of iOS 26.5 and version 6.28 of the app.

[Rbmx1980]

Same here…

got everything working 100% after the app update and fought finally everything working 100%. Now on Saturday after iOS update not working anymore. Tried all the “workarounds” as you so let’s hope Arlo got a fix asap🙏

[Rbmx1980]

Same here...

Tried all "workarounds", but still the same.

[lamartin]

Mine actually stopped working without the iOS update.  I was away for a few days, and it was working fine and had switched to the "Away" mode.  However, on Saturday, I noticed it had switched back to "Home" mode.  I tried a lot of things to get it back to recognize I was away but nothing worked (switched geofencing off/on, changed geofencing range, insured location services were on, restarted phone, etc.).  I had to manually change the mode to "Away".  Since it already was not working, I have just updated to iOS 26.5 to see if that will help.  Based on the comments here, I suspect it will not.

[Ttonim]

---

@StephenB  schrieb:

---

---

The normal approach for geofencing is to switch the system to Arm Away when all the devices leave, and switch back to Arm Home when anyone arrives.  This requires only two automations.  The "Leave" automation is an "and" operation - triggering when all devices in the geofencing list have left.  "Arrive" is an "or" operation - triggering when any device on the list returns.  "Arrive" should only be enabled when the system is already in "Arm Away".  "Leave" can usually be enabled in all modes, but you can disable it in "Arm Away" if you like.

If the old phone is in the geofencing device list and switched off when home, then the system will never detect the old phone as leaving.  So this normal approach won't ever work.  So you really do want to keep the old phone off the list.

I had it configured exactly this way before the new update, and it worked perfectly all the time.
I only use the geofencing automation when leaving the area, not when arriving. I have now completely removed the old iPhone from the device/geofencing list, but the problem still persists even after removing it.

---

@StephenB  schrieb:Can you explain what you did, and the "why" behind it?  I am thinking that might factor into the issues you are having. The only reason I can think of to have separate automations for each phone is if you want to have the system switch to "Arm Away" when anyone leaves (not waiting for everyone to leave). Then you'd need separate "Leave" automations for each phone.  Separate "Arrive" automations don't really accomplish anything, but would do no harm. 

That said, several folks are reporting geofencing issues with iOS 26.5 

I configured it this way so that if someone is manually or accidentally switched to “present/home”, leaving the zone afterwards would still correctly switch the status back to “away/not present”.

That was the reason for the separate automations, and it worked reliably before the recent update.

[Ttonim]

---

@StephenB  schrieb:

---

@AlexWhi wrote:

Ditto, geofencing has died for me. Opening the relevant automation and hitting “test” causes it to notice and switch to the correct state but there is no longer any automatic switching.

---

FWIW, it similarly failed to switch for me yesterday and earlier today.  So there is something wrong with the combination of iOS 26.5 and version 6.28 of the app.

Exactly. If multiple users are experiencing the same issue with iOS 26.5 and app version 6.28, then this is obviously not an isolated problem anymore, but a bug that Arlo needs to acknowledge and fix as soon as possible.

And honestly, as paying customers, we should not have to spend hours trying to get basic functionality working again when it worked perfectly fine before. With a Secure Plus subscription, it’s completely reasonable to expect core features to remain reliable even after app updates.

I also couldn’t find any proper way to create a real support ticket. You either end up with the AI chat, which is not particularly helpful in cases like this, or you are told to call support — which is not an option for me either.

So this is a serious question: How can customers actually create a proper support ticket with Arlo or escalate an issue directly to technical support — especially as a paying Secure Plus customer?

---

[wenklaw]

Nearly a week now, fix the problem.  Geofence worked now it doesn’t meaning my security system is pointless.  Arlo you are a bunch of clueless idiots.

[Edinburgh_lad1]

I find your language inappropriate. 

[whatdidipayfor]

Thankful to hear that I'm not the only one... 

Not only is geofencing completely broken (yes, I've tried logging out of the app, cleaning up geofencing devices, deleting the app and all of the other troubleshooting steps) but HomeKit camera feed is also useless. Meaning - no thumbnail refreshes in the Home App and insanely long wait times to open a live stream (tested on iPad OS, iOS, TVOS). All devices are within 1 to 2 years old, updated to current OS versions and were working properly until recently.

[wenklaw]

I apologise.  Just very frustrating, if I could remove the post I would but it appears I can’t.  
I shall refrain from making personal comments and foul language in future and keep it civil. 

[Hashman]

Having the same issues since the new update. Geofencing works when testing the automation but not in the real world. Have tried everything.

[LeSage]

Same here nothing to do Geofencinf doesn't work anymore since 6.28.. GRRRrrrrrrrrr.......

[JoeyRG]

Hi,

I spent over 2 HRS On teh phone with Tech support 2 different agents and the only thing they had me do was change the Geofence radius from Med to Small. 

Currently the Arrive leave option is not working, i have to manually turn my cameras off and on. I like them to shut off when I get home so the batteries don't drain so fast. this feature has worked fine for over 4 years but stopped sometime in the last few days. I have rebooted the base many times and I have also confirmed phone and app setting.

I can't get into teh Automation part on teh web page as it just spins but I can on the phone app.

Any help would be great.

Thanks

[StephenB]

---

@JoeyRG wrote:

I spent over 2 HRS On teh phone with Tech support 2 different agents and the only thing they had me do was change the Geofence radius from Med to Small. 

---

Are you using an iPhone?  Several folks have posted issues with iOS 26.5 and the current app.

[StephenB]

---

@Ttonim wrote:

I also couldn’t find any proper way to create a real support ticket. You either end up with the AI chat, which is not particularly helpful in cases like this, or you are told to call support — which is not an option for me either.

So this is a serious question: How can customers actually create a proper support ticket with Arlo or escalate an issue directly to technical support — especially as a paying Secure Plus customer?

---

Those are the two ways.  Not sure why calling support is not an option for you.

Though Arlo has to know about this issue - I'm tagging the mods -  @BrookeN , @ShayneS , @JamesC  - in hopes they can provide an update.

[JoeyRG]

Yes I am IOS 26.5