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.
Are you both using the primary account's login or is one of you using an account that was granted access? If the former, the primary user should use Settings, Grant Access to the other's email address.
"To add to what jguerdat mentioned, if you log in to the web portal you will be signed out of the Arlo mobile app and vice versa."
That is not the issue. I have logged in to the web portal perhaps once a year.
Both me and my SO are experiencing the same issue. Me on Android and her on iOS. It seems like we cannot stay logged on for more than about a week. Once we have been signed out we get no notification or indication that this has happened. This makes the whole camera pretty much pointless since we never know when it stops working unless we manually sign in to the app every time we leave the house to make sure that we are signed in. Otherwise we won't get any notifications if the camera sees anything and the camera won't even arm either since the geofencing function stops working.
The app must be able to ensure that we are constantly signed in even if we don't open it. If any manual action is required it needs to show a notification that it needs my fingerprint to sign in again for example. This needs to work even if the app hasen't been opened for weeks or if the phone is turned off for a while or rebooted etc. It is very crucial functionality. Otherwise all your cameras are pretty much pointless, the app should not require constant babysitting for the alerting and geofencing functionality to work. Also, if any of the phones that are part of the geofencing function looses contact with the cloud its position should change to "outside of fencing area" instead of remaining where it was last time so that it doesn't prevent the cameras from arming.
This has been an issue for a looong time and I will be removing my subscription unless it can be fixed soon. There's no point to pay for something that doesn't work. I was planning to buy many more cameras once my new property has been built but I will have to look at alternatives instead if this never gets fixed...
We both have the latest version of the Arlo app available on the apple store and google play store respectively.
Lately the Arlo subscription bills arriving in my mailbox work as a reminder for me to double-check if the geofencing armed/disarmed notifications are still appearing or not and if they have been gone for an unknown amount of time the fix is for both me and my SO to just open the app and sign in again which will make everything work for another 3-14 days (hard to tell how long exactly and still don't know if this time varies or is the exact same amount of time).
Something that would make debugging this a lot easier is if we could check if the phones are reported as inside zone, outside zone or unknown (disconnected from Arlo cloud?) from the web portal. Also as I wrote above a device that has disconnected should have an unknown position instead of being registered on its last known position. Devices with an unknown position should count as being outside the zone or even better it should be configurable what it should count as... even if it takes 1 whole day for a device to switch from it's last known position to an unknown position that would be a lot better than them being registered in their last known position forever. Then the cameras would at least arm during vacations if our devices have mysteriously disconnected from the Arlo cloud...
This is still an issue for us.
As @Arques says, every few days, one of us is logged out and then the geofencing fails. We don't know when this happens or why.
All our systems are up to date, background refresh enabled etc. etc.
It just seems totally unreliable. It's no wonder that insurance companies here don't consider these types of camera systems the same as hardwired CCTV.
“Something that would make debugging this a lot easier is if we could check if the phones are reported as inside zone, outside zone”
If you look in the mobile’s settings for arlo app at the bottom of the page you should see an option to receive notifications to your mobile and guest device for notifications when you leave and enter the wanted region.
While you’re there also toggle back and forth the location option to ‘always’ to force the mobile to configure. Do the same for the ‘background refresh’.
I have seen iOS especially requiring this post iOS and arlo app updates.
Being logged out of the app does not stop recordings. It just would stop getting notifications since the app has to be active in the background. The system continues to work regardless of being logged in.
IF this is being touted as a security feature there should be an associated push notification to the end user.
You can wait for arlo to fix it which has been done multiple times over the years but it always fails to deliver a reliable sense of security for the end user.
The big question is who came up with the stupid idea that sessions should expire in the first place? (If active sessions are a requirement for the geofencing function)
Why are there no notifications from the app that the session has expired?
If you think session expiration is a crucial feature session refreshing needs to be super smooth, why can't the app when still running in the background automatically refresh them?
"If geofencing is not working for you don’t keep trying to use it."
Geofencing is a critical feature of the system and a major selling point. If we can't use it, we have to either leave the system on at all times (battery drain, alert fatigue) or, switch the system on/off (risk forgetting to do so).
Other apps use location services on our phones successfully for years without error or interruption. Why Arlo can't do this is beyond me. I have submitted logs to Arlo to help troubleshoot the issue but am yet to receive a reply.