Agreed. I hate to see updates come out as I know there’s a chance it screws up more than it fixes. As a paying customer it is very frustrating. They can’t keep this level of incompetence up or it’ll will be lights out. I will leave if this continues.
Absolutely pathetic. 3.2.5 has broken more than it fixed for Android. Record to sdcard will not stay toggled on. Other features with toggles also will not stay on. Whether making the changes in group favorites or individual under devices, the changes will not save. Only 4 cameras retained their settings,
all others changed and cannot be corrected back. I am convinced Wyze is on a path of self-destruction. Every time I go back into the app I discover another failure. The decision to request return authorizations for the 2 duos I have is being made easier by the minute.
At this point, it’s prudent to rollback whatever changes 3.2.5 made and start over. Trying to fix all the new 3.2.5 bugs just isn’t worth it.
I genuinely appreciate the sharing of problem reports and updates in topics like this, because I think it has the potential to help other users, and it also reaffirms my decision to do this months ago:
Lol. Very Wyze choice.
Seriously. I un-checked Enable auto update in Google Play Store and disabled Automatic Update for devices in the Wyze app where that’s an option several months ago, after they pushed out the Video Doorbell v2 update that wrecked notifications. (I happened to be away from home when that one was released; otherwise, I probably would’ve updated that right away…but then the reports of problems started appearing. )
Now I get notifications from the Forum and from Discord whenever app and firmware update messages are posted, so I monitor those for at least a few days (usually at least a week, if not longer) before making a decision about applying the update for my own gear. I think it’s saved me some headaches, but I still get frustrated when I read about people having problems, and I’m thankful that y’all take the time to post.
Bummer. Got to the party late.
3.2.5 (591) broke.
Luckily I still have 2.5.x on my old tablet.
Disabled auto update on my primary phone.
I get it. 100% smart move sadly. I’m just an early adopter. Always have been. I live for updates, unfortunately in this case Wyze is a huge gamble every time.
Well, it helps if you have 2 phones and update only one
I get that, too, and I don’t fault anyone for that. I’m glad we have β testers and those who want bleeding-edge features. I’ve said repeatedly on the Forum that I value stability, though. I don’t mind waiting to play with the new stuff if I know that many of the s have been worked out first.
I guess they need a Quality Control member to keep this from getting to us Γ users.
And that’s the problem really, because beta testers mainly check the bugs being fixed. The old working code that’s broken in the process is never tested. Wyze has been doing this for a long time.
Yeah, I absolutely feel the frustration. Fixing one thing (or adding a new feature) shouldn’t break something else, and this seems like a far-too-frequent occurrence with Wyze, which is why I’ve become so cautious about their updates.
Heh: γ.
I think they call that regression testing? Must be a foreign concept.
Luckily it’s early in the morning.
I don’t get pushing this update on a Friday either. It wasn’t critical. It really makes me seriously question Wyze and their business decisions and viability moving forward.
The timing isn’t entirely their fault, though. This announcement posted on Thursday, but sometimes it takes several days before an app becomes available in Google Play Store, and that’s been discussed multiple times here on the Forum and the Discord server, as well.
Thanks. I sit corrected.
happens
Nah, it's all good. I just think the lower-case HTML entities are prettier:
Entity | Result |
---|---|
α |
α |
Α |
Α |
β |
β |
Β |
Β |
γ |
γ |
Γ |
Γ |
Could’ve sat on it until Monday though so it has a full week to hit and then fix or recall. Not 2 days until the weekend.