Geofence Automations No Longer Working After New Arlo App 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 

[ShayneS]

Thank you all for the continued feedback. I provided all of your additional  information to the team, and I will report back as soon as possible. 

[ShayneS]

We have identified the issue where Geofencing (Arrive/Leave) automations may stop triggering automatically. A fix has been developed, tested, and confirmed working. It is currently awaiting Apple review and will be available soon. I will continue to provide updates here. Thank you for your patience

[ShayneS]

The Arlo development team is currently investigating reports of this behavior. We will provide an update as soon as we have more information to share with the community.

[ShayneS · Accepted solution]

Thank you for your patience while we worked towards a resolution. This symptom should now be resolved with the latest version of the App 6.29.1

Make sure you have the latest version from the App Store. If you're still experiencing these symptoms, please let us know.

[Patzum]

Geofencing is still not working

[mariospk]

Updated to the new Arlo app this morning, and so far it is working FINE!!

[wenklaw]

Updated the app this morning on both iOS devices and geofencing is now working again.  Well done Arlo, I never doubted you😎

[Mr_GHW]

Hi,

Have the same problem. Downloaded latest Arlo app IOS now hope it will be settled when testing it later.

Allow me a few comments:

When something doesn't work anymore and it worked before and you need to fix it, why not having a notice board telling what is not working and update with progress of fixing the issue?

And why not including a few meaningful words of what has been fixed instead of this ever the same and absolutely  meaningless "General stability, bug fixes and performance improvements" wording in your app updates?

It would save lots of user complaints, user frustration and endless user troubleshooting whilst Arlo is aware that all of attempted troubleshooting by users is actually fruitless.

Even a short notice informing that there might be an issue and Arlo is investigating it would prevent tons of users desperately trying to figure out what settings might be wrong..

It surely helps your hotline 🙂

And same applies to your firmware updates - where I never found release notes to check what has been changed or improved on my cameras - Arlo keeps it a secret procedure without any information about it nor any chance for users to be in control of the process or at least might easily obtain the info of changes in firmware.

[maithkano]

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?

[whatdidipayfor]

 

Geofence is now working however activity zones are completely broken resulting in constant motion notifications from anything they see, smart detection is broken as well as thumbnail views within iOS lock screen notifications. Oh, and the iOS Home app cannot refresh cameras/thumbnails and takes forever to even connect to live view. 
This is pretty tragic from a security company. 

[Rbmx1980]

Still not working Arlo. 
Updated app on all devices and it worked one time when I got in the geofencing, and not anymore when leaved…

[Smorcote]

And why is there now geofencing in Custom Mode -  but then it tells you to disable Custom to set up Arrive and Leave in Automations - I have tried all of these and none of them works automatically any longer

I agree with comment below that when you Test Automation it puts it in the Arm or Standby Mode but this seems to do nothing to operate automatic geofencing as it used to work

[wenklaw]

Welcome to the wonderful world of Arlo!! Don’t get relaxed and thinking, hey isn’t Arlo all good because I guarantee they will break it and when they do they really break it.  It’s garbage it really is and someone on another thread is recommending to a potential buyer using Arlo even without a subscription, beggars belief.

[HaraldZ]

Geofancing working again with 6.29.1 under IOS 26.5. thanks 

[Alouis]

Works again. Thanks for resolving 

[Alouis]

Well said and fully agree. 
@ShayneS please consider this

[HaraldZ]

Unfortunately it still does not work reliably. It worked once fine for me, but recently, it did not disarm when coming home. @Arlo, please do some more testing and fix.

[CYYau]

Even after updating to version 6.29.1, the issues still persist.

The geofencing function appears to be partially restored, but there is still a major problem with Custom Modes. Previously, if “Away” mode was triggered while I left home, it would remain active and would NOT be overridden by scheduled modes. This behavior was correct and logical.

However, in version 6.29.1, scheduled automations now take priority and forcibly switch the mode, even when “Away” status is active. Worse still, once this happens, I cannot reactivate the “Away” state again. This completely breaks the purpose of geofencing automation and creates serious security concerns.

Please fix this immediately.

In addition, the scheduling system in the new app is full of flaws. For example, I cannot set the end time of Mode A and the start time of Mode B to the exact same time. If Mode A ends at 18:00, the app only allows Mode B to begin at 18:01. This leaves a completely unprotected one-minute gap, during which unnecessary or disturbing notifications may appear. Such a basic scheduling limitation is unacceptable for a security-focused system.

Furthermore, the new app no longer provides proper controls for notification and mute preferences. Users cannot reliably decide which events should trigger notifications and which should remain silent. This issue not existed in older versions of the app.

As a customer who has used your products for many years, I am extremely disappointed that such fundamental functions remain so broken for such a long time. These are not minor inconveniences — they directly affect the reliability and usability of a security system.

I strongly urge your team to prioritize and resolve these issues as soon as possible.

[ShayneS]

@HaraldZ 

Can you enable geofencing for your Arm away mode and test this again? It look like you have it disabled at the moment. 

[Nabbie]

Two reasons:

1. A lot of us are having the same issue. We are just waiting for Arlo to fix it.

2. It's not necessarily obvious to a user that geofencing stopped working. Said differently, some users may not even be aware it stopped working because they assume it is so they are not going to check each time they leave and come back to the location. For instance I'm on Arlo for over 10 years, I've gone through all sorts of products and got more than 20 active right now. Well, I didn't notice it wasn't working until today when I thought it was odd i wasn't getting videos of my dogs inside the house as often as I usually do. Turns out, I had wrongly assumed the geolocation was working and my dogs were sleepier than usual. 

Let's see how quickly Arlo fixes this before someone files a lawsuit claiming Arlo failed to automatically enable the alarm, which prevented the monitoring service to properly function and therefore a house getting robbed without anyone knowing. Hint hint Arlo, get your act together. Also, UAT is a thing. Good luck everyone. 

[JoeyRG]

After update it is hit or miss if it activates or deactivates, I also am not getting the home notification or leaving notification so i have to open the app and check if it is armed or not.

[brothacraig75]

Still not working here.  I’ve tried everything but my wife’s device never leaves the geofence boundaries and auto leave/ arrive still isn’t working.  

[Brock16]

Updated to latest IOS 26.5 and Arlo app is up to date and Geo fencing is still not working! Triple checked all my settings

[Edinburgh_lad1]

So, a typical pattern of Arlo here to show that they're 'actively' doing something to address an issue: let's release a version and see if it's working; then there is the feedback from users that it's still not working; then another and another version until maybe finally, six months down the line, the issue is resolved. But the questions are: Why was it broken again in the first place? Why did it need interfered with again? And, most importantly, why issues are continuing to appear? (I don't mean minor issues, although those are plentiful, too, but problems that affect full functionality.)

And yes, one of the users above is right: most won't notice that it's not working.

[brothacraig75]

A heads up would have been nice before I spent three days trying to trouble shoot the issue thinking it was on my end.

and no, it still isnt fixed.  Ive updated everything and my wife’s device is still stuck inside the geofence and still no auto arm/disarm.  Ironically I just bought the Arlo doorbell last week and havent installed it yet.  Glad I kept the receipt.

[CYYau]

After checking again today, I can confirm that the geofencing function in Custom Modes has NOT been fixed at all in version 6.29.1.

The update merely changed the labels or status names used by the geofencing system, but the cameras themselves are still NOT being triggered or activated properly. Not a single camera responds as it should.

This is far beyond simply being “buggy” or “broken.” At this point, it feels closer to false advertising or outright deception. The update gives the impression that the issue has been resolved when, in reality, the core functionality still does not work at all.

This situation is completely unacceptable for a security product.

[CYYau]

Even after updating to version 6.29.1, the issues still persist.

The geofencing function appears to be partially restored, but there is still a major problem with Custom Modes. Previously, if “Away” mode was triggered while I left home, it would remain active and would NOT be overridden by scheduled modes. This behavior was correct and logical.

However, in version 6.29.1, scheduled automations now take priority and forcibly switch the mode, even when “Away” status is active. Worse still, once this happens, I cannot reactivate the “Away” state again. This completely breaks the purpose of geofencing automation and creates serious security concerns.

After checking again today, I can confirm that the geofencing function in Custom Modes has NOT been fixed at all in version 6.29.1.

The update merely changed the labels or status names used by the geofencing system, but the cameras themselves are still NOT being triggered or activated properly. Not a single camera responds as it should.

This is far beyond simply being “buggy” or “broken.” At this point, it feels closer to false advertising or outright deception. The update gives the impression that the issue has been resolved when, in reality, the core functionality still does not work at all.

This situation is completely unacceptable for a security product!

Please fix this immediately!

In addition, the scheduling system in the new app is full of flaws. For example, I cannot set the end time of Mode A and the start time of Mode B to the exact same time. If Mode A ends at 18:00, the app only allows Mode B to begin at 18:01. This leaves a completely unprotected one-minute gap, during which unnecessary or disturbing notifications may appear. Such a basic scheduling limitation is unacceptable for a security-focused system.

Furthermore, the new app no longer provides proper controls for notification and mute preferences. Users cannot reliably decide which events should trigger notifications and which should remain silent. This issue not existed in older versions of the app.

As a customer who has used your products for many years, I am extremely disappointed that such fundamental functions remain so broken for such a long time. These are not minor inconveniences — they directly affect the reliability and usability of a security system.

I strongly urge your team to prioritize and resolve these issues as soon as possible

[ShayneS]

Thank you all for the continued feedback. I provided all of your additional  information to the team, and I will report back as soon as possible.