Can confirm that the controller still works in the app when upgrading to the firmware that has RTSP available - what stopped working though was the wyze bridge that I had, and I cannot get the stream to come up in milestone no matter what I tried for settings.
Welcome to the Forum, @kodys000! 
Thanks for the confirmation about the Garage Door Controller with the new firmware. 
Is that with this earlier β firmware or with the production version 4.36.16.5654?
I saw your earlier post about Milestone but don’t have any experience with that. I’ve been able to make the RTSP stream work in VLC, FFplay, and OBS (and the RTSPS stream work in FFplay). I’ve seen other users report getting it to work in Blue Iris, and some have struggled with that, so I wonder if the peculiarities of setting that up might help you with Milestone. This seems to be a decent template screenshot for Blue Iris, just in case it might guide your Milestone settings:
Would you be able to tell me what you used to get FFPlay to work? I am trying to get ZoneMinder set up (might abandon Milestone completely) and I’m having an issue with ffplay even getting it to pull up.
[in#0 @ 0x58eb44e38d40] Error opening input: Invalid data found when processing input
Error opening input file rtsp://Admin:Paasfasbsffsb!@10.0.190.8:554/stream0.
Error opening input files: Invalid data found when processing input
Edited to add: This is the most recent official version of the firmware.
Following the directions on the Wyze RTSP Testing Instructions page, the recommended URL (edited for correct username, password, and IP address) for FFplay worked for me when I had RTSPS enabled:
ffplay -protocol_whitelist "tcp,rtsp,tls" -i rtsps://myuser:mypass@192.168.1.33:322/stream0 -loglevel debug
When I disabled RTSPS on my Cam Pan v3 and wanted to try it with straight RTSP, I had to make some adjustments because of errors FFplay was showing me, so I ended up with something like this:
ffplay -protocol_whitelist "tcp,rtsp,tls,rtp,udp" -i rtsp://myuser:mypass@192.168.1.33:554/stream0 -loglevel debug
I’m not sitting at my Linux PC at the moment, so I’m going from memory, but I think that’s correct. The main adjustments I made were these:
- changing
rtspsin the URL tortsp - changing the port in the URL from
322to554 - adding
rtpandudpto the-protocol_whitelist(I think I’m remembering this correctly and can re-check later)
Also, please be sure that you’re using the -loglevel debug flag for FFplay when trying to troubleshoot your command. I don’t have enough experience with it to know if you were or not based on the output you shared above, but I think that’s what helped me figure out which additional protocols to add to my command.
If you try that and still have problems, then feel free to “@Crease” me and I’ll take another look at it on my machine.I looked and confirmed that it’s what I was using before (more information is below).
One other thought if you’re sure that everything else is correct: When I tried streaming via RTSP on a Windows PC using VLC, everything worked as expected, but when I tried the same thing using OBS it kept failing until I created an “allow” rule in the third-party firewall I was using. I don’t know if that could be happening with the stuff you’re trying to do or not, but that’s an additional variable to consider.
Edit @ 2026-02-20T16:15:15Z
Apparently my memory was correct, because that second FFplay command (edited for my username, password, and local IPv4 address) was what I had in my bash history that worked. I played with it a little bit out of curiosity and found that I could eliminate both tls and rtsp from the -protocol_whitelist switch, and it still works:
ffplay -protocol_whitelist "rtp,tcp,udp" -i rtsp://myuser:mypass@192.168.1.33:554/stream0 -loglevel debug
I also wanted to mention that—as others have noted elsewhere—stream1 works, as well:
ffplay -protocol_whitelist "rtp,tcp,udp" -i rtsp://myuser:mypass@192.168.1.33:554/stream1 -loglevel debug
If you’re feeling adventurous, then you could try the production firmware update, see what happens, and report back to the community. If that nukes your Garage Door Controller feature, then I imagine you could re-flash older firmware.
I was feeling adventurous, so I started the firmware update chain from 4.36.10.4054, which was the last version that I could get to work with the Wyze Bridge. Inching forward one update at a time, it took me 4-5 updates to get to 4.36.14.3497, and now I’m stalled, because it says, “Everything’s good! Your camera is up-to-date.” and there is no option to update to 4.36.16.5654, nor a way to manually download it from the Firmware page where it’s listed. So now I can’t see it in the Bridge, which means I can’t see it in Blue Iris.
Is this just an availability thing, where 4.36.16.5654 doesn’t appear for all cameras right away, as it slowly rolls out?
I wish I’d known that before I got adventurous.
Ugh. I now see that this is a known issue:
That is my understanding from the announcement topic:
Yeah, that’s obviously a newer reply in that topic, and it’s nonspecific. I guess it’s probably best to read it as all four firmware releases have been halted, because the Release Notes & Firmware page doesn’t show notes about pauses for any of these. 
I guess you can flash back, depending on how long you want to wait. 
I managed to do this for grins and am able to see a live stream from my Cam Pan v3, so that’s certainly possible.
Thank you so much for doing this. I sold much of my wyze cameras because of the lack of this feature and a windows client. But I held on to two of them and now they work great in my Home Assistant. I bought a V4 just today thinking all things were equal, but I guess I’ll be returning it and getting one or two more V3’s. Please never obselete this. The cameras are working great! Maybe even better than my reolink cams.
Hey @bryonhu, are you reading this? 
Depends on the model, I seriously doubt the comparison is against a 4k series camera…..
Wyze where are we at on that promise of RTSP coming to some newer cam models? We all went out and bought some, time for y’all to deliver on your word. It’s almost March now…
Oh yeah I don’t mean in terms of quality and stuff. I just mean the now seamless integration to home assistant and reliability of the stream. Reolink still takes the cake in 99 percent of cases. Just pleased my v3 stream is as reliable as the Reolinks are and like I said maybe even better for home assistant.
of course I can’t speak for all the other Wyze models that don’t have rtsp or integrate at all which automatically makes Reolink better.
I was just yanking your chain my friend 
I know, but had to reply 
We are still working on the newer models, we have not abandoned it.
I just got another V3 cam, and while I have a couple cams running 4.36.16.5654, the new one is not updating automatically and the “release notes & firmware” page doesn’t allow me to download and manually flash the new FW. It is not hyperlinked. So I just wait? Or can I download the FW somewhere?
Due to reported issues, 4.36.16.5654 firmware has been halted until Wyze rectifies them.
My two RTSP V3’s do not record events, is this normal? I can’t remember if they ever did when I enabled RTSP. When I go into the Event Recording settings it has a message “Event will be recorded only when the camera and PIR sensor detect motion” but the Cam v3 does not have a PIR sensor… The message also appears when I select “All events”
Slightly OT, but can you post a photo of your video wall? That sounds awesome!