New Beta App released on 8/14

I am having the same problem with the 2.5.20 Beta version of the app. I cannot connect to v1 Wyze Cams. It just gets stuck on “3/3” and ultimately fails and says that is “cannot connect to camera”.

Hi Lee,

I am sorry you are also experiencing the issue. As i understand it they are aware of the issue and are working to resolve it. Please stay tuned!

Now you see why I refused to hold my breath… no Wyze chime on the subject. :wink: :grin:

I am sure someone will it just does not happen as fast as we, and they, would like sometimes. :wink:

It sometimes gets dark enough in certain weather to want the lights to go on in a room when it’s not sunset time. A real darkness sensor would be useful.

Sorry about this confusion. We removed the Hardware Decoder setting because we are using the Android original decoder instead of the old one. and which kind of decoding (hardware, software) mechanism would work according to the system default setting.

1 Like

Thanks for the reply.

So… will this setting… or something similar… be added after they get things sorted out? Not sure about others… but there is a 5-10 second lag in the Live Feed without this setting on all my android devices.

Just noticed an update to the beta app, 2.5.21. V1 cameras now streaming live video.

Fast and great work Wyze Guys (& gals :grin:)

1 Like

Can you sent the app log to abao@wyze.com

1 Like

Done … log sent …

There’s a good 10 second lag now in live stream after removing the hardware decoder setting. Could you revert back the setting? Thanks.

I’ve found some odd behavior… the first symptom was that my shortcut ordering was forcibly rearranged during last week’s outage. Once service was restored, I could no longer place shortcuts in the order I prefer. This was all under the GA app.

Rejoined the beta to see if that would jostle caches or other things governing, and sure enough I was able to arrange shortcuts again. However, any that I had automated were converted into “schedules” and became unavailable as actual shortcut buttons. That’s pretty presumptuous to decide for me that I can no longer manually actuate something that I’ve also scheduled… :slight_smile:

Left the beta again to see if the GA app would now allow manual arrangement, and no dice. Unclear if something within the beta conversion process somehow tags automated items, but this makes things really confusing for my parents. I’d FINALLY gotten them into a groove about which shortcut to use at particular times of day / situations, and now they have been randomly shuffled.

Please give folks the choice about whether to convert automated shortcuts into “schedules” (or at least leave the manual button in place) and let us keep things arranged as we see fit!

So sorry for your issues. I know how difficult it can be when the “rules” change rather suddenly. The issue of the sort order is being addressed, but I believe it will take a new release of the firmware to do so.

The Beta app extends shortcut functionality significantly. In essence the same manual ‘shortcut’ buttons still exist but some of the terminology has changed. It may help to think of the new ‘rules’ as the old ‘shortcuts’. If you are willing to rejoin the beta I can probably guide you into recreating your old shortcuts in the new format. As far as your parents would be concerned nothing would appear to have changed.

Bear in mind, it is a beta so there is a potential for things not working, and for things to change as the beta progresses. Again so sorry you encountered this.

Roger that, R.Bruce… but the initial problem I described is with the GA app. I rejoined the beta program solely as a test to see if shortcut control might be regained. Also, I have no problem keeping the items separate in my thought process - however I much preferred the dual functionality of both manual and automated control. Doesn’t make sense to have to build the same thing twice. This is exactly the sort of task where technology is supposed to simplify our lives - not create double the work :slight_smile:

I’m sorry to say that firmware “upgrades” are not a viable solution for me. I’ve found (and described in several threads) that Cam Pan firmwares beyond 4.10.3.40 radically alter the reliability of recorded footage for playback. Curious to know why a firmware upgrade would be required to effect what is essentially software behavior?

My parents are 500mi away from me and the “have trouble” firmware reversion feature has been removed. Not trying brick their cameras with no remote recourse. Way too much other trouble reported beyond the trouble I’ve actually experienced with later firmware.

Thanks for listening, however. Hopefully the dev team is monitoring chatter.

I don’t know for sure a new firmware is necessary, just something I recall reading. I have run into one other person that also said the more recent firmware releases caused positioning issues with their Pan Cams. But I have to say most I know have not found that to be an issue. I wonder if there are other factors at play somehow. In my own case my Pan does not appear to suffer thankfully, from any ill effects.

Again I am sorry for your difficulties, I do know that Wyze very definitely monitors this forum but if you want to certain of their involvement definitely contact support.

This post: Wyze App Service Outage - 8/22/19 did initially say “firmware” but has since been corrected to say it’s an app update that will be needed.

Also, while Wyze employees are sometimes present on the forum, it is intended as primarily as user-to-user community. If you need support, the proper thing to do is to make a Support Request

1 Like

Knew I had read it somewhere just could not remember where.

I know that you’re only trying to be helpful, R.Bruce, and I do appreciate it.

First off, the issues I’ve had with firmware haven’t been with physical positioning. They have been with the fact that once they tethered local recording to the cloud standard, much footage was missing when I went to review playback - routine footage that would’ve normally been captured with the .40 firmware. I haven’t tested with anything beyond .60/65 since Im at a distance; and also because I don’t really see a whole lot of detail about what’s been addressed in the firmware updates themselves. I’m a network engineer/admin by trade and we do appreciate knowing specifics… :slight_smile:

Second, I did submit several support tickets (at the behest of WyzeRoy). Spent several hours reviewing and documenting my findings prior to submittal. All that I ever rec’d back were platitudinal responses, acknowledgements that I had sent them something, etc.

Third, the only other “factors at play” from my perspective are that I’ve actually performed before & after testing to verify my claims. It would be nice to have the sense that this was occuring a little more robustly during development as well. I encourage Wyze not to wade too deeply into the Microsoft-esque update standard whereby the cure becomes worse than the original condition. An ounce of prevention (gentle, conservative development) is usually preferable to a pound of cure (sudden, drastic, forethought-lacking paradigm shifts that impair bread & butter functionality).

Unfortunately it seems all I can offer is further platitudes. I did read some of your other posts awhile back but was unable to duplicate your results. I am sure others have so I will wish you well but I can’t offer you any suggestions that are new or different than those you have already received.

Haha, well thanks for at least listening and taking the time to review what I have previously posted.

Two things would restore my Wyze world to harmony:

  1. Introduce a toggle that allows users to choose whether local and cloud storage are synchronized. To me the whole point of having a local storage option is to have greater control if the cloud is unavailable. I do also agree with other posts that I’ve read that cloud capture can be spotty (as is anything Internet dependent). Local storage was always a hedge against any instability there until recent firmware.

  2. Preserve the original shortcut buttons. The schedule idea is very good and I like it. However, it should be non-destructive and duplicate the buttons with some clear delineation of same. It would even be a clever thing to synchronously update the schedule item whenever one modifies the shortcut button.

That is all I have to say about that… :smiley: