I don’t think a BBB complaint is warranted or useful. It’s a bug. It will either get fixed or not, but either way it doesn’t make the v2 cam unusable - it’s just annoying.
Wyze is free to obsolete old products and drop support for them at any time, even if it makes the product unusable, as many other companies in this industry have already done (including Wyze). It may piss off customers, but there is no legal recourse. If too many people make too many complaints about an older product that hasn’t been sold for a few years, Wyze is very likely to drop support and write it off. They feel no long-term obligation to customers.
I moved one of my Cam Plus licenses to a Pan Cam and viola, works fine now. If their support would have been better through this, I would not hesitate at this point to by an unlimited 1 yr. Cam Plus and still might. It seems anyway, everyone is going to need Cam Plus at some point. Heck, my new Cam Pan V3 serves me no purpose without the license.
Personally, I am going to start looking into other cameras since it seems to be time to pay $1`00+/yr. for cloud services. I did really like Wyze for years through and realize they too need to make money. If only their support were better, sigh.
Next time it starts happening again, I’ll try turning off Person detection to see if that makes any difference before I do the power-cycle Reset. But I don’t think so - I think Person labeling happens entirely on the Wyze server now after the event video clip is uploaded.
I saw more 30011 errors this morning then I have seen in a while. On 3 different v2’s and on 2 Cam Pan’s.
From the looks of the forum many others are seeing them too…
Well, I found a fix a fix, at least for my cams. I have done this with 2 Cam Pan v1’s and tested 2 days in a row.
I have 1 Cam Plus license and all other cams are Cam Plus Lite. If I move the Cam Plus license to a cam that is getting the 3001 error then force an event, everything works as it should. I then put the Cam Plus license back where it was and put the Lite license back on the Cam Pan and it continues to work as it should with a 12 second clip. I did this again on my other Cam Pan and it is now working as expected too.
I have not tried this on my V2’s yet but suspect it will also fix them. I can’t explain why it works but suspect something to do with storage at AWS.
So, although when we get good ol’ reliable 3001 error we are unable to watch the entire video from The Cloud, I can watch it on Playback BUT the playback feature is only available to me. Those who I have shared the camera with do not have access to playback. What this means is if I’m not home and let’s say my wife gets an event that ends in a 3001, what good is the camera to her?
I’m not expecting these cameras to be the end-all-be-all of security cameras but they should at least do what they are supposed to do OR at the very least allow everyone I share the camera to have the ability to access the video on the SD Card.
Wyze is just hurting themselves. I keep getting spammed by them for lack of a better word to by other products. There’s NO CHANCE I will buy anything else from them after seeing how them have reacted to the 3001 issue. Nothing to make me think any other items from Wyze would preform any better then the cameras. Or that they would be capable of taking care of issues with them.
I don’t think they even know what kind of company they want to be any longer. They are kind of the like the Temu of tech lol. Well, not that bad but you get what I mean.
As far as their other products, I have the scale which I do like, outdoor cams which suck and the worst purchase from Wyze yet was a touch free thermometer thing that is always 3+ degrees off. I thought I was sick for months when they started selling it during coronavirus.
I’ve been having the Error 3001 on my Cam v2’s since late 2022; the error has seemingly been fixed on my Cam v3’s since the last firmware. At some point I submitted logs and contacted support. After a LOT of back and forth, Wyze support ultimate suggested removing Cam Lite from my account (because it cannot be removed from a camera once added). It does seem like it can be re-added to my account, but I didn’t want to risk it.
I did have an old Cam v2 that I’d left at a family’s house and recovered recently to my own home. It is still on firmware 4.9.8.1002, and it has been ROCK SOLID. You know where this one’s going now…
I’ve now gone and downloaded 4.9.8.1002 (here) and gone through the process of downgrading the firmware (here), and then ran through the steps to set up a new camera, and so far so good.
I’ll update this post if it doesn’t fix it. But if this post is still here without saying it has failed, you know how long it’s been working for me.
EDIT: As of 2023-05-30, still no error 3001, so it seems this has fixed it.
The problem is getting worse. Up until now, unplugging and replugging the Cam v2 fixed the Error 3001 for several days. Now it’s coming back right away.
Clearly Wyze knows what’s wrong by now, but no firmware update. Apparently they see it as a good thing if it forces owners of v2 cams to discard their older gear.
Suggesting to turn off Cam Plus Lite for the account would not seem to be a solution. Obviously there’s no error 3001 if there’s no 12-sec event clip upload to the cloud, but how is discarding the whole important feature a solution?
Yeah it reflects poorly on Wyze that Wyze’s firmware update broke our old v2 cameras, but there’s a solution and it costs you nothing but 5 minutes of your time. It’s actually really good Wyze gives us access to old firmware and a method to downgrade. Many companies wouldn’t.
“*[4.9.9.1433] (September 27, 2022)
Due to the security improvement on this firmware, you will need to go through the setup process for your camera if you go back to firmware 4.9.8.1002 or below. Because of this, we are removing those firmware files from this page.”
Some try to say 3001 is an issue with certain cameras. And there has been comments saying it’s a problem with the users’ network. No truth to either. I see 3001 on all the different models of Wyze cameras. And to even hint it might be someones network is just plain stupid. This problem belongs to Wyze. It’s on their end. Their lack of interest in this shows how little they think of users after they have your money.
I have the 3001 on my Cam Pan V1’s and Cam V2’s but my outdoor and v3’s are all fine. If I put cam+ on any of the cam’s with the 3001 error it goes away in my case. Put it back on Cam Lite and it is fine for a few days then comes back. My theory is they save the videos in different locations Cam+ vs. Lite or perhaps with some sort of differing QoS but also firmware dependent affecting only certain models.
It is 100% not LAN/WiFi related.
In my case, Wyze ended up giving me $20 gift card to get me to quit complaining. Ended up getting a Cam Pan 3 but of course had to get Cam+ for any real functionality but they gave me a card for a broken Wyze outdoor cam as well so I paid like $15 in the end.
I have begun to replace my Wyze cams with Reolink Duo 2’s outside due to Wyze support. It is a shame they break then won’t fix cams that I just bought 2-4 years ago to force Cam+. If the cams actually fail and I have to buy new ones that require licensing, so be it, just like my Blink XT2’s grandfathered into free cloud. If they fail and I go with Blink outdoor then it is over to a subscription model loosing free cloud but at least they don’t break the cams firmware, then refuse to fix it.
I get 3 types of events for my Wyze cam v2 at the front door:
Motion detected, generates a notification, a 12-sec event clip uploaded to the cloud, and local microSD card recording
Person detected, same except event labeled and reported as Person
Automation event, where my Ring doorbell PIR motion detector triggers a Wyze event clip recording to the cloud via IFTTT, but there is no local microSD card recording
Event type 1 (motion) seems to be the only one that constantly reports Error 3001 - the other two types don’t (Person and Automation).
I could see maybe the lack of local microSD recording for the Automation event somehow making a difference in the processor workload or timing, but that wouldn’t explain how Person labeling makes a difference since that happens in post-processing in the cloud. My only guess is that motion events that have an Error 3001 don’t make it through Person detection post-processing, and therefore never get labeled as Person.
