Filter Notifications - Arlo Plus

[aawilliams123]

Hello,

We have an Arlo Essential Wired Video Doorbell, and upgraded to the Arlo plus plan.  Our phones are blowing up with vehicle notifications so I'm looking to see if there is a way to limit these.  Specifically:

1)  Record vehicle events so that they show up in the "Feed" on the Arlo App

2) Disable iOS notifications for Vehicle events only 

I am aware of the "Smart Detection" functionality, however this disables both notifications as well as saving vehicle recordings to the feed.  I want the videos, just not the notifications.

Thank you!

[ShayneS]

Hi @aawilliams123 

Thanks for reaching out. You can achieve this by navigating to your profile icon > locations and plans > home > smart detection > select the desired camera, and select the people toggle off. Make sure to press the back arrow to save. You should only be notified of your other choices, and recordings will still show up as "motion" in the feed/library. I hope that helps. Please let me know if you need any further assistance.

If you'd like, you can also try adjusting the motion sensitivity instead, bringing it to a lower value, and test again. When I do this, I like to go to close to zero and then move my way up. 

[aawilliams123]

Thanks ShayneS, however this hasn't solved the problem, it's just replaced the Vehicle notifications with Motion notifications.  As noted in my original post I want to record the videos (so I don't need to change sensitivity or positioning), all I want is to stop the notifications.  This used to be possible with Smart Notifications but I believe that function has been removed in place of Smart Detection.

Let me know if there is some other configuration option I'm missing.  Thanks,

-Aaron

[ShayneS · Accepted solution]

@aawilliams123 

Can you try selecting the "All Motion" toggle off as well. 

[aawilliams123]

Hi Shayne,

I was giving some time to see if this update fixed our issue - and looks like it has. Thanks again for your assistance!

[ShayneS]

Awesome! I was sure this was possible as I use the feature the same way, glad we found the culprit.