I own 8 Wyze cams, including two old v2s that still work OK, but my two v4s (non-pan models) stopped reliably saving events on 3/12/26. They aim outdoors through windows to cover yard areas, as do most of the older cams.
In both v4s, Detection settings mysteriously revert to 50/50 motion/sound. Restarting them or just toggling random things like Night vision restores my custom Detection settings (e.g. 35/20) but that hasn’t been a reliable fix. They’ll capture events for maybe 10 hours. day or night, then fail again….repeat above steps.
If anyone else has also had only their v4s stop capturing events, please comment. All firmware is showing as current, plus the app itself.
What happens if you try Reset Services ( Settings ➜ Reset) for the affected Cams? If you do that, then you’ll also want to re-check your settings within Event Recording and Customize Detections or Customize Recordings and re-select your preferences, as appropriate.
When you mention capturing events, are you referring to events-only microSD recording, continuous microSD recording with event tagging, subscription-based cloud events, or something else?
Events not being captured applies to both cloud videos and SD cards, i.e. nothing gets saved or alerted. I only use Event recording, not Continuous (except in rare situations).
I tried Reset Services and will follow up later, Noticed it keeps settings but does revert to Smart detection; I made sure All events were being detected (yes) when this first happened, so that doesn’t seem to be the issue.
I’ve been using Cam Unlimited for all 8 cams since January if that has any relevance, which you wouldn’t think would only be a v4 problem.
The only other thing that changed recently was running 7 of 8 cameras at once due to a water monitoring situation with sound events every 10 minutes or so. Usually, I only have 5 or 6 cameras actively ON. Wondering if the network behaves differently as events add up, but the v4s should at least be saving events to SD.
My reliable newer router (300+ mbps) doesn’t seem to be a suspect. No heavy bandwidth for other things in general. Trying to avoid introducing rabbit trail ideas in a forum like this.
Worth noting that if you have cam plus/unlimited, it does have more connectivity demands (especially if using any of the smart “AI” stuff) than not having a subscription. This would apply mostly to your upload speed on your internet (which for some can be relatively low) and also your wifi network.
But see how it behaves after resetting services, since it sounds like it was some sort of issue with the settings being out of synch.
True, though the sudden loss of just v4 Events on 3/12/26 after several months of reliability is the mystery. Maybe they’re doing something trickier behind the scenes that older models don’t need to?
I’ve been loyal to Wyze but don’t expect them to be the most reliable brand at their price. Will report back here later if these v4s keep working - or not.
Yeah, I don’t have a subscription but my v4 hasn’t ever done anything like that.
Probably not related but I did have a Panv3 that stopped tracking motion and logging events. Rebooting it in the app would make it work for a day or two, then it would stop again. Turned out to be as simple as a hard power cycle (left it unplugged for about 10 seconds). Completely fixed it.
If you haven’t tried that, maybe worth a shot? I do prefer to do the “eject sd card” first just to be safe, though just turning it “off” in the app should theoretically be the same.
Perhaps a minor power fluctuation impacted both cams and something is just “stuck”? Long shot, worth a try if you haven’t already.
Though maybe wait to see how it does after the “reset services” first just to know which thing fixed it (if either).
I did a plug/unplug reset yesterday with similar waiting, but it only fixed Events temporarily.
As for SD cards, several of my cams had recently (before this problem) had been showing “SD card recognized” (paraphrased) notices, even though I’d installed said cards much earlier. That’s happened more than once over a few days with the same cams with no physical removal or software ejects done. Not unique to v4s.
I was actually going to mention possible SD card issues once you had replied as to which one it was (cloud or SD). If it hits a spot where the card can’t write (or can’t keep up) it totally gives up on the card.
I don’t know how that impacts cloud events, in my case I actually had an OG that I was using temporarily with an SD card that had a bad spot in the middle somewhere. As long as I formatted it every day, it was fine, but if I forgot, it would stop recording and was a pain to get it to format or recognize the card again.
From what I recall it still logged events (but the non subscription still frame ones). Maybe having trouble writing to the card and trying to upload a video at the same time is too much?
Maybe try swapping cards around between a problematic cam and one that is working ok to see if the issue persists (and/or follows the card)?
Any SD related cause of this is unknown, but it’s saving Events again for much longer after I did Reset Services, so I’m calling it fixed for now,
Main point of question was to see if others had a date-related (3/12/26) Event-capture failure with v4 cams only. Can’t tell it was related to my cam versions or just an unknowable coincidence.
Good to know, and thanks for taking the time to post an update. That Reset Services feature is goofy, and to me it seems like that and the Sync Time feature should be unnecessary (i.e., I’d expect the Cam to be able to periodically initiate these checks automatically), but it’s a simple thing to tap and to see if that resolves issues, and it often seems to for some things.
I also don’t know if any use of microSD recording would be related to this, and I agree with your previous comment about trying to avoid “rabbit trail ideas”. When I asked about that versus cloud event recordings earlier, that was mostly to get a better understanding of what you meant about “saving events” in order to narrow the focus. If you’re using both a subscription and microSD recording, though, then that may not have been super helpful—and I hope you don’t feel like it took the discussion in an unnecessary direction—but I guess it did tell us that what you experienced wasn’t affecting only one thing or the other with your all-of-the-above approach.
I’m glad things seem to be working as expected now.
I don’t know that a clear explanation of what “reset services” does has ever been determined. I have no subscription and on at least a couple of occasions it seemed to help with some glitches (of course I tried various things each time so can’t say for sure).
Though I don’t think I’ve seen it have anything to do with the SD card, I’m guessing that when you have a subscription, “events” affect the cloud and SD card in a pretty similar way, so at least as far as saving events to the card (or maybe even just tagging them), I can see it affecting that.
Curious if @ajwz1 noticed whether the card was saving recordings (green bars) just not tagging them as events?
That’s part of what makes it so goofy, IMO, because the in-app description provided with the control (tapping next to the feature label) seems to imply that it applies only if a subscribed plan is attached to the Cam; however, user reports here in the Forum seem to indicate that trying a Reset can help with some issues even when no subscription is in place.
There was that thing a couple of years ago in a Fix-It Friday that involved microSD card playback, and Reset Services seemed to be part of the remediation for getting at least some of those Cams working properly again. That’s one situation that comes to mind.
That’s part of what I was trying to pin down in the second question of my initial post.
It would seem to make sense that since the “event”, even when you’re not subscribed, is processed in the cloud and the still frame is stored there, so I suspect it does more than the app implies.
We may never know. Kinda like “reboot your modem”. Sometimes it does actually work, might as well try it.
The only thing I tend to forget is that you have to go fix your detection/notification types after. I have two OGs that I don’t want motion notifications on but I do want smoke/CO, and that requires leaving notifications on and unchecking the motion types. So if I reset I have to remember to uncheck those (usually the first notification is what reminds me). In reality smoke/co should always notify if enabled, otherwise they’re pointless, but I can see why turning off notifications would turn those off too. Main issue is you can no longer use an automation to turn notifications on/off if you want alarms to work. Unrelated tangent I guess.
But I think you always include that disclaimer when suggesting it, and sometimes I remember to mention it too…..
I try when I even remember to suggest Reset. Sometimes I don’t even think to suggest that because it’s one of those things that I still think should be more or less automatic and not require a user to tap a button, so it just slips my mind to even consider it.
We know when the cams reboot (even soft) they have to synch to NTP or they’ll be back to the default date.
Mine reboot every Sunday morning so in theory they synched like 1.5 days ago. No way my eyes are good enough to see if 4 cam times are in synch when viewing a cam group, but I know when looking for an event on multiple cams I’ve noticed they are sometimes off by a couple seconds. So no idea if it ever synchs to NTP proactively without a reboot or not. The small difference I’ve seen could even be just due to delays between reading NTP and setting the clock when it reboots.
Guess I could compare each to my laptop’s time and see any difference, but I’m not that concerned by it.
Luckily any “creep” there may be isn’t bad enough that its ever been an issue for me.
I have a Stratum 1 NTP server in the box that was a spare from work. I don’t think my accuracy needs are anywhere near the need to mount GPS antennas around my house though.
When it stopped grabbing events, it wasn’t saving a trace of anything to the microSD card or the cloud.
How SD files may interact with cloud videos is a question for engineers. I’ve assumed they were independent for redundancy, i.e. the cloud lets you retrieve at least truncated videos if SD ever fails. When both fail, it’s too bad!
I usually avoid continuous SD recording, since it inevitably wears out cards faster and their status can get hard to keep track of, plus it’s one more thing that could cause other glitches.
The recordings are separate, but what triggers them as well as the “tag” that gets put on both is the same.
It can be very hard to tell when there are untagged recordings on the SD card, they’ll just be a tiny green spot on the timeline.
I actually use continuous recording on most of my cams as I want it to be foolproof and not be missing anything. Even if I was subscribed, I’d want it to be there as a backup in case motion detection missed something or there was an internet issue etc.
Endurance rated cards can handle it, my Samsung Pro Endurance 128GB have been going continuous for about 2.5 years now, and running the calculations it came out to about 16 years before their writes would be exhausted. If I get the 5 year warranty period out of them, I’ll be happy.
It’s also helpful in cases where the cloud event that a subscription provides doesn’t include as much pre-roll as I want or the recording ends before the object of interest has left the FOV (the object has slowed its movement or is partially obscured, like by a tree or something, but is still in the picture). That allows me to get a better overall picture of an event with more context, so I also like the continuous microSD recording option.
