@PhilipDAth  :_( ... View more

If you have motion based retention enabled, exporting video will only include the motion events. The final file concatenates the events and puts title cards between the video segments with the date and time each event starts.   For example if you select an export which covers an 8 hour time span, but there is only 1 hour of activity in it, your export file will be one hour long. ... View more

In this case I would recommend raising a support case to investigate what is going on in more detail. ... View more

@PhilipDAth the support person you spoke to should not have given you this feedback. Please re-raise the case and ask for them to investigate it. If you run into issues ask for it to be escalated.  ... View more

MV 4.0 contains significant under the hood changes that we have been working on for the last 12+ months. This means this firmware contains many tweaks, updates, and fixes which improve camera functionality. Due to this scope, it is also the reason why it is not possible to downgrade from this firmware.   It is highly recommended all customers move to this firmware, and new cameras will be shipping with this firmware.  ... View more

You are most likely exceeding the PoE delivery capacity of the switch port which is cutting power to the camera. Without the heater the camera will draw <15.4W for normal operation (same as the MV22). With the heater on it will draw more than 15.4W (PoE) and if the IR LEDs are also active it can draw up to the maximum 25.5W as stated in the datasheet, which requires PoE+. ... View more

This sounds strange. Please can you re-open or re-raise the ticket with support and send them a picture of the issue? Then ask them to forward it to me (George Bentinck) and I will take a look. ... View more

The Instant Export button is just amazing. Complete game changer in how quickly you can now export video. ... View more

Parking my MX-5 🙂 ... View more

Additional controls to help with the increased sensitivity of the new Motion Search 2.0 algorithm are on the way.   All outdoor cameras are susceptible to insects trigger false alerts due to the infra red illuminators making them appear very bright to the camera when they fly close to the lens. External or ancillary IR illuminators completely resolve this issue and are recommended in environments where there are lots of flying insects.  ... View more

Note that we don't support MV22 for outdoor deployments. Although the environmental conditions maybe benign, other factors can impact the quality of the camera's video or cause a failure. For example insects will try and get inside the camera and can cause a problem. Ants in your camera is not covered by the warranty ...  ... View more

This link has the relevant details:  https://documentation.meraki.com/MV/Physical_Installation/MV_Mounting_Options_and_Guidelines     ... View more

Please note that the MV21 & MV71 are now End of Sale (EoS)   https://meraki.cisco.com/lib/pdf/eol/MV21_MV71_EOS_Notice_Update.pdf ... View more

Please raise a case to make sure something unexpected is not happening. If you have motion based retention enabled it should have all of the last 72 hours (3 days) of video. ... View more

With most ML CV implementations the bounding boxes for the detections are rendered in the video pipeline and burnt into the final video. With MV we don't do this, instead we use the browser to draw the bounding boxes in real time using the co-ordinate data from the ML CV inference data stored in the Meraki cloud.   We do this for a couple of reasons. If the bounding boxes are burnt into the video then it means we would have to create a duplicate video recording to ensure there is a recording without boxes should that be what a customer wants. Secondly it allows us to render visualizations for many other things we may want to show in the  future. These would just be additional overlays as we update the ML CV model with more capabilities.   What are the potential downsides of this? As the video is coming from the camera, and the metadata for rendering the boxes is coming from the cloud, they have to become synchronized. As the video data is much bigger (>1000kbps) than the metadata (<10kbps) it can take longer to load and lead to the boxes appearing and moving before the associated video has loaded. This is particularly noticeable when using the cloud proxy remote view over a small Internet connection. These will sync up as the browser can catch-up with both data sets. ... View more

Motion Search 2.0 and Motion Recap are slightly delayed and will be coming out later this month. This was primarily to ensure full support of our GDPR feature set for EU customers. ... View more

We are looking at mobile app improvements for MV, but at this time I don't have any updates to share. It is high on our priority list, but we want to make sure we do it right and that takes time. ... View more

We are looking at updating the site, but we don't have a date yet. ... View more

Today the mobile app doesn't support the video wall, but we are looking at it for future updates. However, we have optimized dashboard for videowall use in mobile browsers and I find it works really well.       ... View more

So I think I've just been too impatient, thinking that when I click the blue bar I'll see something, when in fact there has been something, I just have to wait a full minute or so until it shows up.   The way the indexing of the video files and people detector meta data works means there could be offset from the actual event by +/- 30 seconds.  A little patients normally pays off 🙂 Alternatively just press number 2 or number 3 on your keyboard to watch the playback sped up. ... View more