In the last week or two, the app has started really chewing through my battery when the app isn’t being used. I can go to the battery usage settings and the Wyze app is the number one battery usage app by a large margin, even over the operating system. The app isn’t open and I haven’t used it in hours, yet it is still chewing through my battery.
V2.50.2 (442)
Check 2 settings:
in the app go to Account>AppSettings and make sure Enable Hardware Decorder is off and Running in the background is off. Note: This is my setting
Long Press on the app and choose App Info, scroll down to Battery and set it to Unrestricted.
By having it set this way, you will still receive notifications, but the battery drain will be less. I have a Pixel 8 and a Samsung Pro +, both of which end the day with excess of 50% battery remaining. The Wyze app uses .3% in my case and I get hundreds of notifications a day.
My App Version is: 2.50.1 (441)
I am having the same problem. It just started on April 21st. I have the two settings set the way you describe. My app version is 2.50.2 (442)
Having this same problem running the Wyze app on my MacBook Air to monitor and control a Wyze Thermostat -firmware version 1.2.8. The app draws the battery down very rapidly if left running in the background. Left running overnight the Mac battery is guaranteed to be fully discharged by sunrise.
I’m not seeing this on Android 14 with the same app version. It could technically be Android OS version or device specific but if someone is seeing it happen on a MacBook and someone is seeing it on Android… it has the appearance of being related to a feature, setting, or update problem perhaps.
I’m having same significant issue as of early May that started in mid-late April. 20% of battery use at end of day is from Wyze with less than 1 minute screen on time. 17 hrs of background running, 9 hrs of CPU time with 0 minutes screen time, 0 wake locks and 0 wake ups. Galaxy S23 Ultra currently running 2.50.5.449.
I have not added any new devices or changed my usage of the app. Have tried clearing the cache and adjusting app background usage to optimized and still having issues if not set to Restricted. Would like to get back to previous ability to not have app restricted to stop battery drain.
I’m having the same issue. It’s killing my battery and I only get a few notifications per day.
Any word on a fix?
I’m using the latest beta version.
Same issue, just started with the 3.0 app update. I’ve already fully uninstalled and reinstalled the app, toggled the run in background setting, no nice. I have a Pixel 7 Pro with the latest system update dated August 5th. My wife has the exact same phone and used the Wyze app as well, but isn’t experiencing the background drain.
We went through all of the notification and background settings on her phone and I made mine match, then fully charged the phone and waited. See below… This is critical, as my phone is now running through my battery by the afternoon instead of having well over 50% left.
I am still using App version 2.50 on my Pixel 6 Pro and have great battery life with 2.50. You can try an older Wyze App by grabbing the APK here.
With 1 Day and 20 Hours of use I am at 64% battery left.
That’s a workaround and requires enabling unknown sources to install the APK. I’m familiar with apkmirror and it’s generally safe, but it’s also not a fix. I want Wyze to fix the battery drain issue. Even with background support disabled it drains like crazy, but not all the time. I went half the day with it barely using anything to using 30% of my battery in 3 hours in the background.
I need the app for control and my watch to work but this is really a big issue.
Subjectively, I think the new app is draining battery faster on the one phone where I’ve installed it (which is another thing that makes me hesitant to update the Wyze app on my main phone). I mentioned in a post about the Cam v4 Picture-in-Picture feature that the v3.0 app appears to be able to create multiple running “instances” of itself and doesn’t appear to clean those up properly, so I wonder if there’s an underlying issue with the code that needs to be addressed.
