Activity zones don't work

[marathon]

I have spent hours trying to get Zones to work (because of a train on one side and a road on the other) and have concluded that it simply doesn't work.

For context, I am an engineer and used to build video software myself, so it's not pilot error.

Theoretically, zones are straightforward: only evaluate motion within the region. In clip after clip after clip, it's obvious that it's recognizing motion outside the zone (the train going by). I have edited the region many times, rebuilt it from scratch, adjusted sensitivity, to no avail.

My region is a multiple-point polygon, which may be the problem -- maybe the feature only works with rectangles (a lot easier to implement) ... but they let you draw polygons, and in this case, I need them.

Dozens of false positives per day chew up the battery life.

Lot of other software gets this right. Please fix it.

[n11]

I too am having problems with activity zones and have an observation about when mine get triggered outside of the zone I have designed.

The camera I'm having problems with is aimed parallel to a road (not aimed directly at the road).

• The road is far out of the activity zone
• The road is far beyond the stated detection range for the camera (guessing 100-150 feet)
• Sound detection is off
• There is a speed bump on the road
• Cars DON'T trigger a notification
• Larger trucks DO trigger a notification (like a landscape or trash collection truck), a van won't trigger
• Activity zone redesigns have had no impact on the outcome

I've seen this in multiple recordings over many months and it is very consistent. Is it possible that that the notification is triggered by vibration rather that by being in the zone or by sound? Has anyone else observed triggers where vibration could be the cause?

[bangboi]

Are you on battery or AC?

[bangboi]

I hope somebody from arlo responds and gives us some updates on activity zones. Ive been reading all the posts on this and nothing seems to be solved. blahh

[marathon]

We are on battery. I don't see that that would make any difference (other than to run down the battery with false positives, which is what we are experiencing).

Thanks for the details , @n11 -- I am suspicioius now of audio triggers that ignore the activity zone. There is certainly correlation for us with large trucks and trains, though it seems small things also trigger it (the occasional forklift or car). I will look more closely for those correlations.

I don't see anywhere to turn off audio as a trigger for motion detection. I tried turning off Microphone, but that doesn't seem to change anything (I think it's related to what is recorded, rather than what triggers the recording).

Does anybody from Arlo actually monitor this forum, or do I need to escalate this to them directly? It "just doesn't work."

[JamesC]

marathon,

Given then troubleshooting you've already performed, I recommend contacting the Arlo Support Team to further investigate this issue. You will find several options for contacting support in the provided link.

JamesC