Our internal team just confirmed this bug is fixed in the next release.
I am not using the RTSP firmware, was trying to help out. 
Check your other choices in Make, I don’t think Wyze supports Onvif, but also don’t know that for a fact either. I do not use Blue Iris.
Is there just Generic or PTZ or RTSP,? or something of the sort?
Yes the onvif was for Dream Machine and no it does not support it or at least not yet. Some reason they don’t support generic rtsp.
Blue Iris on the other hand does and I’m using said generic style rtsp. I used it on other cameras even custom firmware by the community for v2 and even wyze-bridge before. But I wanted to now support and use the new RTPS directly but having issues with it.
I might need to setup a VM or something later when I have time with 100% fresh install of windows / blue iris just to make sure nothing I’m doing wrong.
I feel like it should work, but shocked no one else here seems to be using it.
Blue iris has a free (watermark) version so if anyone ever wanted to mess with it they could.
I will keep puttering away though like I said overtime, maybe I will figure something out.
Same here, Frigate even with plus is kicking my butt tuning with a Coral USB. Wyze V4 detects trucks and cars better. lol. I’m thinking Blue Iris is Windows only.
I’d have to spin up a Windows VM probably, I tossed out all Windows and went Linux when MS said throw away a perfectly good PC for Win 11.
Still have an old & funtional Tandy 1000 with DOS. 
Going through the same thing, just now getting the Coral TPU usb working via proxmox to passthrough hass container.
First is to get ‘lsusb’ showing the coral usb in non-whatever-mode and showing “Google Inc” you have to do, on the proxmox host:
git clone --recurse-submodules https://github.com/google-coral/webcoral.git
cd webcoral
scripts/linux_device_rules.sh install
make reset
And secondly - this is important - when doing the usb passthrough to the hass VM do “Use USB Port” e.g 7.1, it may say “Unplugged” but it still worked for me. “Use USB Vendor/Device ID” did not work, I suspect due to it changing the address once the Coral USB kicked in.
Now it’s getting the frigate addon to work with the rtsp stream, rtsp works fine with vlc etc but frigate is NOPEs. Suspect it’s something to do with ffmpeg not playing right with the rtsp encoding, about to jump into to the vm and see.
2025-12-10 20:44:28.967678727 [2025-12-10 12:44:28] watchdog.mover_camera ERROR : Ffmpeg process crashed unexpectedly for mover_camera.
2025-12-10 20:44:28.967949960 [2025-12-10 12:44:28] watchdog.mover_camera ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2025-12-10 20:44:28.968138439 [2025-12-10 12:44:28] ffmpeg.mover_camera.detect ERROR : [in#0 @ 0x555652ce6d80] Error opening input: Invalid data found when processing input
ERROR : mover_camera: ffmpeg process is not running. exit
Solved, i think it was mentioned here earlier, you have to use go2rtc as the go-between - ffmpeg in the frigate container doesn’t seem to play well with the rtsp stream from the wyze.
Relevant parts of frigate config.yml -
detectors:
coral:
type: edgetpu
device: usb
# Use go2rtc to restream cameras
go2rtc:
streams:
# Wyze Pan V3 – low-res detect stream (often stream1)
mover_detect: "rtsp://hass:*@192.168.86.231/stream1"
# Wyze Pan V3 – high-res record stream (often stream0)
mover_record: "rtsp://hass:*@192.168.86.231/stream0"
cameras:
mover_camera:
ffmpeg:
inputs:
# Frigate reads the *local* go2rtc stream, not the camera directly
- path: "rtsp://127.0.0.1:8554/mover_detect"
roles: [detect]
input_args: preset-rtsp-restream
# If you later want full recording, you can add:
# - path: "rtsp://127.0.0.1:8554/mover_record"
# roles: [record]
# input_args: preset-rtsp-restream
I run HAOS in Ubuntu, in a KVM VM, and the Coral is connected right to the host, Docker is running in the host as well.
My five cameras are running ok so far and yes Im using go2rtc as well.
It was tuning a Frigate+ model for the Coral USB that was and still is a bit of a pain point.
I’ll get there. Glad you found your issue.
I also found my ffmpeg way out of date 6.1.1 or something and I think its up to 8.
For RTSP Pan V3 users, not sure how you did it in Frigate. I naively thought, 
if I turned on detection zone they would stay put and not drift. Wrong.
Messed up every motion and object mask in Frigate.
So all three are back to track motion. Stays “fairly” close to position when at the home waypoint.
Of course panning and tracking motion sorta makes Frigate object & motion masks useless or possibly blocking stuff that shouldn’t be blocked.
Pan V3s were a good test bed though. Down the road I’ll retire them for fixed cameras. That means soon.
Still no luck with fresh Blue Iris install/instance on Windows. Seems like I’m the only person in the entire world trying use Blue Iris + Wyze 3 RTSP Beta hehe.
Blue Iris works great!! be sure you have rtsps turned off on the camera. Can the computer access the camera that is running blue iris try and use vlc on that computer and open network stream from VLC and put in your URL like RTSP://username:password@192.168.x.x
@WyzeDave They updated the play store beta and yet it does not work with RTSP firmware still also they have not even pushed new firmware for cameras to work with that build. Still code 36 on beta RTSP firmware camera on playstore build. What is going on? Why would you guys have 2 beta apps just crazy why you would want to be working on bugs on two of them not just one?
Darn, I wish I did something wrong haha. This looks right? No luck BTW kind of crazy and yeah VLC on the same instance works fine, I also tried ending slash and of course without vlc running in case only lets one stream at a time.
I recreated the RTSP as well, and yes I disabled RTSPS this time around right during creation where last time I did not. I also changed the password around just in case some odd symbol acted up, etc. Still nothing.
I wonder I run the latest nightly basically release a blue iris I wonder if that has anything to do with it what build are you running?
6.0.1 or something around those lines here.
I am on 5.9.9.98 as of right now and my Wyze cameras still working great actually two of my reolink cameras started acting up but Wyze have been rock solid so far for almost a month now. Things I would try.
Obviously rebooting blue iris box Blue Iris tends to get a little funky sometimes.
Disabled Windows firewall.
Go with real simple username password on RTSP No weird characters or anything funky.
Try creating a RTSP stream in Vlc with like a video file and see if you can’t add that to Blue Iris if that isn’t working then no RTSP is working in Blue Iris.
If that is the case I would contact Blue Iris and see what their input is.
Possible a codec thing on the blue iris system.
Sadly using Tapo C120’s and their working just fine with RTSP with very similar setup. I was hoping last ditch effort to use my wyze 3’s before moving for good ;(
Hey, for the Home Assistant, Generic Camera integration guys……
I am running a bunch of v3s in that same manner. Not this beta but something that I flashed in early 2025 which I believe is a modified version of that old old old official Wyze RTSP. If anybody really wants to know I can dig up the info for something that just simply works without banging your head against the wall for days.
BUT, I was having problems with generic camera giving me the first preview after setup. The little wheel would just spin forever and it would never show a functioning preview. Here’s the trick… I can’t say for sure but highly suspect that this will work for you. See screenshots below. After you loaded all your HTTP business and RTSP info, submit that. AND THEN… When that little screen with the spinning wheel that you are waiting to see your preview is running, it will never show the preview just hit everything looks good after 10 or 15 seconds. That one little thing as worked 100% consistently for me 7 to 10 times!!! Good luck. HEY OFFICIAL WYZE STAFF, I purchased four brand new pan v3s just because of this RTSP announcement… I am capable of trying to sort through this beta business, but have been eagerly awaiting this official December 11, 12ish 2025 release. PLEASE give us an update of how that official version is coming along. I would much rather wait another week then fiddling around with what sounds like a temperamental beta version. Thanks. PS this is my first ever forum posting of any kind! Cheers
[Mod Edit]: Text formatting corrected for readability and Forum-preferred @mentions added for addressing several users in a single post versus making multiple redundant posts. Duplicate reply removed.
They better say something, I’m about to bail and order some more reolinks lumas pro. they work perfectly for $67 on sale.
Reolinks are awesome! I have got four, All battery / solar powered. The Atlas PT ultra, The battery doorbell, the Argus Track which I ended up returning because the swiveling head was just too creepy for my neighborhood as everybody would walk by on the sidewalk. AND, recently for about three or four weeks the Argus 4 pro which is awesome! I put that in the spot where people are walking by my gate so I didn’t want bright lights and swiveling heads to freak everybody out. That color night vision with virtually zero light is incredible and it has 180° visibility!
Home assistant integration is one of the best developed I’ve ever seen. And with moderate sun the batteries are almost always at 100% charged!
Home Assistant integration screenshot for just one of the cameras….
Guess we violated a rule.