I've posted to Netgear support, but also wanted to see if anyone is seeing what I am. I didn't see this issue with the Pro, but am seeing it with the Pro 2's.
Basically, I'm monitoring an alley, and have it set to "Record until activity stops". However, once a car has gone past, and only sometimes, it continues to record for up to 4 or 5 minutes. I've reviewed the video, and I'm not seeing any motion that would keep it going. Anyone seeing this?
Is this happening on every recording or is it intermittent? Could you post an example of a recording that continued that you expect should not have?
I can show you a few examples of this, just from the last few days.
I think it MIGHT have something to do with the fact that I am using a rule like such:
If Audio or Motion is detected on Front Door, Record Video on Front Yard.
If Audio or Motion is Detected on Front Yard, Record Video on Front Door
If Audio or Motion is detected on Front Door, Record Video on Front Door
If Audio or Motion is Detected on Front Yard, Record Video on Front Yard.
All are set to stop when motion stops, but about once or twice a day a motion kicked off record will just run for 5 mins.
When using "Record until activity stops", after the initial motion detection event is triggered the camera sensitivity is greatly increased and returns to the previous sensitivity level after no additional motion is detected.
In your examples, it could be changes in the lighting or shadows moving across the field of view that is causing this behavior.
You might try adjust the location of the camera slightly to see if you still experience the same behavior.
Nice try man, but there are no moving shadows or tree's in my examples that would keep the camera going for 5 mins. That is only 2 examples, it happens at least once a day. Im not buying you're response.
@JamesC here is another example from a different camra.
The recording ran way past the motion that triggers it. This is a bug, not a camera placement issue.
Thanks for the examples, i'll see what engineering has to say about what you've presented. That last link you provided will expire within 24 hours. Can you provide a drop box for it as well?
I’m guessing it’s considering the clouds in the windshield as motion. Are they using pixel comparing, or actual IR for motion sensing?
I’ll look for other examples.
I am having the same issue with both cameras. Any motion will trigger the camera to record for 4-5 mins. Tried adjusting the cameras, setup different rules and modes, etc. but nothing seems to help.
I did not have this issue with the Arlo Pro mounted in the exact same place and position.
I also tried disabling each camera and switching their positions but both always record 4.59 mins
Not sure why every recording would be 5 minutes unless the camera is actually somehow detecting motion (actually IR difference detection). 50% would seem to eliminate that. Is the camera powered so it's using pixel detection rather than IR? That's more sensitive compared to the IR method.
It could be an issue with the Armed mode. Try creating a custom mode with the same settings and see what happens. It may be best to reset the system byt removing all devices in Settings, My Devices and start fresh to clear out any weirdness.
And, of course, you could always use the fixed time selection but that's a workaround, not a fix.
I can say from my setup, it "seems" to be using pixel detection. However, it's not using A/C power. (yet)
I will also say that in my case, it doesn't record 5min every time, it's rather sporadic. I've switched to 30s max recording just to keep from recharging ever few days, until it's resolved properly.
I will try to create a new mode and test again.
I've created a new mode, and setup it up for 80% motion detection, record until motion stops.
Got a 5min video right away. And, it's not clear what even triggered it, nor what kept it going. Only thing "moving" is reflections and shadows of trees, but it certainly shouldn't have been enough to trigger it, especially at 80% on IR detection. I still think it's doing pixel compare when not on A/C.
A second video was triggered appropriately, but again, kept running for no reason. I'll stop posting until a specfic request from Netgear.
Interestingly, on my other camera (also Pro 2), setup the same as the one above, it has plenty of reason to trigger, and run to the max length of 5min, but doesn't.
All I can suggest at this point is to reset the system and start fresh. Remove all devices in Settings, My Devices. Maybe for good measure use the reset button, too, until the LEDs flash amber. Use the Add Device button to add the base and sync the cameras. Verify your firmware versions are up to date.
If that has the same problem, you'll need to open a case with support.
Can you point us in the direction of confirming what the current firmware is for the Arlo Pro 2 camera? Just curious, although I have already done what you suggested and still have the 5 minute motion for just a few seconds of motion bug and also the horrible night vision bug. So dont think that "solution" will help, but I do want to confirm the most recent camera firmware. Point us into the right direction. Thanks