Well, it’s very promising so far. Both cameras load good video now. And one of them which couldn’t load live video, was recording a weird disco party with psychedelic colors. but it’s normal now with 4.36.0.228.
Hmm, I just checked my account/firmware and that version is not available. Are you guys all members of the beta program? I’m still running 4.36.0.125 and have never had the problem you are speaking of.
Thank you for the heads-up. I had the same issues on some of my v3 cams and tried loading beta 228 firmware yesterday. Problem cams have been streaming continuously with no problems since.
I was able to update to that firmware while on the production app though I believe it was meant for the beta app, based on the Facebook post/changelog.
Exactly, so why are people talking about beta firmware as the fix? This happens over and over again here in the WYZE forums. If people wish to discuss beta firmware fixes in the “Ask the Community” section of the forum, the least they could do is state that they are talking about beta firmware.
We should all try to keep in mind that as WYZE continues to grow there will be more and more people here that aren’t technology geeks.
yes, I am aware of how the beta program works…like I said, I was using the production app at the time & was able to update to that firmware…but regardless, this thread was about the v3 streaming issue & I only mentioned there was a firmware update available to fix the issue. not sure what your point is about the beta firmware
My point is there is not a version of the firmware available to 99.5+% of WYZE users that will fix the issue. The initial replies in this thread did not make that clear. It does now though as the reply was edited.
and as I stated numerous times, when I posted there was a firmware update, I was using the production app, AFAIK, that firmware is STILL available to production app users, regardless if it’s listed in the firmware webpage
Because the fix to a “public firmware issue” happens to be currently resolved in a “beta firmware release” which was just released.
I am very thankful to @Ken.S who answered my original post that has the resolution, even if it is a beta version. If I was a user who was suffering from the issues in this public release, and didn’t get the update because I was not in the beta program, I would have not known unless someone answered my post like he did. So you keep saying we shouldn’t be talking about th fix I asked for, but I disagree.
The beta firmware hasn’t been released as of 12/18/2020 @ 8:30am CST. I’m glad that the original reply has been edited to clarify that the issue has been fixed in a beta release of the firmware. Hopefully that beta version becomes a general release in the near future.