At this point I’m operating on the hope that neither of my 32GB-or-less cards are good, and I’ve ordered a couple more 32GB’ers. I get occasional strange messages that the card is defective and needs to be repaired (then when I ‘repair’ it, it says the card was fine). Could be my USD card reader. I’m sure I have another one hiding around. We’ll see.
Real-Time Streaming Protocol (RTSP) allows you direct access to the video feed so you can add it to other custom applications to view it (VLC, OBS, Home Assistant, etc). You are no longer locked into using the Wyze app to play back the live feed.
Example: You can play back the live feed on your computer with a video playback application. So now, I can stream all my cameras to my computer while I am working, instead of flipping back and forth to my phone (because that’s annoying, who wants to do that?)
It may not matter for some people. But here is why others might care:
Yeah, that’s why when I’ve needed to do this I just take the whole thing where I can plug it into a power strip and then just flip the switch while holding the Cam’s SETUP button.
Yes, exactly like that.
(I’m reading as I reply. Not the best way to do this.
)
For the single Cam Pan v3 I’m testing so far, this is exactly what I used, too.
At this point I’m operating on the hope that neither of my 32GB-or-less cards are good, and I’ve ordered a couple more 32GB’ers. I get occasional strange messages that the card is defective and needs to be repaired (then when I ‘repair’ it, it says the card was fine).
Have you ever tried using SD Memory Card Formatter in “Overwrite” mode on any of those cards? Take a look at this post and then continue reading the discussion to the end of the topic for more context. It might be worth a shot.
Thanks to everyone for the explanation. I’ve filed it in the grey matter for future reference should the need ever arise.
For now I’m quite happy with my.wyze.com. The only time I view my cameras through my phone is when I’m not at home, which really isn’t that often, since I work out of my home.
My cameras even integrated nicely with my Google Home, so for now I can’t think of any reason to get excited about RTSP, but I could see that changing in the future.
Honestly, this is the hard part in some cases.
considering that most of us already have the cameras mounted and set up, it’s hard to plug in the micro USB cord with a single hand while pressing the reset button with another hand, joe would then basically have to use your teeth to help plug the micro USB cord into the camera while your other hand is holding the reset button. Lol
Yeah, that’s why when I’ve needed to do this I just take the whole thing where I can plug it into a power strip and then just flip the switch while holding the Cam’s SETUP button.
If I need to get up on the ladder to do some firmware flashing on a mounted device then I will bring a battery power bank + extra usb cable with me to power on the device and start the flashing sequence, but I usually fumble the microSD card and spend time looking for it in the grassy area
.
I learned my lesson to update and flash only beta firmwares on easily accessible cameras so I can easily revert back.
Have you ever tried using SD Memory Card Formatter in “Overwrite” mode on any of those cards? Take a look at this post and then continue reading the discussion to the end of the topic for more context. It might be worth a shot.
Oh wow, great resource. Thank you, I’ll give that a try!
then I will bring a battery power bank + extra usb cable with me to power on the device and start the flashing sequence,
That’s what I used for one of mine too!
but I usually fumble the microSD card and spend time looking for it in the grassy area
.
Heh, ditto. Even if they are indoors, they’ll hit the carpet and bounce to hide somewhere random.
Username Loop issue update:
I installed more V3s and tried a bunch of things including waiting a while for things to update. Only one thing works and it works immediately every time:
- First, you do have to wait a few minutes after flashing until you at least get to the username the first time, try to enter it and verify it’s looping.
- Back out to the restart setting button and press it
- Immediately click on advanced settings and then immediately click on RTSP. It will show it is loading for a few seconds
- When it suddenly lets you in, hurry and enter and submit the username.
I have done this a handful of times now and it always works to break the username loop. If you take to long and let the camera fully boot up first, then it will always loop at the username. It’s almost like you have to catch it while it’s in the boot stage before it’s fully loaded, kind of like restarting a computer and holding or tapping a keyboard key to get into the BIOS settings. That’s what it feels like to me. If you let the full Linux OS totally load up first, then you can not access the RTSP settings (BIOS) after that and have to restart and try again. That’s what this feels like.
I’ll submit that feedback in the official feedback soon, but wanted to share here for anyone still struggling with the username loop.
I cannot install the app on my Pixel 9 Pro XL it just keeps saying package is invalid, I’ve tried all the different links provided by Dave Crosby on the forums and the email but it just won’t install for me unfortunately, wonder if it’s a Pixel phone issue somehow.
wonder if it’s a Pixel phone issue somehow.
It installed for me on my Pixel 10 Pro XL
Having said that, for a short time Google tricked me into trying their lousy “Advanced Protection” feature. It was a horrible experience for me that took weeks to undo it (technically it let me change the setting and disable it, but it didn’t actually turn off… My phone said that advanced protection was turned off, but my Google account still showed that it was turned on, but Google wouldn’t allow me to access and turn it off through my admin settings, and locked me out of it for a couple of weeks even through devices I’ve been using for years. It was kind of crazy. I’ll never use it again. But the reason I bring it up is because It definitely blocks all side loading as invalid packages. That might be your problem. If you aren’t using advanced protection on your Google, I believe there is another new separate setting that does something similar.
But I can confirm that it works on pixels… At least the ones that have advanced protection disabled and similar settings.
I think the latest version is invalid (Uploaded yesterday)
Android: Download Wyze (Android) version: Wyze_3_9_0_526006 updated: 10-29-2025
Its only showing 11 MB vs the previous version at 300 MB.
I am going to try a lot of the workaround today for getting around the username loop.
Welcome to the Forum, @Kmorimt! ![]()
I think you’re right about the app. I haven’t yet transferred it to a phone or tried seeing if it will install, but the file size seems odd (unusually small) compared to other Wyze apps I’ve used in the past, and the package name and application label/title for this one are completely different compared to the initial release:
$ find *.apk -type f -exec sh -c "echo '{}' && aapt d badging '{}' | awk '/package|application-label-en/' && echo '\n'" \;
Wyze_3_9_0_526006.apk
package: name='com.alexvas.rtsp.demo' versionCode='1' versionName='1.0' compileSdkVersion='36' compileSdkVersionCodename='16'
application-label-en-AU:'Rtsp demo'
application-label-en-CA:'Rtsp demo'
application-label-en-GB:'Rtsp demo'
application-label-en-IN:'Rtsp demo'
application-label-en-XC:'Rtsp demo'
Wyze_3_9_0_a903_542750.apk
package: name='com.wyze.rtsp' versionCode='61666' versionName='3.8.0' compileSdkVersion='35' compileSdkVersionCodename='15'
application-label-en:'WyzeRTSP'
Thanks for posting about this! I didn’t know that a new APK had been linked until I saw your post. ![]()
The one you linked does the same invalid error and doesn’t install for me so something’s up forsure.
I don’t have the advanced program enabled on either my phone or account, I never even enrolled in either. It’s an APK link error clearly cuz the one linked in the document just never works, not sure where to find the right APK at this point .
not sure where to find the right APK at this point .
You can try copying the text (not the linked “anchor” that points to the amazonaws.com site) from Dave’s link in this post and paste that into a browser. That should still allow you to download the initial Android APK release if you don’t want to wait around for the next bug fix.
This worked and installed thanks ![]()
Right on. Thanks for the update! ![]()
That makes it sound like the latest APK uploaded has a corrupted error since the older download worked, but the newer one won’t, and most of us already had the older one.
I don’t know what this newer download is supposed to be because the size, package name, and label/title all seem weird in comparison to the initial APK release. I still haven’t tried installing it, but given the differences I’m seeing, I wouldn’t expect it to replace the initial app even if it does install (because of the different package name).
Has anyone gotten this to work with frigate?
ERROR : Error opening input file rtsp://*:*@10.0.51.4:554/stream0.
ERROR : Error opening input files: Invalid data found when processing input Flood-Light: Unable to read frames from ffmpeg process.
ERROR : Flood-Light: ffmpeg process is not running. exiting capture thread...
ERROR : Ffmpeg process crashed unexpectedly for Flood-Light