My wife and I both have iPhones with the Arlo app. Both if these are listed as devices which are geofenced.
We regularly find that one of our devices has been logged out of Arlo, and therefore won't trigger the geofencing (either Home or Away), leaving our system exposed.
We will both leave home, only to find that Arlo thinks one of us is still there, and won't arm the system. Similarly, we'll arrive home, and the system won't disarm, until we both log in, change mode to arm or disarm, and then back to geofencing.
The trouble is, neither of us know when this happens. The Arlo app doesn't tell us that we've been logged out until we go into it, which defeats the purpose of geofencing. We also don't understand why either of us would be logged out when we haven't touched the app.
This is very confusing and frustrating, any tips would be gratefully received.
A workaround is to regularly logout the arlo background app to refresh the mobile OS timeout set by arlo.
In the arlo app go to settings/profile/logout
then log back in again.
Do this every 13 days to refresh the background app run timeout.
Set a recurring reminder on your mobile device to remind you to take this action on Arlo’s behalf every 13 days.
Has anybody noticed any recent changes on this issue?
I don't seem to have been logged out of the app for a few weeks now.
Hoping it's been quietly fixed. Perhaps something in iOS 17?
I noticed a change of logout behaviour a few weeks ago, instead of logout requiring manual re-entry of credentials every two weeks it changed to immediately logging back into the app when the app was reopened. This happened weekly for a few weeks then stopped.
Geofencing still not working unfortunately.