Not to mention the lack of features when compared to other vendors. I believed in the MV line, and somewhat still do, but Cisco Meraki need to speed up development because the MV system is to far behind.
I get the API sense angle, tying to get customers to build their own apps, but the API is clunky and slow, makes it difficult to build anything that is commercially viable - and I think Meraki know this otherwise why would they open up the RTSP stream.
The MV cameras are well designed, the MV12W can spit out a fantastic image and we have seen them work well in well lit environments, as does the outdoor model. The MV32 however is terrible. The biggest issue is the storage. We had an MV32 being trialled in a commercial environment which was very busy before COVID, where foot traffic is now almost non-existent other than cleaners passing by - the MV32, with all quality settings (only has an 8.4 MP lens which is rubbish compared to standard 12 MP you would expect in a fisheye) set to the highest levels is only able to record 8 days (with motion retention enabled) - 8 days in a low traffic environment? thats ridiculous considering most customers will want at least 30 days. So then you have to purchase the cloud backup license, which just keeps adding to the cost. Now what if it were a large retail store where the customer wanted to deploy say 30 MV32's with a minimum of 30 days storage - let's discuss the uplink bandwidth implications of deploying such;
MV32 with motion recap enabled (and why should we have to disable it considering its a key feature!!!)= 200Kbps at idle x 30 = 6Mbps
MV32 with cloud backup license enabled (per camera to achieve min 30 days) = 1000Kbps x 30 = 30Mbps
36Mbps just to run 30 cameras with cloud backup. Hardly a solution when a org may need say 100+ cameras on an internet connection here in Australia.
