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.

[jguerdat]

Not here but there have been scattered posts about mode switching causing cameras to record. Of course, motion may have been detected but was too fleeting to capture due to the camera startup time. I've also had recordings apparently caused by a different camera's IR LEDs being detected. Why those LEDs happen to have been turned on isn't necessarily known. It's apparent that overnight cameras seem to activate when checking for updates or similar activity.

[alex_loo]

@jguerdat do you have links to those scattered posts? Thanks.

Alex

[jguerdat]

No, I don't track such things except in my (feeble) head. Here's one such I found with a search for "mode switch camera records" here:

https://community.arlo.com/t5/Arlo/When-a-mode-activates-all-cameras-record-automatically-with-the/m...

[alex_loo]

---

@jguerdat wrote:

No, I don't track such things except in my (feeble) head. Here's one such I found with a search for "mode switch camera records" here:

https://community.arlo.com/t5/Arlo/When-a-mode-activates-all-cameras-record-automatically-with-the/m...

---

thanks.  I had a read of that thread.  Turned out it was NOT an ARLO bug, but mis-configuration with the scheduled routine.

Do you recall any other cases? 

Alex

[jguerdat]

Nope. My search for exactly the same thing turned up different results that had no utility. The posts have been sporadic so there's no easy way to find them.

[alex_loo]

---

@alex_loo wrote:

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.

---

so back to my issue .....

I did try something with the 1130pm schedule routine that switches to ArmAway.  Adding "send notification" as the action together with the switch action (my original routine did NOT have the action of sending notification).

And the result?  Still buggy, sending me this WRONG notification, every time the 1130pm routine (correctly) switches to ArmAway.

Sigh.  Anything that can go wrong, ARLO will just get it wrong.

Alex

[BrookeN]

I have let the development team know the behavior you are seeing. I will update you as soon as possible. 

[alex_loo]

---

@BrookeN wrote:

I have let the development team know the behavior you are seeing. I will update you as soon as possible. 

---

thanks @BrookeN .  Are you able to let development team know about the geofencing issue?  This is more important, actually a show stopper to me.

Alex

[BrookeN]

@alex_loo the development team is already currently investigating the behavior with Geofencing. I will update the community as soon as I have any updates. 

[alex_loo]

---

@BrookeN wrote:

@alex_loothe development team is already currently investigating the behavior with Geofencing. I will update the community as soon as I have any updates. 

---

thanks @BrookeN .  More than happy to provide info on error cases and assist with testing, if that helps.

Alex

[alex_loo]

---

@BrookeN wrote:

I have let the development team know the behavior you are seeing. I will update you as soon as possible. 

---

so this is about the issue as reported by the original post ---- false motion recording+notification every time when my automation routines (correctly) switches to ARM AWAY at scheduled time of 1130pm, but then also incorrectly recording motion + sending notification.

Given your other reply re the geofencing issue, just some reminder regarding above too.

(this is still happening every 1130pm here!)

Alex

[BrookeN]

Our team is still looking into this behavior, I will update the community as soon as possible. 

[alex_loo]

---

@BrookeN wrote:

Our team is still looking into this behavior, I will update the community as soon as possible. 

---

hi @BrookeN ,

Do you have updates regarding this?

Alex

[BrookeN]

@alex_loo I am checking on this, I will update you later today or tomorrow.,

[alex_loo]

---

@BrookeN wrote:

@alex_looI am checking on this, I will update you later today or tomorrow.,

---

thanks.  I notice there were 2 issues mentioned in this conversation:

1. geofencing issue

2. false recording by camera, when it get kick-started arming (correctly) by 1130pm routine.

I was asking about issue #1 (ie geofencing).  It has not improved at all.

Issue #2 on false recording has disappeared recently.  Nothing for ARLO to follow up, from me.

Alex

[jguerdat]

FWIW, GF has recently been working properly for me. This was with both the 5.7 as well as 5.7.4 Android apps. Whether it remains working, we'll see.

[alex_loo]

---

@alex_loo wrote:

---

@BrookeN wrote:

@alex_looI am checking on this, I will update you later today or tomorrow.,

---

thanks.  I notice there were 2 issues mentioned in this conversation:

1. geofencing issue

2. false recording by camera, when it get kick-started arming (correctly) by 1130pm routine.

I was asking about issue #1 (ie geofencing).  It has not improved at all.

Issue #2 on false recording has disappeared recently.  Nothing for ARLO to follow up, from me.

Alex

---

@BrookeN , as mentioned above, I desparately need fixes on "#1 geofencing issues".  I haven't seen and heard any good news yet.

Alex