New V3 hangs after about 5 hours

I bought two new V3 cams. One over my driveway is working perfectly, and takes amazing videos. The one over my yard takes amazing videos, but hangs every day. It’s not a timeout or a wireless connection, because it starts working again as soon as I restart it. This weekend, I’m going to let it die, then check to see if it’s recording to the flash drive when it appears to be hanging.

I’m a little frustrated with the new cam, and even more with Wyze Supports complete radio silence after I opened a support ticket a couple days ago.

So I’m hoping somebody in the community forum has some ideas, or whether this is a systemic problem and I should just return the cameras.

Thanks for any advice or thoughs on “next steps”.


1 Like

The only thing I can think of is delete it from your app and then add it back in. Maybe something that simple will resolve the problem? It’s worth a shot anyway…

Best of luck!

I have the same issue, along with many many others. I hope Wyze fixes this soon.

I received four v3 cameras and two have gave me problems in the first two weeks. They say one is hardware issues and got up this morning to find a problem with another. Camera is on but says it is off line and cannot be turned off or controlled by app. I had to unplug it and plug back in. Too many issues with my v3’s.

Me and other users have had similar issues. Hoping its a software issue that can be resolved with a future update.

Just FYI, I just opened support ticket #931313 for this issue. I would suggest everybody else do the same. I realize these are brand new products, but having them go offline after a few hours kind of defeats the purpose of a camera in the first place.

1 Like

I did when first one quit on 12/09/20. They gave me a ticket number.

Sending my 4 V3 cameras back. Too many issues. I need reliable cameras. These should not have been sent out with these bugs.

1 Like

I agree @parkerpress :slightly_smiling_face: Open a ticket with Wyze is the 1st step.

  • Create and send in a log file: Please recreate the issue and then go to Device Settings > Wyze Support > Submit a Log.
  • When you’ve sent it in, please post the log file number to your open Support Ticket.
    Wyze does not automagically view and analyze unassociated log files. Thanks :relaxed:

Thanks for the info on how to submit a log and attach it to a support ticket. Wyze does not make it clear how to do this. I really appreciate the guidance.

I’ll get my logs in next time the camera “hangs” (and add a new log each time the camera hangs)


1 Like

Hi @parkerpress Good job!
They probably only need one good Log unless the problem is different or new.
If you don’t hear back in 3~5 days post your ticket & log numbers here.
We’ll see if one of the Mavens can help get it noticed. :slightly_smiling_face:

You might try using the V3 w/o the uSD card installed. If there is a bad cell on the uSD card, the camera can hang while it is trying to write.

Not the solution, but certainly a work around. If your cam is going offline every 5 hours, setup a schedule to reboot it every 4 hours. I’ve noticed that if I power off my cable modem my v3 flakes out and won’t properly populate events. The playback is there, but no events show up in the app. I simply restart the cam via the app and all is well again.

I had a similar issue with my v2’s when the WCO first hit the streets and WYZE added functionality to the app for the WCOs and also upgraded firmware for the v2’s at the same time. I have always rebooted my WiFi AP once per day at a given time. I now reboot all of my cams about 10 minutes later, one by one a minute apart from each other. Granted a person shouldn’t need to do any of this, but it is what it is and only has to be setup once. Then it is completely automated.

You must be new to Wyze “jargon”.

“Events” are camera recordings saved on online servers. “Playback” are camera recordings saved on the local SD storage.

If power down your cable modem, your camera can’t upload to the servers.

No, I’m not new to WYZE at all. Please allow me to clarify. If I bounce my cable modem or my WiFi access point, my v3 will no longer display events until I restart the camera (even though both the cable modem and AP are back online). Fortunately the playback functions continue to record to the microSD card the entire time.

1 Like

Some new notes/observations:

  • When the recording-to-cloud stops, so does all local recording. No new .jpg files in “alarms”. No new .mp4 files in the “record” directory.
  • Turning off the camera and turning it back on does not “reactivate” any recordings
  • Restarting the camera re-enables recording and alarm records to the SDHC and to the cloud.
  • I “swapped” the camera on the side of the house with the V3 over my driveway, so I should be able to tell if the problem moves to “driveway” (from “west side”) fairly quickly.
  • I pulled both flash cards, reformatted them in my Mac, then added them to the “other” camera (so neither camera has the same flash drive it had before I swapped positions). I also reformatted them in the camera, then turned them off, and back on “just in case”.
  • I tried to peek at the logs, but they are encrypted. If anybody knows how to decrypt them, I’d be interested in learning.

More information will be posted tomorrow.

So after swapping cameras and using new flash drives, the problem followed the camera… So it’s something with the physical camera, not the flash drive, the cabling, or the wireless connection from where it started. The other camera continues to operate flawlessly in it’s new home, but this one still shows the same problems.

At @Known1 suggested setting up schedules to automatically restart the cameras every six hours. So I tried that. I don’t think it worked. The restart at 6am might have been attempted, but at 8am, the camera was hung again. I ran the “Restart Camera” option manually and now we’re back online again.

I’d be able to assist in debugging a lot more effectively if there was a way to interpret the logs locally, Has anybody been able to figure out how to read the logs from the flash drive?


Sorry to hear you’re still having problems. Actually I suggested a schedule reboot every 4 hours. My logic is if the camera hangs every 5, reboot an hour before the known hang time. I do find it odd that your scheduled reboot at 6 hours didn’t work, but a manual restart through the app did. I believe they do the exact same thing.

I doubt anyone has worked out the unencryption routine for the logs. If by chance someone has, I suspect that person would never share that information in a public forum.

OK. I’ve added additional reboots to every 3 hours of every day. I found that odd that the scheduled reboot is apparently acting differently than the one triggered through the UI. I’ll keep an eye on it today.

And I’m baffled why the logs need to be kept a secret from the camera owner. As long as any passwords and actual Wyze URLs are sanitized, I can’t imagine that there’s any other activity data that would be sensitive. But I guess that’s what I get for buying into a closed system.

Thanks again to everybody for advice and opinions. It’s been invaluable, especially in the total lack of communications from Wyze support.


1 Like

I was having so many problems with 1 of my 2 V3 cameras. Mostly stuck on step 3/3. Most of my issues have been resolved by performing a “Sync time” in advanced options, and then rebooting. It works for about 2 days and then needs another sync time/reboot.

I still can’t get Person Detection to work, but at least video is running smooth now.

1 Like