Geofencing works on either of two cameras but not both

[Petychka]

I have two Arlo Q Plus cameras in the one premises using the same wireless network, both connected to the same two iPhones. Each phone has a different iCloud address. Both cameras are set up to be on when in zone, off when out of zone and a night mode, which is schedule when in zone.

When one of us is away (with one of the iPhones) but the other is at home (with one of the iPhones), Geofencing switches to "away" mode and we get notifications whenever the person at home moves around. Sometimes this happens when one of us is away, sometimes when the other is away. We do not carry each others' phones.

The Mode screens do correctly show that one phone is in zone and the other is outside zone.

Furthermore, there are problems in turning geofencing + schedule on. One camera will accept the double setting but the other camera will accept geofencing but not the accompanied schedule. Again, this can happen with either camera and it can switch cameras after I check the settings in the Mode screens.

It looks terribly buggy. Or is it me?

[Stomlinson]

Xi

[jguerdat]

I don't use GF but I think the usual suggestion is to remove both phones and readd them.  Does that help?  If not, someone else will have to pop in.

[TomMac]

read this just in case; https://community.netgear.com/t5/Arlo-Knowledge-Base/How-do-I-add-and-manage-multiple-mobile-devices...

[Petychka]

Thank you, jguerdat. I did try that with only one of the cameras but it didn't't make any difference. Also the attachment of the cameras is finicky - it can take a few tries. 

[Petychka]

Thank you, TomMac. I had read these instructions before and I believe I have complied with its advice. I wonder whether the problem lies in that the geofencing is still a beta facility and the bugs haven't been ironed out yet. Otherwise, the Arlo camera system is very, very good. Regarding any improvements, besides fixing up what could be a beta-bug, it would be good if the geofencing zone had a smaller radius than its present minimum 150 metres. One hundred and fifty metres may sound like a short distance but it means that my home is not protected when I am in the next street.

[jguerdat]

I'd suggest the removal of both devices from GF, save and then add them back in before doing anything else (just the standard troubleshooting steps, not personal experience).

The potential issue with the size of the GF zone is the precision of the location mechanism used in the device. I understand that being in the next street is a significant distance but I've seen less than accurate locations being determined.  There has to be some wiggle room.

FWIW, I'm also involved in a beta test of the app for my August Smart Lock which uses GF to varying degrees of success.  Comparing the two implementations (Arlo and August), neither has a clear edge over the other in how well it works.  I don't know the root cause of this - it's just an observation. My phone simply wouldn't connect to the lock yesterday until I restarted the phone, not clever when you're standing outside with arms full of groceries in the rain.

[Petychka]

Dear jguerdat, I have tried removing and replacing the cameras and it didn't make any difference. Today, I tried removing my phone, which one of the two cameras was avoiding,  from the devices that was being geotagged, saving the removal and then replacing it and saving it - and it worked! So it's OK now. 

Yes, I understand there needs to be wiggle room to manage the error circle of the estimation of the position of the cameras but 150 metres appears to be more of a hog than a wiggle.