I’m not sure what happened, but time lapse stopped working for both my v4s approx. 24hrs ago, but it continues to work normally for my v3 and v2. When I start a time lapse (using the updated interface), it shows the stop button. When I then exit the time lapse screen and go back in, it doesn’t show the stop button but instead behaves as though a time lapse hasn’t been started, with nothing showing in Album.
Is this a new bug?
I’ve three v4s.
On my iPhone running Wyze App Beta 3.7.5 (3) I was able to set a timelapse on two of my v4 cameras, leave that screen, return to the Timelapse page, I see a “Stop” button down below.
On my ‘ancient’ Galaxy Note 8, running Wyze App v3.6.7 (694) on the 3rd v4, I did the same, and upon returning to the Timelapse screen:
If I click on the green button below:
So I assume the timelapse is still running.
Maybe try clearing the App Cache and try again?: Account > App Settings > Cache File Size > Clear
Updating my own thread: I found that it stopped working for me on the recently updated Android app version 3.7.0.695. Rolling back to 3.6.7.694 and it’s working again.
Intersting. How does one do that?
I got the APK bundle for the older version from APKPure (it’s also on APKMirror).
I can confirm that it seems to work properly in the previous version of the app!
For whatever it’s worth, I just tried a brief time lapse with a Cam v4 on firmware version 4.52.9.3415 using the Android Wyze app version 3.7.0.695, and that recorded and downloaded as expected, so I’m not quite sure what the issue is, but it may be worth looking into.
Welcome to the Forum, @sshonweb! 
In case Wyze monitors this forum for bug reports, time lapse on Android app version 3.7.5.697 still doesn’t work for me (Cam v4 firmware 4.52.9.3415).
That would appear to be a public beta release, so for visibility to Wyze I suggest posting to the relevant Beta topic with a Log ID. I’m not finding a topic that mentions that exact version (they don’t always post announcements immediately), so for now I’d be inclined to post to this one:
If it’s an app issue, as it seems to be so far, then that should help bring it to their attention so that it can be remediated before the next production app release.
Just to add more data to what I previously posted:
That was absolutely true, and I decided to also try what @Tish reported in a related topic:
I notice if I set and start a time lapse and then back out of the Timelapse screen to the main Live Stream screen and then tap the Timelapse icon again or if I let the phone display time out and go to sleep and then unlock the phone to show this Timelapse screen again, then the button at the bottom is now Wyze teal with “Start” in red. Something funky is happening, and I’m going to see if I can get someone to look into this.
2025-09-02T17:32:14Z Edit: Despite that funky behavior with the button, the latest short test time lapse I attempted did record. It showed up in the Album, and I was able to download it to my phone.
An additional bit of information:
After setting the time lapse using a device with Android app version: 3.6.7.694, the above is also what I’d see when I go into Timelapse on another device with 3.7.5.697 (I got this from the Play Store and was unaware that it’d still be a beta)
Thanks!
I’m not sure how iOS beta testing and TestFlight work, because I don’t use that platform, but my understanding of the Android beta program is that enrolling switches you into a different channel for Wyze app delivery through Google Play Store. When I enabled that and did a refresh of the Play Store app on my phone just now, I saw that what it’s offering me is version 3.7.5.b696. That’s the latest beta version I’ve seen posted (as I linked above), and it has the “b” that they tend to add to their beta app version numbers. I’m not seeing the version you’re reporting in Google Play Store, here in the Forum, or on the Release Notes & Firmware page, so I can’t account for that. Just going by the version number you’ve posted, though, I was speculating that it might be another beta, but I’m not sure. 
You’re welcome! Unless someone from Wyze chimes in here, I’ll try to update this topic if/when I learn more.
That’s an interesting observation. You’re right that 3.7.5.697 isn’t reported in the Play Store:
It is oddly what’s reported by Android:
I appreciate the screenshots. 
I’ll be interested to learn what someone from Wyze might say about this.
Time lapse is still not working.
Is that with the most recent app version? I mentioned in the announcement topic for the most recent production app release that this issue has been reported in recent weeks and may be an app problem. If you can verify your app version, then posting to that topic with a description of your issue might help to get it some attention.
Also, which app platform are you using? Your profile indicates “Both iOS & Android”, and an Android user in another topic reported successful time lapse use when trying it on an iPad. Providing more detail about your experience can be helpful, and you might want to try it on iOS to see if you get better results.
Welcome to the Forum, @cooliochix!
With the latest app update a couple days ago (v3.7.5(697)), the timelapse quit working on my V3 cameras as well. V4 quit working a couple weeks ago. Now the timelapse only works on my OG. I suppose they will break that on the next release?
That’s frustrating to read, and I this seems more and more like it’s an app-specific issue. Other users have been reporting changes to the Cam v3 UI with recent apps (both public beta and production), so now reading that you’re having this issue with time lapse on Cam v3 doesn’t surprise me as much as it should.
I’d still recommend logging it, opening a ticket with Wyze, and including the Log ID in the ticket to try to increase their awareness of the scope of the problem. With anything that seems to be related to changes introduced by a new app version, I also think it’s a good idea to post about those problems to the announcement topic for that particular app and/or firmware version (whichever seems to be the cause of the problem), and I linked that for the latest app in my previous post.
Welcome to the Forum, @ryan.devos @RDV![1]
FYI:
