Timelapse is broken on any camera using Plug-in version 3.7.0.17

Cameras
, ,
1

Timelapse is not working on several of my cameras. I finally narrowed it down to the Plugin version. Steps to reproduce:

Go to Timelapse hit start, navigate away from timelapse screen in any way then come back. It will be ready to start another timelapse as if you never started one previously.

No matter what you do, no timelapse is ever recorded.

Wyze app hotfix - Released 9/8/2025
2

Are you positive? I’ve been seeing the behavior you’re describing with Cam v4 recently because other users have reported it in a couple of topics.[1][2] I find that if I don’t revisit the Timelapse screen (to cause the apparent interruption) the time lapse shows up in my Album. Even if I do navigate back to the Timelapse screen after scheduling a recording and before it has completed—and the Timelapse screen isn’t showing the current schedule but has reset as if it’s waiting for the user to schedule a new time lapse—I’m still finding the recordings in my Album for that camera once the appointed end time has passed, and I can download and view those.

I still think it’s a bug that has persisted since app 3.7 RC and made it from the release candidate into current production. I’ve noted this in yesterday’s app release topic because I’m seeing that UI behavior in testing today despite the availability of the completed time lapse recordings in the Album.

  1. ↩︎

  2. ↩︎

3

Yep, tried that. I still get nothing. I just setup a 5 min timelapse and left it on the screen until it finished. Nothing saved.

4

Same issue here with cam v3 running firmware 4.36.14.3497. If my screen turns off or I switch apps it just goes back to the start timelapse setup screen

1 Like
5

FYI:

I haven’t yet tested this, but, like I indicated above, I’ve been able to retrieve time lapse recordings even when it appeared that I interrupted the process in the app (based on what the UI was communicating to me). Hopefully this resolves both the UI issue and the actual recording issue that some users have been reporting for a while.

6

Still not working for me. It did fix the part where losing focus in anyway reset everything but still, no video is ever recorded. I tried canceling and instead of asking me if I wanted to save the video it just asked if I wanted to cancel the time lapse and it didn’t even attempt to save it. I also tried letting one run all the way thru but still, nothing was saved.

7

Updated. Still broken for all V4 cams.

Will not save the time lapse.

Manually stopped it but no option to save any video.

8

I haven’t yet tried to record a time lapse with the v3.7.8 hotfix, but a few things come to mind:

  • Another user (I think a long-time beta tester) reported successful time lapse recording with the 3.8β app on a Cam v4 yesterday. I’m trying to determine whether or not the production hotfix was tested prior to that.
  • Does the microSD card you’re using have sufficient free space for the time lapse you’re attempting? (I would expect the Cam to just overwrite older recordings—Continuous or Events Only if you’re doing that—if it needs to release space for a time lapse, but I’m not positive that this is what happens.)
  • If your camera is physically accessible without significant effort, then what do you see on the microSD card if you pull it and try reading it with a PC? What I see on the card I just pulled from a Cam v4 is a time_lapse subdirectory in the root, and that holds several time_Task_{##########} subdirectories, where {#} is a single digit. Within each of those, I’m finding a record.h264 file, and I can open and play those recordings in VLC. Note that these recordings were scheduled/recorded using previous versions of the Android app as I described above (the same versions that you and others have been reporting errors with).
  • If you can see those files on the microSD card but the app isn’t showing them available and retrieving them for you, then I wonder if you have some cache or other data corruption on your mobile device and if deleting that and refreshing some of your data from Wyze’s servers would fix it. Have you tried just clearing the in-app cache recently? Sometimes I find that doing that ( Account ➜ App Settings ➜ Cache File Size ➜ Clear) and potentially clearing the Android cache for the app (long-press on the Wyze app’s launcher icon [on the phone’s home screen or wherever you tap to initially open the app] and then tap App info in the pop-up menu; tap Force stop on the App info screen [may need to tap OK to confirm] and then tap Storage & cache; tap Clear cache on the Storage screen; back up one screen [back to App info] and then tap Open) fixes some temporary glitches.
  • As an Android user, it’s easy to enter and leave the beta channel for the app at will, so that might be another option for you if you want to give it a try with the v3.8β app.

Since I was able to successfully schedule, record, and retrieve time lapses on a Cam v4 using a previous production app version, I’m not sure how much useful information my testing with the v3.7.8 hotfix will yield, but I might try that at some point anyway.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.