Correct schedule switch to ARM AWAY but getting motion notification incorrectly

[alex_loo]

This is very weird and already the 3rd consecutive night happening this. 

I have this time routine switching to ArmAway every 1130pm, followed by no notification.  Running Perfectly perfect so far.

And then these 3 nights, it still switched to arm away, but then

• Notification about motion alert of 1 of my 3 cameras
• Recording with that camera ( and there was no motion at all)

The camera in context happens to be the last camera that is armed up.

Anyone experiencing something similar?

Alex.

[StephenB]

---

@jguerdat wrote:

I'm now on (Android) 6.2.8 with GF working 100% for a while now.

---

@alex_loo - I started monitoring this again a few days ago (iOS, only one geofencing device). Not a lot of occurrences yet.

The system triggered properly on all the "Leaves", but only one "Arrive" resulted in a trigger.   The other two "Arrives" were missed.  So not anywhere close to 100% for me.

This was with 6.2.6 - I just updated to 6.2.8.  Hopefully that will do better.

[alex_loo]

---

@alex_loo wrote:

---

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

---

hi @BrookeN , yes the issues never improve at all.

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[jguerdat]

With trepidation in my heart, a couple of questions:

1) You are on Android only, right? ( @StephenB is on iOS)

2) You are still on a rather old version of the app, correct?

You can use a file manager such as "File Manager +" to back up your existing app, remove it and install the current version on both phones to see if that works. If not to your liking, you can then revert back to the backed up version.

[alex_loo]

---

@jguerdat wrote:

With trepidation in my heart, a couple of questions:

1) You are on Android only, right? ( @StephenB is on iOS)

---

Negative.  I have both OS here.  My device is on android 16.  Wife's on iOS 18.5

2) You are still on a rather old version of the app, correct?

---

Negative.  I have been forced to update to this 6.2.8 here, more than a week ago.

You can use a file manager such as "File Manager +" to back up your existing app, remove it and install the current version on both phones to see if that works. If not to your liking, you can then revert back to the backed up version.

---

I won't waste my time trying this and trying that.

a. ARLO support has contacted me for data log looking into geofencing issue.  @BrookeN  has also confirmed in this community that DEV team is looking into this.  So far I have NOT heard any news regarding any version fixing geofencing issue, so I would assume GEOFENCING IS STILL OUTSTANDING ISSUE AND ARLO IS STILL LOOKING INTO IT.

b.  I have been told by "superusers" that they "do not work for ARLO", so won't bother any non-official suggestion trying this and trying that, understanding that ARLO has simply made zero fixes to geofencing.

Alex

[StephenB]

---

@StephenB wrote:

---

This was with 6.2.6 - I just updated to 6.2.8.  Hopefully that will do better.

---

FYI, I've also missed an Arrive with 6.2.8.  So still not working correctly.

So far it has not missed any "Leaves", which is puzzling.

[alex_loo]

---

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

---

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #5)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[BrookeN]

@alex_loo can you please go into your wife's phone and under edit Geofence make sure that your wife's location permissions are on. If they are off it will show like a triangle with a line through it and it will state needs location permission.

[alex_loo]

---

@BrookeN wrote:

@alex_loocan you please go into your wife's phone and under edit Geofence make sure that your wife's location permissions are on. If they are off it will show like a triangle with a line through it and it will state needs location permission.

---

hi @BrookeN , where is this "edit geofencing"?  Nevertheless, I have configured the following on wife's iPhone, since 12+ months ago:

• ARLO app has permission to iPhone location service (ALWAYS ON and "Precise location")

Do you have updates regarding any ARLO app fix, over these 12 months?

Alex

[alex_loo]

---

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

---

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #6 #7#)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.
6. [2025.08.06] ARLO app was ARM HOME.  Both devices were at home.  Then only my device left home, but then ARLO switched to ARM AWAY, incorrectly.  It should have stayed at ARM HOME (since my wife's device was still home)
7. [2025.08.06] ARLO app was ARM HOME.  Wife's device was home and my device was away.  Then my device arrived home, but then ARLO stayed at ARM HOME, incorrectly.  It should have switched to STANDBY, according to my geofencing routine.

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[alex_loo]

---

@BrookeN wrote:

@alex_loocan you please go into your wife's phone and under edit Geofence make sure that your wife's location permissions are on. If they are off it will show like a triangle with a line through it and it will state needs location permission.

---

as a side info to show that wife's phone has location permissions in place.  Today (2025.08.06) ARLO was ARM AWAY, and both devices were away.  Then wife's device arrived home, and then ARLO switch to STANDBY, correctly (well for this time) following the routine I have set up.   This shows that the device location permission settings have been well in place.

Alex

[alex_loo]

---

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

---

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #8)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.
6. [2025.08.06] ARLO app was ARM HOME.  Both devices were at home.  Then only my device left home, but then ARLO switched to ARM AWAY, incorrectly.  It should have stayed at ARM HOME (since my wife's device was still home)
7. [2025.08.06] ARLO app was ARM HOME.  Wife's device was home and my device was away.  Then my device arrived home, but then ARLO stayed at ARM HOME, incorrectly.  It should have switched to STANDBY, according to my geofencing routine.
8. [2025.08.06] This is the same issue #7 repeated again, on the same day.

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[alex_loo]

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #9 #10)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.
6. [2025.08.06] ARLO app was ARM HOME.  Both devices were at home.  Then only my device left home, but then ARLO switched to ARM AWAY, incorrectly.  It should have stayed at ARM HOME (since my wife's device was still home)
7. [2025.08.06] ARLO app was ARM HOME.  Wife's device was home and my device was away.  Then my device arrived home, but then ARLO stayed at ARM HOME, incorrectly.  It should have switched to STANDBY, according to my geofencing routine.
8. [2025.08.06] This is the same issue #7 repeated again, on the same day.
9. [2025.08.07] This is the same issue #6
10. [2025.08.07] This is the same issue #7

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[BrookeN]

I have been passing this information onto our development team. As well as the logs that were provided. I will provide an update as soon as possible. 

[alex_loo]

---

@BrookeN wrote:

I have been passing this information onto our development team. As well as the logs that were provided. I will provide an update as soon as possible. 

---

thanks.  I'll report incidents here.

@BrookeN , any chance we could:

• be updated here regarding the troubleshooting progress, say on monthly basis?
• be shared about the ball park date in development team's mind?

Alex

[alex_loo]

@BrookeN wrote:

@alex_looare you still seeing this same behavior?

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #11)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.
6. [2025.08.06] ARLO app was ARM HOME.  Both devices were at home.  Then only my device left home, but then ARLO switched to ARM AWAY, incorrectly.  It should have stayed at ARM HOME (since my wife's device was still home)
7. [2025.08.06] ARLO app was ARM HOME.  Wife's device was home and my device was away.  Then my device arrived home, but then ARLO stayed at ARM HOME, incorrectly.  It should have switched to STANDBY, according to my geofencing routine.
8. [2025.08.06] This is the same issue #7 repeated again, on the same day.
9. [2025.08.07] This is the same issue #6
10. [2025.08.07] This is the same issue #7, again
11. [2025.08.08] This is the same issue #7, again

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.

[alex_loo]

@BrookeN , I'll add up my failing cases here, if you or anyone is interested:

(new #12 #13)

1. Just yesterday, my device and wife's device were leaving, but ARLO didn't switch to ARM AWAY and it should have, according to my away routine
2. While both devices were away and ARLO was ARM AWAY, and then wife's device was back.  ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
3. As the next scenario of number 2 above (ARM AWAY, wife device home already, my device still away), when my device is back, ARLO did NOT switch to STANDBY, but it should have, according to my ARRIVE routine.
4. [2025.08.03] ARLO was ARM HOME.  Both devices leave together.  ARLO stayed at ARM HOME, incorrectly.  It should have changed to ARM AWAY.
5. [2025.08.05] Both devices are away, and ARLO is at ARM AWAY.  When both devices are then arriving home together, ARLO stayed at ARM AWAY, incorrectly.  it should have switched to STANDBY, according to the geofencing routine setup.
6. [2025.08.06] ARLO app was ARM HOME.  Both devices were at home.  Then only my device left home, but then ARLO switched to ARM AWAY, incorrectly.  It should have stayed at ARM HOME (since my wife's device was still home)
7. [2025.08.06] ARLO app was ARM HOME.  Wife's device was home and my device was away.  Then my device arrived home, but then ARLO stayed at ARM HOME, incorrectly.  It should have switched to STANDBY, according to my geofencing routine.
8. [2025.08.06] This is the same issue #7 repeated again, on the same day.
9. [2025.08.07] This is the same issue #6
10. [2025.08.07] This is the same issue #7, again
11. [2025.08.08] This is the same issue #7, again
12. [2025.08.09] This is the same issue #6, again
13. [2025.08.09] This is the same issue #7, again

Months ago, I submitted data log on similar issues, but have heard nothing.  And again, such basic geofencing has NOT been working, since more than 14 months ago, when I first owned the whole system.