What I did: I went into the TStat app settings and told it to “Restart Device”
I couldn’t tell through the app if it actually restarted or not so I waited several minutes then did it again. Then waited a while and did the same thing from another device. Then waited a while again. After rebooting the Tstat probably 3-5 times I finally attempted an update again through my Android Studio Emulator running API 33 (Android 13) on an emulated Pixel 4 (latest production app) and it updated successfully this time.
Can’t say for sure what made the difference this time or if it’s coincidence, but it did work on my like 9th or 10th attempt So we’ll roll with it, at least it worked.
We might have some struggles with this when it rolls out to production though if it took some of us this many tries to get it to go through. Just wanting to report the experience for the Wyze devs to know how it went. Ultimately it was successful though.
I’m going to keep track. They’ve been offline a few days now, they’re set to auto, and working. My router shows them as being connected, but the wyze app says no.
I’ll give them a restart tonight and make sure I’m on the latest beta release and will report back!
This is why we beta test, we try our best to try and catch as much as we can before it goes live. Not many companies even do this sort of thing and I’m happy that Wyze does. It does suck and does happen but at least they do seem to listen when people report issues with beta firmware.
Thanks! Life just got super busy. Long story short, got a promotion at work and my only co worker jumped ship to a different unit to take a promotion there, which left me as the sole person. I’m holding my own, but working a bunch of extra hours and my dumb butt got the wild idea to volunteer to help out another unit on top of my full plate. Coupled with some vacations and some health issues with my old @$$ furries I’ve just been on a short hiatus.
I promise to be more active this next week as I’ll be on vacation! Yippee!