- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Motion detection
Either I have misunderstood how motion detection on the MV works or I am doing something stupid.
I have a camera setup near an entrance. I have enabled motion based retention and marked out an area of interest which only captures an area in from of the doorway.
The issue is every piece of motion even outside of the selected area show as an activation on the timeline which is a problem because there is a road in the background of the view so every car that goes past is considered motion.
Is this normal? Every other brand of camera I have used only records motion in the selected area of interest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
But does it only show movement or is it also recording when movement is detected outside the selected area?
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Theoretically, only the selected area should be considered.
So I suggest you open a support case.
https://documentation.meraki.com/MV/Initial_Configuration/Motion_Based_Retention
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Motion-based retention only kicks in for footage that is 3 or more days old.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Where in the documentation does this say?
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://documentation.meraki.com/MV/Initial_Configuration/Motion_Based_Retention
"The industry-standard motion-based recording is never considered 100% effective, and some missed events are expected. To combat this, when motion-based retention is enabled, the footage will continue to be recorded on a 24/7 basis. This provides a three-day buffer period to review any events containing limited motion (e.g. <5% total scene coverage), events in low light conditions (e.g. at night time), or events with far-away objects for significant events. After this three-day safety net, the camera trims footage based on its index of motion events."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could also consider drawing a privacy window over the road.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes I did consider this and wanted to avoid it in case having background footage could have been useful i.e. criminal activity but it looks like this might be the only option.
It would be nice if strict motion detection was an option that could be enabled as I am sure there are others in the same boat.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The camera should still show motion events on the timeline after 3 days with MBR enabled, but unless the motion occurs with the area of interest it shouldn't be saved.
Example from my MV52. Area of interest does not include main road into the neighborhood.
The last 3 days of video are saved, anything older is only saved when motion occurs in the area of interest.
While motion occurs on the street it's outside the area of interest and not saved. The motion thumbnail is hosted in AWS, not on the camera (you can right click on them and see the link).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the information, it would be useful if general motion detection and area of interest detection were shown as different colours.
Otherwise the option to follow industry standards but I would have thought different colours would be easier to code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Agreed, the motion detection is not up to standard yet. I was looking to see when a courier dropped off a particular package by our entrance and the MV72X gave me 200+ motion events to look at over a few days.
We have people only detection enabled and live at the end of a private lane so there are a max of 10 people in that part of the view per day.
We also get hundreds of motion events when it rains at night.
So far we've tried regular and experimental models and V1 and V2 detection and are waiting on support for more ideas.
Hopefully something can be done as otherwise the MV cameras are pretty good!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Agreed, a Hikvision camera is a fraction of the price and has industry standard motion detection. Sure the new gen cameras let you search based on the colour of the shirt someone is wearing but that basics aren't there yet.
I am having a hard time justifying any further MV purchases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki support have acknowledged the issues I'm having and are working to resolve it. Let's hope it is sooner rather than later 🤞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The option to deploy custom CV module which we have currently built and capturing events via mqtt that are being processed by the model seems to eliminate false alarms that generates in the 100's per day when default motion is enabled...
The above sample event shows how the AI in the cloud thats running off the RTSP feed is performing vs the custom model deployed on the meraki camera and being captured via mqtt..
