Version: 3.13.0.b778
What’s new:
- Added support for Android 1x1 single device widget
- Bug fixes
Finally!
Installed latest beta app. Don’t see a 1x1 widget.
Will restart device and see if it appears.
Restart did not make it appear.
I don’t see it either under Android 10, 12, 15 and 16.
Bleh. I haven’t actually grabbed the public beta to see for myself, and now I’ll probably just stick to the production track. I was pleased to see this announcement because I’ve thought for a long time that the other widgets have seemed unnecessarily large and other users and I have suggested the 1 × 1 size for a long time, so I thought maybe they’d finally done it. Guess not. 
A workaround for 1x1 Android widgets: Delete current widgets, delete Wyze app, sideload 2.50.9.512 or 2.50.7.487, drop 1x1 widgets wherever, update Wyze app to latest, don’t mess with your 1x1 widgets. 
Con to doing that, you’ll have to redo your preferred 3.x device order and recreate your Favorites.
It’s a funny thought, but I’m not seeing it work on the phone where I have both the current Wyze app and an app clone of v2.50.7.487. For one thing, the smallest widget that older app is making available to me is 2 × 2, and that’s for a shortcut (not a device); the smallest device widget I’m seeing with that version is 3 × 3. I can’t make either of those any smaller. This is why I’ve said for a while now that widgets are broken and why they should really implement Android App Shortcuts and iOS Quick Actions instead.
The other problem with the way I’m doing it (two apps) is that the clone has a different package name (which allows it to be installed concurrently with the more recent app), and I imagine either the package name itself or some unique system ID for that particular application determines which app launches from a widget, so when I tap the widget to view a device it opens in the older clone app and not in the newer app (because I didn’t do it the way you suggested, which might work, but it’s not something I’m eager to try because of the con and because getting this working right now is a low priority for me).
I can wait on this to be real and actually implemented, but for now I’m glad that it’s been announced as a beta thing only (which hopefully indicates that they’re actually working on this) and not as a non-working feature in a production app, and I’d also still like to see them do work on the app shortcuts and Quick Actions instead, because that might be a better solution for delivering 1 × 1 launchers for specific intents rather than implementing these as typical widgets. I have a few apps that I access most frequently with built-in app shortcuts (e.g., the authenticator module I use in an app where I get TOTP codes for MFA), and it’s great to be able to get to a specific part of an app with a single tap from a regular-sized icon rather than launching to the app’s home and navigating through the UI to find the thing I want. That’s what I’d like to see Wyze do.
Maybe something changed? I’ll try to redo 2.50.x widgets in a bit. I use only the Monitoring and single-device widgets. I use 2.50.x only for testing.
I don’t know. On my 32-bit Android Go tablet that’s stuck on app v2.50.9.512, the smallest I’m seeing are 2 × 2 for Device, Event, Rule, and Wyze Home Monitoring.
I don’t want to derail this topic too much. I think it’s cool that they seem to be announcing work on Android widgets, but I’m getting the impression that the announcement may be premature (and I say this knowing that beta software is expected to have issues).
Appreciate Andriod app v3.13.0 (b778)
I really like the latest app version on my android phone. The live camera views finally load very fast and I no longer have to wait a few minutes. Thank you!!!
[Mod Note]: Your topic was merged to this Beta announcement topic for better visibility to Wyze.
@WyzeAndy App crashes when trying to add Wyze switches
Log number 2333630
Pixel 8 Pro XL: Massive background battery usage with this build. By itself, using up 40-50% of all utilization. Turning off background access in Android does not prevent from occuring either. In addition, app is super sluggish on this build and seems to hang frequently (high CPU utilization?). Please fix whatever was broken in this latest beta build.
I have a Pixel 9 Pro and not experiencing this issue at all. I have all permissions set and for the App Battery Setting I have Allow Background Usage.
Battery usage only indicates 10%. I get a lot of notifications as well.
Do you have your app running in the foreground all the time?
No. I rarely pull the actual app up. I too get a lot of notifications (significant number of cameras). I just checked , and I have 3:16min screen time overall (all apps) since last charge, and Wyze has 3:20 minutes background usage on top of 3 minutes of screen time. I tried disabling background usage in case that would temporarily resolve, but it hasn’t. This is the only app even coming close to these kind of utilization numbers. Chrome itself is 2nd place with 16 minutes. I’ve never encountered this before with any Wyze build, so not sure what’s up. I suppose I could blow away the cache and reinstall and see if it fixes, but posted here just in case others were experiencing similar.
Edit: On a side, but possibly pertinent note, this phone is running the latest Android 17 QPR1 beta, build CP31.260403.005.A1
Update: While clearing cache, data, and reinstalling appears to have solved the sluggishness, the battery usage sink still exists. No other app comes close to this level of utilization even with foreground utilization.
My radar is up. This morning my Samsung s24 was dead battery. I didn’t think to much of it until I read your post.
I looked at my battery usage and wyze didn’t even show up. I went back a day and wyze took over. See screenshot.
Never seen this before but as I said earlier wyze isn’t even showing up today. Maybe the phone needed a cold start. We will see. I’ll keep an eye on it.
Samsung S24 ultra, Android 16
App version 3.13.0.b778 when I try to view any event in the app it immediately closes. I’m seeing this on both my S25 Ultra phone and Tab S10 Tablet. I did try clearing the app cache.
Release version of 3.13 has resolved the closing on trying to view events.