So I have had a Wize Cam OG and about a month or two ago it started to reboot itself when motion was detected. I have a memory card in the camera and 24/7 recording turned on. When motion is detected a starts to upload video to the cloud about 5 seconds into the uploading to the cloud it reboots itself. Not sure if it is some bug in the firmware or what the deal is. As long as no events are triggered I don’t think it ever reboots.
I thought maybe a bad USB adapter and bad power so I replaced that but didn’t change. I just replaced the memory card and no change. Now I am going to turn off cloud recording on that camera to see if that stops the reboots.
Has anyone seen anything like this? It will record for hours and hours when motion isn’t detected but as soon as it is it starts rebooting itself.
Are you using the stock USB cable or something longer? It sounds like a power issue, so if you’ve tried different adapter and cable (and aren’t using a longer than stock USB cable) I’d exchange it as it sounds defective.
I’ll be interested to learn what happens when you do this:
The way you describe the problem also makes me wonder if what you’re seeing is related to or the same problem as that described in this topic:
In that issue—which seems to affect only Cam OGs attached to subscriptions—users who have microSD cards set for continuous recording see gaps in the recording timelines, and those can look like reboot events.
Could it be that all the others just haven’t noticed that the cam is rebooting? Seems unlikely but not something that has specifically been asked I don’t think. But I’m guessing this is totally separate, not sure what software or server side thing they could have done that would actually cause the cam to hard reboot. But never know.
I’m not sure of an easy way to tell without setting up some kind of monitor for individual Cam OGs, especially since logs aren’t easily accessible to the users and there’s no “uptime” feature on the Cams.
I’m interested in learning what happens if cloud events can be disabled entirely. I still think there’s a connection between those (subscription-based) and and these microSD recording gaps, at least in that other topic, and I think this one might be related, but I’m really just speculating and also eager to see an update from someone at Wyze about all this.
If that works I may just remove it from my Wyze subscription so that would give me notifications of events but no videos sent to the cloud. I think you just get an image or something like that and to see the event you have to go to the SD card.
Right now if the motion event is LONG as in 2 min of motion the camera keeps rebooting and i have a gap in the timeline of 2 min. The Interesting part of this is that I haven’t seen any gaps when motion wasn’t triggered. To be fair MOTION also means the camera is doing more video compression because things are changing in the frames so it is POSSIBLE that this is a problem and that this is causing the reboots. So I will know better in a few days.
Yes mine is rebooting. Because it drops off the network. And while this is happening I can’t connect to the camera for a while.
I made some changes to mine and it hasn’t done it since. But I have two theories.
First the things I changes is I removed the camera from my subscription and rebooted it. Then put it back into my subscription and i erased the detection zone and made a new one.
Since then (24 hours ago it has worked). BUT!!! No one has been lose to the camera in the last 24 hours NO LARGE events where signifant motion is in front of the camera.
I noticed previous it often lost recordings when BIG objects like cars pulled in close. IF this turns out to be THE THING. That may indicate that it is a problem with uploading larger files or data compression issues.
So I still have to wait to see if this is part of the issue.
OK that’s an interesting development then, the discussion to this point has been about the card having gaps, but making more sense if the gaps are caused by the cam crashing and rebooting.
Maybe they’ve changed something with the compression for cloud clips and the cam isn’t able to handle doing two different compression types (one for cloud, one for card). Just a random theory though. Hopefully they get to the bottom of it soon.
I have more examples of this happening today. I did have cloud detection turned off.
So one event or gap last night was around 5AM on my OG. My Aqara doorbell also has 24/7 recording and I can see at that time nothing happened. But at 9:30 AM today when my wife left the hours and drove the van directly under the camera that whole sequence is gapped out of the SD and no event was triggered for the cloud.
I am removing that camera again from my subscription to see if when she returns i just get a basic motion image but nothing. I need to do more testing but this is real garbage. I guess the OG is just not holding up.
Sounds like even though you removed cam plus, whatever glitch it is causing is still in the camera.
It’s possible that a true test may need the cam to first be removed from the subscription, then deleted from the app, factory reset, and added new (under a different name ideally, and without activating Cam Plus). That should prevent any previous settings from being added back to the cam.
Of course that’s a pain and may not be something you want to try.
This same symptom started for several people with several cams around the same time, and is only impacting people with both Cam Plus and SD Card recording. I highly doubt all these cams just decided to have a hardware limitation/issue at the same time.
I have it OFF again now… so lets give it 24 hours with cam plus off to see if i get any incidents with cam plus off.
I also saw with cam plus ON i was getting gaps when NO events was triggered… But it could be that the cam plus crashed it before the event even triggered.
For example when my wife drove UNDER the camera today leaving at 9:30 NO event was triggered on cam plus but a GAP in video. When she returned cam plus did trigger and stopped early and HUGE gap in video.
Cam plus is OFF and she left and I got a notification of a single frame showing the car and NO gap in the continue recording. But I want more data points before I say this is a fix.
OK I must have misunderstood your previous post/timeline.
If the cam is rebooting (as a number of people now have reported) then it would not surprise me if event logging is intermittent when the issue is happening. If it can’t upload to the cloud before it crashes, it won’t exist.
What you’re seeing now with cam plus off is exactly how all mine work (since I don’t have cam plus). But yes, agreed, let it run for a day or two to confirm.
I can actually semi-simulate cam plus by using the “upload a clip to the cloud” automation feature, maybe I’ll give that a try on one of mine, but it wouldn’t really be an apples to apples comparison, especially since there is no analysis or smart detection happening.
I have had MANY events now since the cam plus was turned off and it has worked no issues.
So initial assessment is that disabling cam plus on the OG will solve the problem of things lost in 24/7 recording. May also explain why others don’t have an issue because maybe they don’t use cam plus.
I just orderd a V4 to replace this unit because I don’t think this is something Wyze is going to fix.
I have 3 OG’s. Just got the 3rd newest one yesterday, and it is different from the other two which are from 2024. This new one has the SD card slot on the side of the camera, where the two older OG’s have it underneath next to setup.
On the 2 oldest, I’ve had the same gaps in continuous recording whenever motion is detected and sent to cloud. I haven’t noticed if its rebooting, but the cloud vids are random between showing actual recording time and 5 min(not actually recording 5 min). The new one set up today, appears to be working normally, and it has a different firmware version than the older two - 1.1.0.97 vs 1.0.98. No option to update the older ones so the newer must be a different model version. Can’t wait for Wyze updating the older firmware to make these work right again.
Yes the newer OGs are the “2025” edition but in reality it was likely just due to a lack of availability on parts or something forcing a design change.
All my OGs are the older version and without cam plus they don’t have any issues, and it also isn’t firmware related as the OGs haven’t had an update in a long time. Since this problem seems to have just started a week or so ago, hopefully they’ll get to the bottom of it. My guess is something new server-side is somehow overloading and crashing the cams when they’re attempting to do both things at once.
I like my v4 but I wouldn’t give up on the OG so quickly, this started recently, and there is no reason to believe they’re going to just ignore this issue affecting one of their best selling cams, especially when it affects paying subscribers.
The fact that it is not firmware related should mean once they find the issue they can get a fix out relatively quickly.
