StevenA,
Hopefully this will stay on the Fix-It Friday list, it is really an aggravation for me.
I may have 100 events in a day, and when you have to return to the list, then scroll down, it is a PAIN.
Please Wyze fix this problem with the Android App!
Please look into the video stuttering on Android playback with the V3 and V3Pro cameras.
I have Cam+ yearly subscription, and it happens on the current android client.
The videos play fine over webview, but stutter on my Pixel 6a with Android 13.
All cameras have current firmware, and the app is up-to-date. The V2 cameras do NOT stutter.
V3 Pros at 4.58.11.4679 V3s at 4.36.11.4679 Android app is at 2.44.5 (330)
Here is the ongoing thread on the subject:
Latest Android app update still shows CamPlus filters as unusable. @WyzeJasonJ
This issue appears to be fixed under the latest app for Android 2.45.0.342.
Great News, I checked it on my Android phone, and it is fixed!
If they could get the stuttering on playback for the V3 and V3 pro cameras fixed on Android 13 that would be awesome!
I am still on v3 firmware 4.36.10.4054 with no stutter. Maybe you can roll back to older firmware.
Good afternoon!
Thank you for your patience with us! We have our issue submissions for September and are happy to provide these updates to you.
Discord - When viewing an Event and then going back to the Events list, it brings you back to the top
This should be resolved in the 2.45 app update we released this week! Is this still impacting you? If so, please let us know! Otherwise, we’ll remove this from the update list next week.
Forum - ‘Content type is error’ message when trying to create Rules
May we please have app logs for this? We’d like to look into it. Here are the instructions:
Recreate the issue. Then in the Wyze app, go to Account > Wyze Support > Submit a Log. Select your device from the dropdown menu. Then fill in the description box with the date, time, and time zone of the most recent time you noticed this issue and a description of what’s happening. Make sure the Send Logs option is selected and then submit your log. When you have the log number, please post it here as a reply to me so I can get it to the right folks.
Reddit - Event playback in the app is stuttering
For this one, logs and screen recordings would be helpful. If you’re experiencing this, could you please provide that documentation? Here are the log instructions:
Recreate the issue. Then in the Wyze app, go to Account > Wyze Support > Submit a Log. Select your device from the dropdown menu. Then fill in the description box with the date, time, and time zone of the most recent time you noticed this issue and a description of what’s happening. Make sure the Send Logs option is selected and then submit your log. When you have the log number, please post it here as a reply to me so I can get it to the right folks.
Forum - Wyze Cam v3 Pro status light is not working properly, light will turn on when motion is detected but not recording and according to documentation it is only supposed to turn red when recording
We are running a fix for this through QA this week. We’ll let you know the outcome!
- Let’s Take a Look at Some Previous Submissions -
Core - Error 3001 is happening on cameras such as Wyze Cam v2
We have started a gradual release for Wyze Cam v2 and Wyze Cam Pan v1 firmware that fixes this problem! Please let us know if you continue to experience Error Code 3001 after updating to the 9.2351 firmware.
Core - Cameras appear offline in the app, though they are online and viewable *
We began a gradual release for firmware that helps with this! Please keep an eye out for firmware 4.36.11.5859. For those using the firmware already, has it helped?
Core - Playback stutters when selected for the first few seconds of Playback from the microSD card
The gradual release of firmware 4.36.11.5859 also should resolve this problem! Please let us know how it performs when you receive it.
Forum - Wyze Cam v3 microSD card Playback is skipping the first minute of every hour (excluding midnight)
This issue is also addressed in firmware 4.36.11.5859! For people with the update, is it doing well for you?
Discord - Camera time and notification time do not match
We believe we’ve identified the root cause of this. In the meantime, please try manually changing your cell phone’s time zone to a different one, leave it in the other time zone for 5 - 10 minutes, and then change it back. We’ve heard back from customers that this workaround has helped with this problem. If this hasn’t worked for you, please let us know!
Reddit - Wyze Cam Pan v3 does not return to set home position
We’re currently planning to release a firmware update that works on this issue to beta next week. We’ll keep you informed!
Facebook - Cam Plus subscribers unable to filter events
We’re working on changes to the app that will take place in an update after the upcoming 2.45 app release. That should help with this! In the meantime, we’ll continue to seek solutions for this problem.
Forum - Wyze Sprinkler Controller schedule skipping days
Looks like we still can’t reproduce this issue. But we’ll keep an eye out for other ideas and feedback for a while longer.
:cam_v3: Discord - Wyze Cam v3 does not stay connected to the Spotlight accessory :cam_v3:
We don’t have a further update for this one yet. We’ll let you know when a fix heads to QA! At this point, we’re still checking on the submitted logs.
Thanks for reading! Have a wonderful weekend.
Does that mean you consider this fixed? A few of us still have the problem.
Forum - Wyze Cam v2 Detection Zone reverted to a box instead of a grid
We put a fix for this on the cloud side! Is anyone still having trouble with this? If not, we’ll remove this from the update list next week.
[Mod Edit]: Linked referenced text.
Thanks again for fixing that Android App bug where the Event Viewer returned to the top of the list instead of where you left off. This was a big deal for me. If you have over a hundred events to look through, having to scroll to get back to the spot where you left off was really frustrating.
THANKS VERY MUCH!
Many V2 and PansV1 with same firmwares. Some of them have the small boxes and the others the big one.
Hello, everyone!
It’s another lovely Friday in September and we’re here with your next batch of Fix-It Friday updates! Here’s what we have for you:
Forum - ‘Content type is error’ message when trying to create Rules
May we please have app logs for this? We’d like to look into it. Here are the instructions:
Recreate the issue. Then in the Wyze app, go to Account > Wyze Support > Submit a Log. Select your device from the dropdown menu. Then fill in the description box with the date, time, and time zone of the most recent time you noticed this issue and a description of what’s happening. Make sure the Send Logs option is selected and then submit your log. When you have the log number, please post it here as a reply to me so I can get it to the right folks.
Reddit - Event playback in the app is stuttering
For this one, logs and screen recordings would be helpful. If you’re experiencing this, could you please provide that documentation? Here are the log instructions:
Recreate the issue. Then in the Wyze app, go to Account > Wyze Support > Submit a Log. Select your device from the dropdown menu. Then fill in the description box with the date, time, and time zone of the most recent time you noticed this issue and a description of what’s happening. Make sure the Send Logs option is selected and then submit your log. When you have the log number, please post it here as a reply to me so I can get it to the right folks.
Forum - Wyze Cam v3 Pro status light is not working properly, light will turn on when motion is detected but not recording and according to documentation it is only supposed to turn red when recording
The QA test for the fix is currently underway. We’ll keep you posted!
- Let’s Take a Look at Some Previous Submissions -
Reddit - Wyze Cam Pan v3 does not return to set home position
Well, we don’t really like saying this. But the firmware we were hoping to release does not meet our expectations, so this is on pause again. We’re discussing these issues and will provide an updated timeline later when we have more information. We appreciate your patience.
Core - Error 3001 is happening on cameras such as Wyze Cam v2
We have started a gradual release for Wyze Cam v2 and Wyze Cam Pan v1 firmware that fixes this problem! Please let us know if you continue to experience Error Code 3001 after updating to the 9.2351 firmware.
Core - Cameras appear offline in the app, though they are online and viewable
We began a gradual release for firmware that helps with this! Please keep an eye out for firmware 4.36.11.5859. For those using the firmware already, has it helped?
Core - Playback stutters when selected for the first few seconds of Playback from the microSD card
The gradual release of firmware 4.36.11.5859 also should resolve this problem! Please let us know how it performs when you receive it.
Forum - Wyze Cam v3 microSD card Playback is skipping the first minute of every hour (excluding midnight)
This issue is also addressed in firmware 4.36.11.5859! For people with the update, is it doing well for you?
Discord - Camera time and notification time do not match
We believe we’ve identified the root cause of this. In the meantime, please try manually changing your cell phone’s time zone to a different one, leave it in the other time zone for 5 - 10 minutes, and then change it back. We’ve heard back from customers that this workaround has helped with this problem. If this hasn’t worked for you, please let us know!
Facebook - Cam Plus subscribers unable to filter Events
We’re working on changes to the app that will take place in an update that is in the works. That should help with this! In the meantime, we’ll continue to seek solutions for this problem.
Forum - Wyze Sprinkler Controller schedule skipping days
Looks like we still can’t reproduce this issue. But we’ll keep an eye out for other ideas and feedback for a while longer.
Discord - Wyze Cam v3 does not stay connected to the Spotlight accessory
We don’t have a further update for this one yet. We’ll let you know when a fix heads to QA! At this point, we’re still checking on the submitted logs.
Thank you for your attention! We’ll be back next week for more Fix-It Friday.
Again, this is not fixed for me;
Forum - Wyze Cam v2 Detection Zone reverted to a box instead of a grid
Could someone just let us know if this can be fixed?
I’ve seen someone post that this issue is fixed if you set up you cameras using an Apple device. Could Wyze send me an iPad?
No iPad for you.
Seapup,
I saw your post in the Wyze News thread that this is broken again in Android App Version 2.45.5 (347).
Obviously someone had an older version checked out (withOUT the event viewing return fix), and made changes to it, then checked it back into “go live” without fully testing it.
I have no answers to your questions as I don’t work for Wyze and don’t have the ability to directly ask the dev or CM team questions. You are most likely correct though, someone probably checked in a patch to old code and checked it back in.
Too many factors to know for sure and I doubt Wyze will expose their internal IDE, version control and CM/QA choices, procedures and policies. I wouldn’t.
You are right, I just hate seeing the same bugs creeping back into production.
Good natured piling on allowed?
Is there a simple way to explain to a lay person why bug fixes and enhancements to the app and firmware often seem to eff up other stuff?
Imagine an app or firmware (like in a security camera) as a complex puzzle made up of many interconnected pieces. Each piece represents a different feature or function, like taking photos, recording video, or sending alerts.
Now, when the developers work on this puzzle, they’re often trying to make it better. They might fix a piece that was broken, like a piece that made the camera not work correctly sometimes. Or, they might add new pieces to make the puzzle more exciting, like a new feature that lets you zoom in on the camera feed.
The challenge is that making changes to one piece can sometimes accidentally affect other pieces nearby that used to be perfectly shaped, but now have to change to accommodate the new piece that is shaped differently. It’s a bit like if you were fixing one part of your bicycle, and suddenly, the wheel starts wobbling even though you didn’t touch it. It’s because everything in the puzzle is connected, and changes in one area can have unexpected consequences in another.
So, when developers release updates with bug fixes and enhancements, they’re doing their best to improve the overall experience. But because of all these interconnected pieces (some of which they can’t see or anticipate being affected), it’s possible that something might not work as expected when they change one thing to make another better. This is why you might notice that sometimes, after an update, a feature that used to work perfectly may not work as well as before.
That’s the end of the simple explanation to the lay person. Then there is the demand about testing EVERYTHING to make sure everything works perfectly with the updates. I’ve worked as a professional QA tester and I don’t care what anyone says, It’s impossible to test everything. I like to share this simple example:
Anyone with any professional programming or QA testing experience will explain that what is being sought here is absolutely guaranteed 100% utterly impossible for ANY company in our current situation with electronics and using programming to ever promise anyone.
Let me give you a quite simple example. In the following control flow example, this “simple” program consists of up to only FOUR decisions. Just 4 decisions and a loop (even with just 4 decision trees, it could’ve been made almost doubly more complicated if we expanded the decisions on the far right and each subsequent decision…but we’re keeping it as simple as possible). For this SUPER SIMPLE piece of programming/code, if you were to EXHAUSTIVELY test every possible combination of execution with a limit of only 20 cycles, then if it took the tester 5 minutes to execute each test sequence, then complete testing on this small piece of code with as few as 14 lines of code and 4 total decisions to make, it would take the testers ONE BILLION YEARS to finally test everything to be sure it was “fixed period and without exception and in all manner.” One billion years on even the absolute simplest code because even for something so simple it seems almost worthless, there are actually roughly 100 quadrillion sequences of just this stupid easy program.
If a person says, “yeah, but you can run most of the tests automatically and fast for each test case instead of a human testing each case.” Fair enough point in some cases (not always true, but we’ll pretend it is in this case). Let’s assume that each test now only takes FIVE MICRO SECONDS instead of 5 minutes. That’s a more than fair adjustment. That means complete testing on this small piece of code with as few as 14 lines of code and 4 total decisions to make, it would take automatic testing NINETEEN YEARS to finally test everything to be sure it was “fixed period and without exception and in all manner.”
Basically, if anyone is looking for a promise from Wyze (or ANY company that uses programming of any sort) that something is 100% fixed without bugs, etc…it’s NEVER, NEVER going to happen. They would have to be completely insane to ever promise anyone that. Research has proven this fairly conclusively, and that is just for the most simple of code…let alone all the other huge complexities of millions of lines of code and decisions and loops actually being used. Everything Wyze has is infinitely more complex than this smallest of tiny programs.
A promise of no bugs will never be forthcoming. It’s nearly impossible. Best we can do is get indications that most things work okay most of the time with few known critical errors reported with any frequency. It also means if a person wants more stability they should stick to production versions of firmware and software and stay away from beta like the plague. Beta is for helping to test and find the most common and critical bugs and problems which almost for sure, guaranteed, exist in some form…some of them we will find immediately, some of them might take billions of years of testing to discover, but statistically it is pretty guaranteed there are bugs.
If such guarantees are needed, then I would suggest giving away or selling all Wyze devices now because this promise is not only not EVER coming, it is absolutely impossible. Wyze can not possibly eliminate every single bug within our lifetimes. It would be hard enough if their code was only a few lines long and a single product. With everything they have and the amount of code they are using…impossible, utterly and completely impossible. It’s not their fault, it’s math. It’s normal.
This is a really good explanation. I’m currently working on a pretty complex system, mainly consisting of a web app, and it’s amazing how you can make the smallest little change, use it for weeks, and then find out it broke something else and no one has noticed or reported the issue because it’s so small and I would have never thought to test it.
The relationship of every line of code is so complex you can never keep track of it. Automated A/B testing is the ideal solution, but it can only test so many things, and you have to write those tests which can have bugs of their own.
In this specific case it sounds like a VCS (version control) error, as in the branch with this change was not up to date with the branch that includes the fix for the scrolling event. An issue like this should not happen, but it sounds like this update was rushed to get some security patch out because I don’t know why else they would release an entire update for that one little FAQ change. But that’s just speculation