The five minute cool-down is a very popular topic of concern for many posters, so I’ll skip the review. We understand this is to limit the cloud space usage so Wyze can continue to provide this service, but this gap in notices is problematic. Who has time to sit through five minutes of playback video to see if there is something or someone that came by after that last insect? Can there be a compromise that doesn’t significantly increase the storage space for Events, such as placing a record in the Events log that signifies motion during the cool-down period and not including a video, but the mm/dd/yy & hh:mm:ss of the motion?
Solution: If an SD card is installed, there is an alarm folder containing motion triggered event thumbnails. This is at the heart of Events. Unfortunately, these records are subject to the five minute cool-down and should represent a one to one with cloud Events.
I propose in this Roadmap to keep the five minute cool-down for event records being sent to the cloud so the current Free Cloud Videos remain consistent for what Wyze advertises. (Paid cloud storage is a separate issue so please post those comments in the appropriate thread.) Change storage of thumbnails in the alarm folder to a cool-down of 30 seconds (so constant movement doesn’t blow out the SD card capacity) so users will have visibility of continued motion with the cloud only, having the 5-min cool-down. Also create visibility within the app of alarm folder thumbnails, so users can ‘at a glance’ have confidence that motion within the cloud cool-down is either critical to view and act upon or is insignificant and can be ignored. The thumbnail filename contains the YY/MM/DD and HH:MM:SS of the actual trigger motion, so going to that point in the Playback timeline should be easy. The ability to click and go there, even better!
This also give users visibility of events in cases of connectivity issues with the cloud servers.