Event Video Skips during playback

Help Please,

I reached out to WYZE support about two weeks ago but I haven’t received any feedback.

I have several OG cameras that I’m using indoors. I’ve noticed that the events have been skipping when playing them back. The event time also shows 5 minutes on the event page but when you play the actual video, they are less than a minute, usually 12-30 seconds long.

Another strange thing when watching the video, the time in the lower right corner says 15:04, but then jumps to 16:04 and jumps right back to 15:04, jumps again to 16:05 and then back to 15:05.

I do have SD cards in each camera. When Support asked me for the TXT file, none of the SD cards had anything in the file (they were all 7 kb file size)

I have tried:

  • restarting the cameras,

  • Reset Services,

  • removing the SD card,

  • reformatting the SD card,

  • signing out of the app and signed back in, nothing helps.

I’ve stopped short of reformatting all cameras.

My firmware is up to date. I do have automations on all the cameras to turn on and off at a set time.

Any thoughts would be appreciated. thank you

Some of what you’re describing (event duration showing as 5 minutes, skips) and the fact that you’re using a subscription (shown in your Person and Pet event tags) makes me wonder if what you’re seeing is the same issue described here:

If that’s the case, then Wyze is soliciting Log IDs and MAC addresses in order to determine the root cause. Please take a look at that and let me know if that seems to fit what you’re seeing.

The video timestamp jumping around is goofy, though, and I see that in the video you shared, so thanks for that illustration. I don’t know what’s causing that or if it’s part of a constellation of symptoms currently affecting subscribed Cam OGs. :man_shrugging:

Hi, I saw this post, but took their issue as an issue with the SD card and continuous recording vs (what I believe to be) videos on the event recording page. Maybe they are related??

I followed two support persons instructions for removing the SD card and placing it back into the camera in order to generate the TXT file, but there’s nothing in the file?

Here were the instructions, maybe I’m doing something wrong (Please note: I didn’t hear a ding after reinserting the card so I turned the camera on):

To submit a microSD card log:

  1. While the device is still showing as “offline”, remove the microSD card from the device, and wait a few seconds before re-inserting the same card or inserting a new microSD card by pressing it in until it “clicks” into place.

    • The camera will then make two “ding” sounds, usually within 30 seconds. It is important that you hear the “ding” sounds before taking the next steps.
  2. Remove the microSD card from the device, then insert the card into a computer.

    • If you do not have a microSD card slot, you may need an adapter.
  3. On your microSD card, there will be a root or log folder with the device log. The files are named xxxxx_log.txt.

    • If there are multiple logs, select the most recent log file.

I appreciate your response

I tried to generate a log again based on the WYZE site instructions, the only way I can get the ding sound (of the log generation) is if I turn the camera on, this is what I see:

the Time Unknown files just showed up on this last attempt to generate a log.
As you can see there is nothing in the TXT file. The gemini log numbers don’t match my camera mac address.

One other thing I have noticed this morning. I’m attaching two videos, where the time of one video overlaps into the second video AND they both jump from 2:29 to 3:29:

Video 1: 20 sec video from 2:28:26 - 2:29:38 (jumps to 3:29 for a sec then back to 2:29)

Video 2: 14 sec video from 2:29:04 - 2:29:39 (jumps to 3:29 for a sec then back to 2:29)

I’m attaching the screenshot from the events page, oddly for one event it doesn’t show a picture of the room but a camera pic.

I didn’t notice where Crease mentioned the following so apologies for repeating but please note the steps to workaround the issue:

You’re experiencing the same OG issues as seen in at least two other posts including this post here.

Please check that out because there are some settings you can try that likely resolve the playback and SD card issues but it is NOT a fix it is merely a workaround until Wyze actually comes up with a solution. As of now there are support tickets out there but the more the better. You’ll find a Wyze agent in this thread who’s asking for DM’s of support ticket numbers and MAC id numbers for affected OG cams that he is direct sharing or something like that with engineers.

Here’s the steps for the settings mentioned above:

  • Camera settings

  • Event recording

  • For Recording Preferences

  • Change to All Events

  • Tap Customize Detections

  • Uncheck everything except Other Motion and Other Sounds

Good luck!

Hi, thank you for your response, I’ll check the other posts.

My settings were very close to what you suggested, but I’ve gone ahead and unchecked the Person and Pet.

1 Like

I unchecked as you suggested and checked all cameras and that does appear to be a fix.

I’m also attaching my Wyze Ticket 4748489, in case someone at WYZE sees this.

I’ll also provide support with my posting here in hopes my analyses provides any more insight, since they’ve yet to get back to me (Disappointing customer support).

thank you for your help

1 Like

You’re welcome! Credit appears to go to @rick5 for finding the workaround and forum maven @Crease for spotting their post and suggesting a repost over at the @jeffermc post, where I’ve been hanging out.

Apologies for taking some time getting back to this. I’ve been pulled in a few different directions, lately. I want to respond to a few things here.

I think so. I believe there are several topics now discussing symptoms of the same root problem.[1][2][3][4]

I think the double-ding chime sound is what the Cam does when it recognizes microSD card insertion, not something that’s specific to log creation. I believe it’s necessary for the Cam to be on for this recognition.

I suspect that the Cam didn’t have a Wi-Fi connection at the time those files were generated. My understanding is that the Cam requires an Internet connection in order to get the time (because there’s no internal battery to keep time on a real time clock when these are powered down). I think the Cam probably generated those subdirectories as a means of logging some kind of information without having access to actual time.

If your comment is about the gemini_20260201032847.log file in your screenshot, then I believe that’s a date+time stamp (YYYYMMDDHHMMSS) and not a MAC address. That’s what it looks like to me, anyway.

Are those downloaded cloud events or recorded from microSD playback? Either way, I still think that the jumping around video timestamp is weird, and I haven’t seen anyone else describe that with this particular issue. I’m also envious of your cat’s teleportation skills. :grin:

I didn’t mention the work-around, because that doesn’t really solve the problem. So far it seems to be the best temporizing measure I’ve seen suggested, though—at least until Wyze fixes this—so thanks for dropping that in here. :+1:

I did mention that above, yeah. :wink:

I passed that along, and I also want to reinforce what I noted above:

The work-around of disabling certain detection tags/notifications isn’t really a solution, I don’t think, because the issue itself is still affecting users who are doing microSD recording with their subscribed Cam OGs. Hopefully submitting logs and then passing those Log IDs to the Wyze Team member as requested in that related topic will help the engineers to determine and remediate the root cause of this issue. I’m still recommending log submission for this issue, especially in your case with the goofy changing time stamps.

Thanks for the plug. I’m just trying to help the community keep an eye on things, and something like this that is affecting a number of users over several topics really gets my attention.


  1. ↩︎

  2. ↩︎

  3. ↩︎

  4. ↩︎

2 Likes

First off, my cat is a superhero :smiling_cat_with_heart_eyes:

Can you clarify, since I couldn’t get a response from Support on generating the log?

Should I turn on the camera, remove the SD card, and then put it back in? I’ve tried several methods but the TXT file still seems empty.

I appreciate your follow up and help.

1 Like

I’ll take your word for it. Mine’s more of a sleeperhero. :grinning_cat_with_smiling_eyes:

Yeah, what I’d suggest is submitting a log through the app, as I think that’s what @WyzeJasonJ was requesting in the other topic. See “How do I submit a log in the Wyze app?”. That should generate a Log ID, which you can PM to Jason along with the MAC of your Cam OG.

You could try that—and I think you want the camera turned on when inserting the microSD card anyway—but my understanding of what Wyze is seeking from the other topic is app-generated Log IDs.

Hopefully that makes more sense. If it doesn’t, then please let me know, and feel free to “@Crease” me to get my attention. :grin:

1 Like

I just did logs for each camera, didn’t know if I needed for each camera or just one time (but did for all 3 cameras);

I sent a DM to Jason

the gemini log, I just mentioned about the MAC address because the suport page said something about the report having your MAC address as part of the file name.

thank you for your direction

1 Like

I’m not sure what’s included in logs, so I think that’s probably a safe bet. :+1:

You’re welcome, and thank you for contacting Jason. I hope that data helps them to locate and resolve this issue for everyone affected.

Maybe I’m confused but the agent kept telling me to remove the sd card while offline, hear the ding, then remove card and take it to a computer and send that TXT file

but that TXT file appeared empty (7 kb file size)

I’m not sure how to account for the Wyze Wizard’s scripted instructions, and I also don’t know if they’re considering that there are different Wyze Cam OG generations (a newer revision was released last year; they use different firmware versions, but I don’t know if that means they create microSD card logs differently), but I think sending the app logs as Jason requested is probably a better route at this point for getting the requested information directly to the engineers.

1 Like

Hi, @k.whittenburg there’s been murmurings about the issue having been quietly solved. Our other forum thread has more details and comments from users who’ve seen service restored without the side effects that’ve been discussed in both of these topic threads. I am on like hour 40 with smart detections enabled without any of the related negative symptoms. If you’ve been contacted directly by the support team, notifying you of any fix or updates to the issue, please drop a line on our other thread as from what I’ve seen, none of us have heard official word yet.

good luck!