My girlfriend and I bought four Cam-v4 cameras. All the cameras were initially set up under her Wyze account, and she uses an Android phone. Initially, she shared the cameras with me, and I had created my own Wyze account, and my phone is iOS.
We set up all the cameras to individually record time lapse videos overnight. In the morning, she is able to download all the Timelapse videos and view them properly in the album tab of each camera on her Android phone.
For me (on iOS), if I go into camera 1 first, I can download the time lapse video for camera 1. However, if I go into cameras 2-4 after that, they will all display the time lapse video for camera 1, not giving me the option to download their individual time lapse videos. This is not a camera 1 issue. The next day, if I download the time lapse for camera 3, then all the other cameras will show the camera 3 Timelapse only.
At first, we thought this might be a permissions issue, since she shared the cameras with me. However, I logged out of my account and into her Wyze account on my phone (iOS 17 pro, with iOS 26.2, the latest firmware), and the issue persists with her account on iOS.
I should say that I don’t use iOS and haven’t tried downloading a time lapse recording from a Cam where I have shared access, so I can only speculate at this point, and I don’t know how useful that’s going to be. Is your problem potentially related to a file name/location issue on iOS?
When I downloaded a time lapse recording from a Cam v4 (as the camera owner) a few minutes ago, it saved to my Android phone several layers of subdirectories within the DCIM folder and had a generic title of Time Lapse.mp4. This was several layers deep, though, so within the path it ends something like this: /timelapse/{MAC_address}/{##########_##########}/video/Time Lapse.mp4. I’m not sure what the 10-digit-number_10-digit-number string means after the device’s MAC address, because it doesn’t appear to correspond to start/stop times, but I suspect that saving the actual .mp4 file in these subfolders (especially the MAC address) is what’s intended to keep that time lapse recording specific to that Cam v4’s “Album”…at least on Android.
Two things I’d try on iOS:
If you have an app that allows you to navigate the phone’s file structure (it’s been over 10 years since I’ve used an iPhone, so I don’t recall what’s available), then see if you can investigate how/where the time lapse recording is being stored immediately after you download it from one of the Cams. If it’s not being saved in a unique path or with a unique filename, then that could be the problem.
Download a time lapse from any camera (say camera 1). Find the file and move it elsewhere and/or change its name. Then try to download the time lapse from camera 2 and see what happens.
If you’re doing time lapses concurrently on four different cameras, then I wonder if iOS is seeing an existing video file and refusing to overwrite that with a new file with the same name/time/etc. If so, then that seems like a bug to me, but I wouldn’t really know without a more detailed observation of the app’s behavior and how it’s storing these downloads on iOS.
Based on your suggestion that it might be naming all the video files the same, and that might be the problem, I set the recording times for the time lapse videos to be staggered by one minute, so they all had different start times. The next morning, I was able to download 3 of the 4 time lapse videos! This seems to be a workaround for the situation. I’m not sure why 1 of the 4 videos isn’t showing up, but seeing 3 of 4 instead of 1 of 4 is progress.
Edit: it looks like we’re missing the 4th video on Android as well, so at least the iOS/Android issue seems to be worked out.
Thanks for taking the time to report an update. I’m glad to know that you’re seeing some progress, though the thing about the missing fourth video seems like a troubling new development. Hopefully that’s just a temporary glitch, but it’s something I’d keep an eye on, especially if that video is unavailable to both phones for some reason. That could also maybe be a card issue, so I wouldn’t hesitate to try a different microSD card or to do a full “overwrite” format with SD Memory Card Formatter if an in-camera format doesn’t resolve that. You’ll want to be sure you’re using quality microSD cards, too.
Staggering your time lapse schedules was a good thought. I haven’t ever tried running several in identical Cams at the same time, though I would expect the app to be smart enough to handle them all appropriately. Apparently that’s what the Android app was doing if I understood your initial post correctly. I don’t know if the iOS app has been coded differently to account for the way iOS forces things to work or if the iOS app’s handling of the recording downloads is problematic because of an internal bug that isn’t accounting for something as it should. In any case, I’d probably be inclined to submit an app log and then follow that by opening a ticket with Wyze Support, referencing the Log ID and this discussion in the ticket. Although I haven’t ever seen anyone else report this issue, I imagine there are probably other users who run concurrent time lapses, so this seems like something the engineers should be aware of so they can fix it in that version of the app.
Something else you could try if you haven’t already: Pull the card from the Cam v4 where you’re missing the video and pop that into a PC. You should see a time_lapse subdirectory in the root directory, and within that are probably several time_Task_{##########} subdirectories for time lapse recordings you’ve already made or scheduled if you haven’t already reformatted the card. Each completed time lapse folder should have a record.h264 file within it, and you should be able to view that file directly from the card or copy it to your PC and do whatever you want with it. Be aware that some video players might not want to play this format natively, but I’ve had good results with VLC media player. When you have that raw file, you can use other software (e.g., FFmpeg, HandBrake) to convert it to another format of your preference (e.g., .mp4).
I haven’t ever tried running several in identical Cams at the same time, though I would expect the app to be smart enough to handle them all appropriately. Apparently that’s what the Android app was doing if I understood your initial post correctly. I don’t know if the iOS app has been coded differently to account for the way iOS forces things to work or if the iOS app’s handling of the recording downloads is problematic because of an internal bug that isn’t accounting for something as it should. In any case, I’d probably be inclined to