RTSP broke for me on the firmware upgrade to version 4.50.17.10, want to rollback to firmware version 4.50.17.7064 but cannot find a link,
can anybody direct me to this download>
TIA
None of the versions after December have download links. Not sure the reason for it but it could be that it is not possible (or is risky) to roll back once certain new security or features are put in place. The only thing I can suggest is to reach out to support and see if they can provide you a link. What about RTSP has broken? I don’t use it but my Panv3s all show the RTSP option with the latest firmware installed. May just be a matter of re-configuring it?
contacted support via live chat, but no resolution, the previous version is not available for download??? because it’s still rolled out??? this while the latest version is also rolled out. does not make much sense to not have a rollback available.
Live support was also useless, as they just write you back the script answers from the help bot. presently i lost all my camera’s rtsp feeds. my mistake of course to have the firmware update on automatic and me choosing to update all firmware versions on all camera’s at once…
All 3 non-downloadable versions still say they’re being rolled out gradually, may or may not have something to do with it (i.e. they may still be considering them “current”). Or it could be like I said, rolling back risks bricking the cam.
@WyzeJasonJ or @carverofchoice happen to have any insight?
In the meantime, have you tried resetting the RTSP and starting from scratch? Maybe it is something as simple as they’ve changed the stream name/number or it just got corrupted and needs you to re-enter the credentials.
My Panv3s are on an isolated network (and isolated from other devices on that network) but if I have a chance I’ll pull out my spare one and join it to my main LAN to see if I can get RTSP going on the latest firmware. Or maybe someone who has it working (I’m guessing you’re not the only RTSP user that got the latest firmware) will have some tips on getting it working again.
yes, went to complete factory reset and have interrogated the camera. the final answer:
Cam Pan v3 firmware 4.50.17.10: native RTSP configuration is available in-app, but TCP port 554 is closed after enabling RTSP, and a clean factory-reset/reconfiguration does not start the RTSP service.
any suggestions?
@Crease have you used RTSP on your Panv3(s)?
I’ll check mine if I have a chance later.
yes, it was working perfectly on the previous firmware
I was tagging another member and asking him
Just set up my spare one and so far it is listening on 554 (I set it up for regular RTSP). Are you using RTSP or RTSPS?
Changing to RTSPS and it is listening on 322.
It is running the latest firmware.
I’ll test it out with VLC a bit later.
Are you running it on an IOT or guest network? That will likely not work with RTSP unless you allow it LAN access (which also typically disables client isolation).
I would check your PC firewall and your router to see if anything may be blocking it.
at the moment the camera is running firmware: 4.50.17.10, just came out (should not have upgraded​
) using RSTP, just running it on my main LAN network
Mine is up and running fine using RTSP (not RTSPS) in VLC. I don’t think VLC supports RTSPS
rtsp://username:password@192.168.0.50:554/stream0 is the format for the stream
Try telnetting to the camera IP on port 554 (if RTSP) or 322 (if RTSPS). If you don’t get a blank screen and it times out, something is blocking your traffic.
EDIT - Sorry I just saw that you’re already on the firmware that was released today. I don’t have that yet, I was assuming it was the firmware that came out a couple weeks ago but just looked and saw it came out today. Unfortunately I can’t test until my cams get the update.
the firmware you using was the firmware which worked for me as well. doing some more testing using RSTPS as this seems to be open
Welcome to the Forum, @DamCaptain! 
If you think that’s what broke RTSP for you—and given what you’ve described so far, I imagine you’re correct—then I’d be inclined to post in the announcement topic for that firmware version, which is App and Firmware updates - Released 8/11/2026. If you can submit an app log and then post the Log ID along with a description of the problem and any troubleshooting you’ve attempted to that topic, then that’s one way to get better visibility from Wyze on this issue. I haven’t yet seen anyone else report loss of RTSP with that firmware version in that topic.
I have, but the Cam Pan v3 I just connected to using VLC is still running firmware 4.50.16.6242, so I’m afraid I can’t currently provide much direct help for this particular experience. It’s still working for me with that older firmware.
BTW, thank you for pinging me with the @‍mention. I prioritize those, and it likely would’ve taken me a while to get to this discussion otherwise. 
FWIW, I’m using TP-Link equipment and have my Cam Pan v3s (and other Wyze Cams and devices) on an IoT network, and I’ve found that enabling Device Isolation for those does seem to kill the RTSP feed when I want to test it, so I explicitly disable Device Isolation for those Cams when I want to use those streams on my LAN.
I believe this is correct, and Wyze’s document indicates that RTSPS (or at least their implementation) is not compatible with VLC.
I hope you have better success with that. I wish I had a better answer for you. I do think making them aware of the issue in the Wyze News topic I linked above might be helpful. Hopefully this is something they can isolate and fix fairly quickly with another update.
funny part is RSTPS is open and working, unfortunately Synology Surveillance Station is not working with RTSPS only RTSP. Luckily my friend ChatGPT build me a quick docker bridge RTSPS - RTPS, so for the time being i’m up and running again, thanks for advising me
Yeah that’s the recommended solution for VLC and other stuff that doesn’t support it (yet) too.
Yeah, they stopped supporting rollback and firmware flashing to recent firmware versions (anything related this year). I could get a link to a firmware from last year, but that won’t solve the RTSP issue
I’m surprised I haven’t seen others bringing up this issue yet. At least you reported it with support so they can start tracking it.
This is a good example why they should go back to making firmware available for download.
I wonder if they just want to make it more difficult for bad actors to easily analyze it.
You may be right. Check out this article.