This is a dev log submission for beta Wyze app for Android version 2.32.0 (b148). No Wyze Customer Support action is necessary.
Problem Description: Tapping anywhere in the live stream space results in an exception thrown. UI forced back to Home screen.
Android versions affected: 8, 9, 10, 11 (12 not tested)
Viewing device types: Various Android phones and tablets
Viewing device orientation: Both portrait and landscape
Cam types tested:
Affected: Cam v2, Cam Pan v2, WCO, WCO v2
Not affected: Cam v3
Not tested: Cam v1, Cam Pan v1, doorbell (all)
Impact: Unable to perform any function that requires touch interaction in the live stream space. E.g., tap zoom, pinch zoom, pan, tilt, resolution settings and recording features in landscape, device/stream info in landscape, etc.
Note that the Wyze app has been changed to severely curtail the amount of text input and attachments for log submissions. This is now the max text allowed:
This is a dev log submission for beta Wyze app for Android version 2.32.0 (b148). No Wyze Customer Support action is necessary.
Problem Description: Tapping anywhere in the live stream space results in an exception thrown. UI forced back to Home screen.
Android versions affected: 8, 9, 10, 11 (12 not tested)
Viewing device types: Various Android phones and tablets
Viewing device orientation: B
I’m not sure why this change was implemented, but it is very counterproductive. If you are encountering issues with spam submissions, curtailing valid input is not the solution. The only workaround for log submissions is to link back to a forum post that conveys full details.
I have the issue with trying to connect to bluetooth devices. (band, watch & scale) Trying band & watch give “couldn’t connect”/“connection failed” errors, trying to connect to scale shows “loading” message for a second or two, then black screen then the home screen (i’m assuming that’s the app crashing/re-starting)
Tried uninstalling/reset/reinstalling, but no change.
Update: Looks great under Android 10 (phone) testing Cam v2, WCO, WCO v2 and Cam Pan v2 in portrait and landscape modes. Also tested Cam v3 even though it wasn’t affected. Good job!
I’ll now test under Android 8, 9 and 11 (mix of phones and tablets). It may take some time…
Update: Tested everything I could and it looks great Andy!
Running the 2.32.0 (b150) build now, and I can again connect to my Band, Watch and Scale.
however, the Band is no longer connected to Alexa. When i try to reconnect, I get to the screen with the “sign in with Amazon” button at the bottom, but tapping that button does nothing at all. I tried the usual round of resetting, clearing caches, reinstalling, etc, but no joy. Any ideas?
App version: 2.32 (b150)
On: Android 12 (Google Pixel 6)
Unable to sync Wyze Watch 47, 47C, Wyze Scale S, and Wyze Headphones. Unable to add devices after factory reset. Headphones randomly went missing from device list.
Never got a comment or response to this, so likely no one cares, but a follow-up anyway:
Connection to the Band and Alexa works again. I’m not exactly sure what the issue is, but after some research I think this was it:
When (b148) broke bluetooth connectivity, one of the things I did to try to fix it before knowing it was (b148)'s fault was to remove the Band from the Wyze app and then re-add it. That was a mistake. When connecting the Band to Alexa, the “sign in with Amazon” part apparently involves the Amazon Shopping app (directly? thru the Alexa app?.. don’t know which) and it turns out there’s been a problem with the Amazon Shopping app (possibly in conjunction with the Wyze app) that caused this to fail. And at least in my case, caused the Amazon Shopping app to fail & restart. If I hadn’t removed the Band, I likely would have been fine with (b150).
A few days later, both the Amazon Shopping App and the Wyze app were updated. One or both of those fixed the problem, and now everything works. I’m currently on Wyze 2.32.0 (154) and Amazon Shopping 24.12.6.100.
I noticed yesterday that the VoIP notification seems to not end the call on a secondary device when answered or declined on another device. Is this by design?
Basically, I have a Pixel 5 and Pixel 6 with that app on both. Someone pressed the Doorbell yesterday which I declined on my Pixel 6 as I walked out of the garage and saw the individual. A few hours later I came back home and my Pixel 5 was still ringing.
I was curious if this is the intended option or if there is a timeout for the VoIP to hangup after a period of time which is not firing?
BTW: I am sure not many have 2 devices tied to the same account actively being used for testing. So this may not have been considered.
Yes, it’s a 
