Wyze app 3.2.5 - Released 11/14/2024

Hey no cutting, the line forms way back there.


:telescope: :wink:

2 Likes

Not a peep out of them yet? Seriously!?

1 Like

What’s the rush? They got their new task robot to fetch coffee without spilling this morning. This stuff :bucket: :bucket: by comparison. :grin:

2 Likes

Someone mentioned they are having issues with the cat rectal thermometers working on 5G.:cat2: :thermometer:
:smile:

1 Like

Is that the latest Wyze gear? :rofl:

2 Likes

The update is not good at all the app freezes all the time and that has never happened before in 4 yrs.

1 Like

Has Wyze acknowledged there is an issue with this update?

I thought we would have heard something by now, since the blunder happened on Friday.

I’ve been watching like a hawk. What bothers me is it is still on Google Play!!

1 Like

That is sad. Do they even know we have an issue?

Guess I will have another Margarita :tropical_drink: and check tomorrow. :worried:

Still nonfunctional for me while in network on iOS 18 as of today, older iOS versions continue to work fine in network. :rage:

I haven’t seen them acknowledge anything. They are even more inept than I thought if they don’t know about it. I’m assuming they use their own products?

1 Like

They know about the issues and will post a fix.

As usual, the response in the forum will likely be an app update thread about a hotfix. I don’t think they usually foreshadow or give ETA’s about imminent hotfixes, they just launch them as soon as they’re ready, as is pretty normal for a lot of companies when they have bugs. I’d say public announcements about each bug are rare in the industry, but they do happen, especially if said bug is very high-severity and high publicity. Otherwise they usually just push a fix without a PR statement.

I do know they are aware and working on this though.

To be honest, the only reason I even know about the advanced settings bugs is because I read almost every forum comment and saw it in here. I don’t check my advanced settings every day, and especially since this issue doesn’t prevent my cameras from working in any way that I’ve noticed, it would’ve gone completely under my radar for possibly months except that someone else asked about it and prompted me to check. I don’t often change my Advanced settings after I first set them up unless I’m trying to verify something to help someone else out. Additionally, this is Android only, so anyone with iOS probably wouldn’t know about it either.

But to answer the question, yes, they do use their own products. I don’t know who uses which phone OS or how often they change their advanced settings like me, but they have certainly gotten support tickets about this, and I made sure they are aware anyway, along with all the reported issues listed in here for each camera model.

The response will likely just be an app update as is a fairly standard response in the industry for bugs. But who knows, I can’t speak for them, they might have someone say something once they have an ETA. It’s really only been 1 business day so far, so I am not too worried at this point since the cameras are mostly working and retained the settings functionality they had before the update…the GUI just isn’t reflecting them right. It’s definitely an IMPORTANT issue still. I would be surprised if it’s not resolved this week. My main curiosity is which Google Play release method they will choose…Will they announce the hotfix immediately and have us wait for Google’s Approval, or will they do the staged release so they wait for Google to release it first before they announce it. :thinking: The answer to that questioncan make up to a 7 days difference of when we hear about it.

You’re way to accepting of their poor service in my opinion.

1 Like

Possible. Though, I have seen a ton of similar and worse things throughout my time as a professional QA tester in the past, so maybe I’m just used to being less panicked and catrophizing about such things since I’ve seen this kind of thing so much in that career. It does not feel like a super urgent high critical issue to me as I have seen many of those too.

I’m by no means saying that this is a ā€œgoodā€ situation, and I think they made a mistake not doing a Release Candidate between the Beta and the production app. If they had, a lot of this would likely have been caught. There were certainly mistakes.

But even if I did think it was critical and urgent, in my experience doing QA testing, a lot of companies don’t make PR announcements about bugs like this unless it’s severe enough to make it into tech blogs and newspapers, which is unlikely in this case. Otherwise they will probably do what most companies I worked with do when such things come up: Make the fix and release it. That’s the typical response in the industry. I rarely saw many clients consistently do something different, so I don’t really expect Wyze would do something significantly different. I’m just basing my acceptance level on my professional experience and what are standard responses in similar situations. I don’t see something far out of the ordinary here and don’t feel entitled to something abnormal.

I think the BCPro streaming issues are another thing though. That one, while not affecting everyone (I don’t know why all mine are working fine), is extremely important/urgent for the people it is affecting and needs to be figured out. Several of us have been trying different variables to see if we can narrow down what the difference is between those having the issue vs those who don’t.

For anyone who does have that, Spamoni has been collecting logs to pass on to a dev investigating the issue, so if you submit a log for it, please tag spamoni so he can make sure to get that to the right people working on resolving it.

But yes, it is quite possible that my professional experience has my tolerance level a little higher than some others.

My experience in business has been silence is never good dealing with customer problems. I hear and see your points, but just because it’s done a certain way doesn’t make it good or the best way to handle it.

1 Like

Those are fair points, particularly when Wyze wants to be known for ā€œbeing friends with usersā€ and transparency, etc.

For a while they kept up on a list of known bugs, etc on their website, but once upon a time Wyze seemed to have as many as 5 community managers (someone doing Discord, someone on the forums, someone on Facebook, someone covering Reddit, someone covering Twitter, Instagram and the rest)…then they downsized to just Gwen and Jason and then since Gwendolyn left, Jason hasn’t had time to keep up on everything he used to because he’s doing all the work it used to take 3-5 people to do and now all by himself (this should probably change soon since Jason said they’re hiring more help for him again this winter). So I expect they will go back to doing better with this when the workload is spread out a little better again.

But in the meantime the OFFICIAL way to get a response is to contact support. Not unreasonable, but also not ideal. Like you indicated, choosing transparency would be better especially when you choose certain values for yourself as a company. I’m hoping things get back to better communication and organization on those type of things once they hire some more community managers to help again.

:+1:

Agreed and remaining hopeful. Take care.

1 Like

At Wyze Labs, no one looks up til the metrics bell rings.

That’s how they get so much done.

1 Like

Right there with you. V3 several SD cards new and old but it says it’s not there.

@WyzeJasonJ , after the said update my app is acting up. Some of the settings under advanced aren’t saving after exiting and I’m not getting push notifications on my phone anymore.

1 Like