Timelapse is painful to use for many reasons.
My download died. Will try later.
This was addressed years ago. They used a type font that’s legible for both dark and light backgrounds. A subsequent update obliterated the fix.
Wyze cameras used to have an ftp server. They removed it. They can either bring it back or use any open source ftp software. Since they are already using open source code, it shouldn’t be a problem. Then any download manager can be used and the download can be done in the background.
Agreed. Just felt like complaining about the downloads. The lettering has been a problem for years. I hope they fixed it in 
.o
I haven’t thoroughly tested this but to agree with @ssummerlin… staying on the page to download is silly. Sometimes I even set them and nothing will be there. I can’t tell if it’s because I pulled the camera up to look at something else while it was doing the timelapse stuff and that interrupts it or if it just never runs.
I have seen this on all the cameras. I’ve basically learned to set the time-lapse and DON’T touch the cameras and that seems to ensure it will run correctly. I might be doing something wrong.
Agree with many points in this thread. I hate the design coloring/font. It’s hard to read anything. I also hate having to stay on that page while it downloads and converts the timelapse. That is really annoying. This should be an approved background process. It gets really infuriating when you have a LARGE timelapse and it fails a few times and takes forever to download/convert. I had one on a WCO that took me HOURS of not being allowed to touch my phone, and it still kept failing and needing me to restart or unpause it over and over again. It made the timelapse experience very unpleasant.
Isn’t the biggest problem that there can’t be big time-lapse? Anything above 1.9gb get trimmed out and lost and there’s no way to know how many Gb a time-lapse will take unless doing mental maths. Like 2 days should be set at max 20sec per frames.
Good question. Mine were within reason (not days but like 6 hours).
It stands to reason that a massive time lapse could fail in terms of saving the file. But, I would also think they would have a file system that is built for keeping a file open and writing to it, while not corrupting the file. File systems (unix, DOS, etc) have been doing this for a couple decades reliably.
I’m not sure what you guys are talking about, I’ve been taking time-lapse every 2nd day for years and downloading them with no issue, yes it takes about 20min but it’s never an issue.
The problem is with 2.5k resolution it fills up to 1.9gb very fast and any length above that size is just lost.
That could explain my problem. I need to not take a photo every 3 seconds. Do you have a good recommendation?
Be advised, with everyone of my “failed” TL downloads the data gets stored within the app and can build up very quickly. This is in addition to the cache that you can (supposedly) delete from within the app.
I uses System Panel 2 (Android) to show (and delete) both cash and data for each app. Depending on how much you get downloaded before it fails, and with repeated attempts, you can end up with serval Gig of data stored there. Using the clear cache file command in app settings only partially deletes the total stored cache and does nothing to free up any unused (e.g failed TL downloads) data. Be advised deleting the data like I have had to do will reset all of your app settings and reset your logon credentials. You will have to re-login and change any systems settings back. Deleting and reinstalling the app probably has the same effect, but I have not tested.
FWIW this problem has existed since day one and continues to this day.
Since we can now download TL from the internet instead of local network only I haven’t been able to finish a single download. It always fails before the end. Now the only way is by physically pulling the SD card and extracting from h264 file.
