Meraki Dasbhoard Snapshot API might be confusing at first so let's try to demystify it. After one receive the URL which is automatically generated as a result of one's POST request, the camera must then find the appropriate frame from it's recorded footage (providing that the footage was being recorded), extract the snapshot at that specific date and time, change file ownership and permission details, and finally - create soft link between the automatically generated URL and the file you requested. There is a lot going on here so one need to allow time for that image to become publicly available. We call this process a cold start and we have no control over it. It might also means that one may never get a successful response back for which one should create processes to repeat call if necessary.   Regarding the possible differences in your snapshot requests, please make sure that the timestamp includes the time zone that matches the camera time zone settings. For example, if the camera time zone is UTC+1, then the request should include the time zone and be formatted as follows: "2019-10-24T13:30:00+01:00". ... View more

Hi @PhilipDAth, how are you?   You have asked some good questions here.   Web Hook is an excellent option for anything motion detections related. Time sensitive so that's what you want.   You can use the MQTT topic as a trigger to fire away a POST request to the Meraki Dashboard Snapshot API. Just bear in mind that obtaining a snapshot directly from a camera will take anywhere between 6 - 12 seconds per each request. MQTT topics distinguish between a person and a vehicle, but only on the MV72. ... View more

Hi @Rafaetero, I can confirm that I have the same issue here on my end.   Cheers, P. ... View more