Connection failed retry since v3.2.0 (580), ETC, ETC

EDIT: forgot to say that clicking on the microSD to see more playback gets you no response about half the time so that you have to re-start the app or at least re-start the camera :frowning:
This is an overnight event:
I don’t know what the version # was before it went to v3.2.0 (580) but since the other morning Events clip playback have been saying CONNECTION FAILED RETRY over and over again with different event clips. Absolutely nothing has changed on my end, I have made no changes to anything. All other wifi devices in our home are behaving the same. I just woke up and POOF the Events playbacks have stopped connecting. The only thing that’s different is this pos new version doing things completely different such as removing the delete button from below the Events playback screen and putting it in a 3-dot menu which disappears and adds 2-3 extra steps to navigation IF it connects and plays in the first place.
Also, the app freezes up and closes without warning. The only thing I’ve found that seems to settle it down is to close it myself and re-open it, AND/OR go to the App Settings and clear the cache file size.
If wyze isn’t going to do anything about this, I guess I’ll have no choice but to go back to 2.50.9.512
In my opinion, wyze has bloated up the app to the point that it just can’t keep up with someone speeding through with clicks, which is what I have to do to get through so many clips to see what’s going on on this property.
Thank you for any help.

Wyze fix of last resort - reboot everything; router, phone, cam

HA! I re-booted, optimized, cleaned memory, wiped cache, deleted cache, uninstalled, factory reset my phone, re-loaded the phone, re-installed wyze, etc, etc, etc…still garbage. It’s this pos version. It was at least useable before the other morning :frowning:
But thanks for replying :+1:

I know why Wyze is in this fix - they don’t do regression tests. Let’s say they are fixing bugs A, B and C. They do those fixes well. They ask the developers to test fixes A, B and C. The fixes work. They start beta testing. The beta testers run extensive tests on fixes A, B and C. Everything’s working AOK. They release fixes A, B and C.

Then comes your post: they found new bugs AB and BC, that the devs erroneously created while working on fixes A, B and C.

In some dev shops, they even have another step before regression tests; code reviews! It catches edge cases easily.

2 Likes

That is a masterful statement and it makes sense to even a novice like me. I mean it :+1: