×
Arlo DevOps team is investigating an issue where customers are experiencing login issues. We apologize for this inconvenience and are working to resolve this issue.
×Arlo End of Life Policy Notice To view Arlo’s new End of Life Policy, click here.
×Urgent: Activate Two-Step Verification Arlo requires all users to activate two-step verification to continue to access your recordings, devices, and account. Please enable this feature now. Learn More.
×
We are experiencing an outage of our ReadyCloud service and are working to resolve the issue..
×
We are experiencing an outage of our Google service and are working to resolve the issue..
This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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
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.
i did however notice my partners phone was running previous version of Arlo so have updated and will report back as we are both out today so will see if geofencing works again, fingers crossed!
Since the release of the new app the camera’s do no longer record activity when the system is on Geofencing mode.
the hub detects when I’m gone and home ( all good so far ) bit the camera’s do not record any activity. All cameras are active and the settings are set seems to be right. When I arrive back home I get the “ disarmed” so OK from that perspective.
Seems to be an iOS app issue. Have you used the app to go to Settings, Support and talked to official support? You may want to check the phone's settings for the app about location services. I don't have an iOS device so can't be specific.
Followed all suggestions on the community. Also customer representative did not have a clue. Asked me to delete all automations and recreate them with no result.
Since updating the Arlo iPhone app to version 6.28.0, geofencing automations are no longer working correctly.
Before the update, everything worked perfectly: When everyone left the house, the system automatically switched to “Arm Away” mode without any problems.
Since the new update, the automation no longer triggers reliably, or does not work at all. The system no longer activates “Away” mode when all family members leave the house.
I already checked:
iPhone location permissions set to “Always”
Background App Refresh enabled
Location Services enabled
Geofencing enabled in the Arlo app
Everything was functioning correctly before the update, so this appears to be caused by the new app version or the new automation system.
I also noticed that many other users are reporting similar geofencing problems after recent Arlo updates and the new app experience.
Please investigate this issue and restore the previous reliable geofencing behavior.
Seems strange the forum isn’t full of people having the same issue. I’m reluctant to delete all my automations as since the new app last year it was a bleeding nightmare to setup in comparison to how the old app worked with geofence
update, it appears many users are having the same issue with geofence no longer working after the last iOS arlo app update, jeez Arlo suck
My Geofencing now longer works since Arlo released there latest App version 6.28.0. I have tried changing the location settings, using a different device, creating a new routine nothing appears to show the geofence at home. Is this a wide spread issue @Arlosupport, @Arlo are you aware of this?
I decided to enable the new 'custom mode' which effectively disables all other modes and also automations. I then set the custom mode to 'arm' when away and 'disarm' when at home using geofencing, again this doesnt work proving that my modes and automations arent the cause (they have been working for over a year) and Arlo have basically messed up yet again.
Fix the effing thing, god knows how many customers you have lost for being this bad but i for one have and will not ever recommend this garbage to even my worst enemy
The system no longer activates “Away” mode when all family members leave the house.
I already checked:
iPhone location permissions set to “Always”
Background App Refresh enabled
Location Services enabled
Geofencing enabled in the Arlo app
Also check "available geofencing devices" in the privacy center section. Sometime the system will add something when the app updates. Mine added an ipad which is always home last time I updated, and that also broke "away" for me. Sometimes we've seen it add "ghost" devices, so make sure your actual devices are uniquely labeled - making that easy to spot.
Nothing was changed or modified on the iPhone; only the Arlo app was updated.
My suggestion is to check the available geofencing devices in the app.. As I said, sometimes I see old geofencing devices re-appear in the list - which gets in the way of "everyone leaves" automations.
Thanks for the suggestion. I’ve checked the available geofencing devices in the app, and there aren’t any others.
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. Also, until yesterday I had already removed the old iPhone from the geofencing devices list.
Today I added the old iPhone again, deleted all automations, and reconfigured them on the old iPhone. At the moment, it only works with the old iPhone and the old Arlo app.
I also created the automation separately for each iPhone. Until now, it was never necessary for all devices to leave the area at the same time. If the first iPhone left the area, the mode switched correctly. When the second iPhone left the area, it also switched correctly.
Since Friday 22 May 2026 Arlo Secure geofencing no longer works. When we both leave the house, Arlo does not recognize this and remains in standby. Please fix
