Arlo|Smart Home Security|Wireless HD Security Cameras

Not capturing events if not on smart notification AGAIN

Reply
Discussion stats
  • 9 Replies
  • 1011 Views
  • 3 Likes
  • 6 In Conversation
kayg
Star
Star

I have Arlo Pro 4 cameras and again I am not seeing vehicles, animals, or person unless I have smart notifications (now smart detections) toggled on. 

I don’t need to be sent a notification for all of these events, but I would still like to see these videos  in my feed. 

They’re labeled as “motion” amongst other things that move e.g my trees a bug etc. Arlo had a big thread of customers reporting dissatisfaction with this update and Arlo reverted it back. However, as of 10/2/2024 it seems that Arlo has changed it back to what customers were showing dissatisfaction with in the original post (now locked, so we can’t add updates). 

Is anyone experiencing this as well? Please change this feature. @JamesC 

9 REPLIES 9
ToolslingerMPM
Initiate
Initiate

I'm running Pro4, and Pro4xl's.

When they made the initial change, I happened to be messing around with settings, and figured I had messed up somehow...

Alas, no, it wasn't me.  Since they made the "update" I've lost 80-90% of what should be triggering the units.  I've gone back through, and turned on every single notification to no avail.  All sensitivity is maxed out.  I've made sure the apps are all updated, and all the firmware is curent.  I get no vehicle triggers on the cam pointed at the road.  I used to get 30-40 a day.  It didn't trigger on a car accident, and the ensuing 1.5 hours of response in my front yard Tuesday.  3 hours later, it triggered on a deer walking by.

 

I now have zero confidence in the system.

 

I'm done.  This crap will be in use for whatever it might capture until I can trench in IP cams in the spring.  

dgoldg
Star
Star

Yes, they've broken (again) what they fixed. See this thread: https://community.arlo.com/t5/Arlo-Secure/Again-not-correctly-recording-event-types/m-p/2420701#M996...

 

@JamesC what is going on? Why are the engineers reversing this once again? 

JamesC
Community Manager
Community Manager

While content in feed will have a generic "motion" label, you should still be receiving recordings for all content regardless of the selections made within your Smart Notifications toggles. The development team is working to restore these labels but I do not have an ETA for when this will be resolved.

 

JamesC

kayg
Star
Star

I agree, I have two cameras in the alley, and you can imagine now how many notifications I am getting for vehicle being turned on. Oh, if I have motion on just to see videos in my feed guess what, now I have to see trees moving, bugs flying by etc. 

 

I have nine arlo cameras too with solar panels, so I invested a lot over the years, and now I guess that's money being thrown down the drain. 

JamesC
Community Manager
Community Manager

kayg,

 

You can turn off "All Motion" and "Vehicles" for the desired cameras and that will suppress notifications only. The change to these toggles suppressing notifications and recordings was reversed. You should still get recordings on the cameras with toggled off Smart alerts as long as those cameras are armed, those recordings will just have a generic "motion label".

 

JamesC

AndreaEW
Aspirant
Aspirant

JamesC, I’m having this problem, too. Is there a fix?

kayg
Star
Star

@JamesC it's been some time since this change and no update. When will the development team restore back to it's original function? 

AndreaEW
Aspirant
Aspirant

It's not just that the label is a generic "motion" label, I, and I think others from what I'm reading, are not receiving recordings unless the Smart Notification is toggled on. We want the recording action without receiving a notification to be restored.

lpn-ch
Aspirant
Aspirant

Same issue, if the motion alert type is not enabled in smart notifications, the corresponding motion type event is not recorded at all. Same as this:

 

https://community.arlo.com/t5/Arlo-Secure/Not-capturing-events-if-not-on-smart-notification/td-p/241...

 

Was supposed to be fixed from my understanding of the thread.