@carverofchoice was there any feedback from the “fix it Friday” discussions?
Any news on when the fix from cam v3 will be rolled out onto other cams?
Knock on wood but I’ve stopped getting this error code for some reason on my V2s, V2 pan and my V3s. My doorbell cams are working as well. I haven’t changed anything or subscribed to CamPlus. It just playing events again for both Android and iOS. I have no idea why but I hope there are no changes coming!
Seems to have slowed down a little. I only had a couple 3001 errors today. But it’s not any particular camera type. I get them randomly on V2’s and Cam Pan’s. I don’t have ant V3’s. And don’t plan on buying any till Wyze takes care of this issue. That I think has been going on for a full year.
2 Likes
Substantially better for me in the last week.
You have to make up your mind, better or worse 
1 Like
I’ve been sitting perfectly still for seven days, so it must be the system that fluctuates. 
Incidentally, this also improved:
…returning to near normal in the last few days. 
OK Carver,
I was trying to reply to your Fix it Friday post from 4-7-23 about err 3001 to keep it in the proper thread post(s) but as with many other wyze products I have, even this forum don’t work properly so I’m posting here. In rebuttal to one user saying that he has sent 10 log dumps to wyze with no avail, you said that they wont even look at them until a call is made to support to open a “ticket” on those logs and my reply to that is if I have to call support for everything that used to work fine and now dosen’t because of a firmware update breaking something else then I’m sorry to say that there is not enough time in the day or days in the year for ME to report on everything that an update breaks or fixes. After all , is that not what the BETA testers in the “BETA Program” are supposed to be doing ?
I mean come on man, the last time i needed to call support to stop being billed for something I didn’t order I lost the better part of 2 hours of my day.
During the pandemic and some time beyond that I had all the time in the world to be a beta tester but that program was always full and I believe still is. So with that being said I believe that if your going to include an option to submit logs from every device they make and I would argue that these logs should contain “All” relevant version info to said device and app versions etc. , then why must they insist that the end user take the time out of there lives to call and report the issue to a human that may or may not even have a clue as to whats going on with the problem.
That seems to me to be a big stretch to imply that it is necessary to reach out to a company and alert them to issues that occur as a result of a required "Firmware / Security Update and or Bug fix.
Now that I got that all out, I totally understand that from the “Forum readers and Posters” perspective , that info is absolutely needed if anyone is going to give advice on troubleshooting within this forum.
So long story short here is I used to only have that 3001 err on one V2 cam and it was very intermittent, I now see that err (and other new ones) on EVERY cam I have (1- V2 / 8-V3s / 2- PanV1s / 2 PanV2s / 2 PanV3s / 1 OD camV2 and 1 Doorbell Pro ) by my estimates that’s about 20+ hours on the phone to support for this one issue.
So with all that unloaded I think you can see why so many users posting here are rather frustrated with Wyze right now. I love the cams and the prices especially but rather than getting better I think they are biting off a bitter pill to keep releasing more new products when there are ongoing issues with their staple brand cams etc. If anymore firmware updates break anymore unbroken features in my cams , I am just going to stop updating them altogether and if necessary Ill keep the working app version on an old phone and that will be my last Wyze recommendation or product purchase. There are far too many other competitors is the home automation market for Wyze to be “Not So Wise” with customer service and support .
Thanks and Good Day Sir
Respectfully
Terry W.
1 Like
Hi Terry,
I hear your frustration. To clarify, sending in a log doesn’t necessarily mean that nobody will look at them unless you call support, but it does mean there will be no “response/answer” without going through a support ticket. It is also most effective when a log is specifically passed on to someone on the right team to look through with a support ticket, though they can get passed on in other ways too. I get people’s logs for different bugs passed on to the devs/teams from here all the time. The important thing is to understand that a log is NOT the same thing as a support ticket and there is no response to log. A lot of people believe that submitting a log is the SAME THING as submitting a support ticket, and I try to help make it clear that they are 2 entirely different processes. Currenlty, only the devs have access to see support logs, and while they do use them to look into things, they will not be responding to people through a log. It is a one-way transfer about what happened with the device recently. The reason I make an effort to clarify this for people is that many wonder why they aren’t getting a response from their logs, but they don’t work that way. Responses only happen through Support Tickets (which can reference a log and ensure the right team is definitely checking it out). When I submit a log I personally make sure it is always passed on specifically in one way or another to make sure it reaches the right team, just to make sure the right people see it and that it is definitely being taken serious. I suppose it’s fine if others don’t want to do that as long as they realize 1) a log is not a support ticket, 2) there will not be a response to the log.
I also understand not wanting to spend a lot of time on a support call. For that reason, when I do contact support, 90% of the time I choose the email option. I simply type out a quick message of what it’s about and then I can deal with the situation on my own time when it is convenient for me. I always suggest this option unless it is something critical or someone needs immediate help and a walkthrough with immediate feedback on something. But like I said, 90% of the time I recommend email. It’s convenient and the best use of my time IMO when I don’t need an urgent immediate response.
For what it’s worth, this issue did make it into the Fix-it-Friday reports so it is being actively addressed for everyone:
Anyway, even though this issue isn’t affecting any of my 40+ cameras (I have every camera model but the WCO v2), I still did what I could to bring attention to this and get it added into Fix-it-Friday for the rest of you who are being affected so we can get weekly updates on the progression and action plan now. 
That is a good step in the right direction.
5 Likes
I have had the error message on all my cameras of 3001 and have reported it so many times. No response from Wyze. This is ridiculous. If I needed a video for proof I have nothing. It blips out everytime on most of them and sometimes on the others. Wth? Can you help us out? Yes I’ve rebooted, yes I’ve updated, yes I’ve uninstalled and reinstalled. I’ve also rebooted all my cameras, rebooted my phone,. These were great cameras.
1 Like
Further up the thread it’s mentioned the fix needs a firmware update which had been delivered in v3 but is not yet released on the other models.
I don’t really understand how this can be firmware related because if you download the video it will play without the error code in an external video player.
To me it seems that the cloud solution/integration in the app is just poor.
Even without this error my cloud videos take minutes to load before I can view them. When I download the video it is 3 or 4Mb in size so should take milliseconds to view in the app.
The “Year of the camera” hasn’t got off to a great start.
First time on forum. I too have been having on and off problems with motion events from the cloud. I have a Moto G6 without sim that I use for the Wyze app and an Iphone Xr with the wyze app as well as an iphone7 without a sim that I use for the Wyze app (Second home). I get an error 3001 on the moto every time the Iphone Xr “hangs up” loading a cloud event. The iphone7 never hangs up or indicates and error-works everytime. Wyze app 2.41.5 (5) on both. Don’t know if this helps any.
1 Like
Maybe they use more then one server for their cloud. I still see 3001 on all cameras. I don’t think I’ve had a day go by without seeing at least one. I reset my cameras often. I feel like that helps. But I’m not sure. I guess what bothers me the most is Wyze trying to see new items thru all this. Unwanted beeps on my phone telling me it’s my last chance to but something else from them. Or begging me to get Cam Plus. I will probably never buy from Wyze again. This has NOTHING to do with any users’ network. As some loyal followers of Wyze will try to tell you. The 3001 issue totally belongs to Wyze. And is on their end. Not out here in user land.
1 Like
To be clearer about what I meant. The same motion event will work perfectly on the Iphone7, “hang up” on the Iphone Xr and show an error 3001 on the Android phone (Moto).
That is really interesting! Thank you for sharing. Weird that it reacts a little differently on different models of phone, not even just different OS’s.
The difference between android & iPhone was already suggested further up the post which is another reason why I can’t believe this issue is solely related to the firmware of the camera.
@carverofchoice can you ask someone from Wzye to provide a explanation of this problem & the fix they are rolling out and when?
I do know they have been looking into it and made some good progress on some devices and for a lot of people, but I have not heard a lot more than that. I know it’s not anywhere near resolved for everyone yet, so I will push this again a lot harder in about 2 weeks when they are looking for more items to give priority to. Hopefully we can get this added onto that list with more explanations and ETAs, etc.
1 Like
BTW, for everyone looking in this error thread and wondering about whether logs are useful, I asked directly in the most recent AMA about whether it is necessary to tell someone (support or an employee in here) about the submitted logs, and this was the response:
So if you are having an issue, and submitting logs, make sure to coordinate that through support or another employee in some way or apparently, it is likely to go into a “blackhole that is the log backend,” since there are millions of logs in there.
Also, if one of the forum volunteers ask you for a log, they are specifically passing it on to employee too, so those logs also get looked at. Basically don’t just submit a log and do nothing else. Make sure to tell someone in one way or another so it can specifically get passed on.
Right, that’s a joke!
They read these forums, hear our complaints after going through all the hoops and BS we’re all still exactly where we were months ago!
I agree! I can’t remember the last time I checked events and didn’t see 3001. This has been going on for some time. Wyze either does not care about it. Or are not capable of fixing the problem. Either wat it shows what kind of company we have wasted our money with. And still they continue to come out with more products. And keep pushing Cam Plus.
1 Like
Update related to Error 3001 that will apply to some people:
1 Like