@Banfield75 Agree with @PhilipDAth and wanted to add regarding capturing license plate information (or facial features for example) generally requires 40 pixels per foot or better, just a rule of thumb. There is a pretty good discussion on PPF here https://documentation.meraki.com/MV/Viewing_Video/Understanding_Image_Quality_on_the_MV32 That is an MV32-specific KB article but PPF applies to all the cameras. Consider using a camera placement calculator like the Meraki specific one here https://meraki.cisco.com/products/security-cameras/site-survey or a 3rd party tool like https://calculator.ipvm.com/ to give an idea of distance, FoV width and PPF to have a reasonable plan for camera placement to meet your requirements. On the motion search and timeline, I'd respectfully say that's just something we get used to. Any new system will likely be awkward at first. With simplicity being the true goal, I'm sure the developers designed it to be as simple as possible but also with the highest functionality. And those two things tend to be mutually exclusive sometimes. Note that you can simply click on the calendar tool and immediately select a day, or a time, or also just type into the text box, which can process natural language processing, such as "yesterday lunchtime" or "3 days ago" or "last friday at 7am" for example. On the wind question, I do get some false positives on my MV72 on occasion during heavy rainstorms, but never on the very windy days. If it might be pole mounted, I'd imagine there could be some sway that's triggering motion events? Note that there is a "sensitivity"setting you can adjust on a per-camera basis, hopefully that would help. In addition, perhaps you could alert on people events only, so any swaying motion won't trigger motion alerts unless there also happens to be human motion detected as well. Also, on the diagonal (or freehand) areas to record (or not) I understand your point, and things like Sensor Crop and Privacy Windows won't really get you there. It's probably a difficult engineering challenge actually, allowing a freeform or diagonal detection area, given the way a camera's field of view is broken down into X/Y coarse cells and 16x16 macroblocks and the way the motion detection algorithm works. Still, please do make wishes in Dashboard, and bring this up to your local Meraki team so they can create (or append to) a feature request for this functionality.
... View more