It is the same beta app that was uploaded on Oct 24 that mentioned it had a crash bug.
SHA-256: e29d39d31fdf20a95a2bf7bf03029080bbce0b60aefae4d6b18986a34404f0e0
It’s identical to the previous app link that has the crash bug. I’m guessing they uploaded the wrong APK to the new link or they are just using a new link that doesn’t require a passcode, and an updated app will be released later.
I showed where they diff the same, and now my post is gone. 
Alright, we’ve got one link now with everything…check this. https://wyze-beta.s3.us-west-2.amazonaws.com/rtsp.html
Yeah, the link Dave just posted is the same apk, so I think your guess is right.
Thanks, it’s great to have everything on the same page! 
I like it!
Why post it if users say it doesn’t work? Am I missing something?
I wouldnt be affected by the stream bug as I just want to enable RTSP, but sadly am getting the other issue instead. But those that can enable it can then test with other systems.
They should publish it until it is working to avoid confusion.
Yes. It still works to set up the camera on rtsp. You just cannot do the live stream through that app or it will crash the app. However, The rtsp app does not have an installation conflict with the production or beta app that goes through Google Play. This means you can have both installed at the same time.
This means that you can use the crashing app to set up the camera with RTSP, But then use the normal production or beta app to view the live stream. You just can’t control the rtsp settings in the production or beta app. So, really you only need the rtsp app to be able to set up the rtsp settings. After that, you don’t really need to use it anymore anyway, so it’s no big deal that you can’t stream through that app. But now, you will be able to use rtsp and view it through nearly any other source.
I don’t understand, it won’t let me configure RTSP.
For awareness, the latest android apk version @WyzeDave posted appears to have the same file name as the version from 10/24:
Wyze_3_9_0_a903_542750.apk
Even so, after installing this update I am now able to complete the RTSP setup flow (“Next” after username input now advances to password definition, as expected) and I’ve successfully set up the Generic Camera RTSP feed on Home Assistant! Furthermore, I am not encountering any crash on streaming from the WyzeRTSP app.
I remain eager for a proper Home Assistant integration with sensors and controls to compare with my Tapo C120 equivalents, but this is a big step forward and important to acknowledge—many of us have been waiting many years for this!
@WyzeDave will there be a way to do OTA updates once the beta and mainline firmwares merge?
I have some of my cameras in enclosures that are harder to access physically.
Thank you again for adding this feature.
I don’t understand why it’s not working for me. I’ve already installed it on two devices and it won’t let me configure RTSP.
If you are not making it to the RTSP password screen after setting your user name, try rebooting the camera through the settings menu, and retry as soon as it restarts. I found that worked for me on two of my three V3s.
Nothing works 
I’ll try another question: @WyzeDave, should we be submitting logs from the WyzeRTSP app and then reporting Log IDs and issues to the Wyze RTSP Round 1 Feedback you linked in the initial post? I’m still unclear on the expected issue tracking/reporting process, and I imagine community members who are willing to test this might appreciate some guidance.
That’s because it’s exactly the same file, which I demonstrated with a diff output earlier before my post was removed. Only the source link was different, and that’s what I was trying to get some clarity about when I replied to @WyzeDave’s earlier post. I believe @grapefruityoda’s assessment is also correct.
I appreciate this advice, and I’m glad it worked for you. Unfortunately, I seem to be stuck in a loop with the single Cam Pan v3 I’m trying so far. Initially I got as far as the waiver acknowledgement screen, because I intended to try it with RTSP and not RTSPS, but no matter what I chose the app kept sending me back and forth between those two screens (the one with the two buttons for making the RTSPS choice and the one with the acknowledgement). When I quit and tried to start over again, I couldn’t even get to the password entry screen: As soon as I tried to assign the RTSP username (didn’t matter if I tried the same name I initially assigned or something different) and hit the “Next” button, the app dumped me back to the initial RTSP settings screen, and that’s where I remain in this process.
I’ve now done a factory reset on the camera, re-flashed the camera with the new firmware (which displays the correct test firmware in Device Info), and cleared Android’s cache and data for the WyzeRTSP app, but that’s not helping me to advance past the naming screen now.
That camera has a lot going for it. I’ve used one for over a year.
2025-10-28T08:37:03Z Edit: Sometimes persistence stubbornness pays off. I decided to continue beating my head against the 
and finally got to the password setting screen again. After getting that set, I didn’t want to risk the no-RTSPS loop again, so I left that enabled and was able to continue. Now I have a Cam Pan v3 streaming to my PC via FFplay.
2025-10-28T09:18:50Z Edit:
I’m seeing this when I put Cam Pan v3 into “Privacy Mode”, as well. That Cam’s tile within its app group says, “This device has been turned off.” If I enter its Live Stream screen, I can see that the Privacy Mode icon is green. Despite this, FFplay is still capturing frames and shows a screen with black snow and an incrementing time stamp. It also continues to play audio coming in from the Cam. This is not what I would expect from a feature called “Privacy Mode”.
I’m also seeing a significant (~45-60 seconds or so?) delay between what the production app shows coming from the camera versus what the player for the RTSP stream is showing me, but that may be at least partly a consequence of how I have the network configured for this PC, so I’ll do some testing later under different conditions.
The Add Device > Cameras screen is blank in the RTSP beta IOS app. I cannot add the camera in the Beta app. I was only able to add it in the production app. Then, back in the beta app, I can access the RTSP settings.
I’m running the RTSP trhough Scrypted. Working well so far.
I’m pushing the feed into Apple Home via the Scrypted Homekit plugin. Working well so far.
However, I am unable to configure it in Apple Home as a Homekit Secure Video device. I believe more settings/alerts need to be exposed. I think ideally adding ONVIF support would be ideal.
ONVIF: I’ve tested the alternative firmware Thingino on both an old V2 and a V3 and it works really well. Maybe @WyzeDave should take a peek at it. 
Can you share any tips on how to bypass the username loop?
Almost literally this:
I tried what @danl suggested many times. Like I said, I did a full factory reset, flashed the test firmware to the device twice, and blew away the app’s Android data (thinking something may have been stuck there), which required me to re-authenticate when I launched the test app again. I couldn’t tell you which combination resulted in success, because it seems like a game of chance. I was just stubborn (foolish?) enough to keep trying.
If I had a magic formula, I’d share it. I don’t. I just know that once I got the password set after not even getting that far for so long, I wasn’t going to risk blowing it by telling the settings not to use RTSPS. I haven’t yet tried turning that off since I got it working the first time. That’ll probably be another future test.
Good luck!