I am holding on to until you guys iron all the creases 
Once officially working, I’ll dive into it and see if I have the need for it or not.
But WyzeBridge (mrlt8) isn’t working anymore for the V4 @WyzeEric
Or did i something wrong 
I’m about to take off my diving gear and surface.
One Pan V3 camera out of 3 worked?
I have the money for cams that already work. 
However, I too will just wait and see a for a couole months.
Last 3 days have been a trip.
Works for me still. Try this @Jeetje…
Well Ai unicorn suggestion🦄 was a waste of time. I’ve done all I can currently do. One in 3, Pan cam v3s worked.
I’m waiting a few months. Last 3 days have been been nothing but frustrating.
Ai Bantha Fodder.
For my network, this only worked with 1 of my cameras, the rest were erroring so I had to abandon it. Really need RTSP built in so I can get back to monitoring my home easier. I really don’t want to replace all my cams.
Not for me anymore 
DOCKER-WYZE-BRIDGE v3.12.3 AARCH64 NIGHTLY BUILD [2025-09-21t22:37:11.509z] f0bb190 USING MTX 1.12.3
[WyzeBridge] [MTX] Setting up default RECORD_PATTERN=‘/Record/{cam_name}/{cam_name}_%d-%m-%Y_%H-%M-%S’
[WyzeBridge] [MTX] The computed record_path: ‘/Record/{cam_name}/{cam_name}_%d-%m-%Y_%H-%M-%S’ IS VALID
[WyzeBridge] 
Could not find local cache for ‘auth’
[WyzeBridge] 
Fetching ‘auth’ from the Wyze API…
* Serving Flask app ‘frontend’
* Debug mode: off
[WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on all addresses (0.0.0.0)
* Running on http://127.0.0.1:5000
* Running on http://192.168.178.20:5000
[WyzeBridge] Press CTRL+C to quit
[WyzeBridge] 
Saving ‘auth’ to local cache…
[WyzeBridge] Could not find local cache for ‘user’
[WyzeBridge] Fetching ‘user’ from the Wyze API…
[WyzeBridge] Saving ‘user’ to local cache…
[WyzeBridge] [AUTH] WB_AUTH=False
[WyzeBridge] Could not find local cache for ‘cameras’
[WyzeBridge] Fetching ‘cameras’ from the Wyze API…
[WyzeBridge] [API] Fetched [2] cameras
[WyzeBridge] Saving ‘cameras’ to local cache…
[WyzeBridge] [+] Adding Achtertuin [HL_CAM4] at achtertuin
[WyzeBridge] [MTX] Starting record for achtertuin
[WyzeBridge] [MTX] The computed record_path: ‘/Record/{cam_name}/{cam_name}_%d-%m-%Y_%H-%M-%S’ IS VALID
[WyzeBridge] [MTX] 
Will record 1800s clips for achtertuin to /Record/%path/%path_%d-%m-%Y_%H-%M-%S where %path will be achtertuin
[WyzeBridge] [+] Adding Voortuin [HL_CAM4] at voortuin
[WyzeBridge] [MTX] Starting record for voortuin
[WyzeBridge] [MTX] The computed record_path: ‘/Record/{cam_name}/{cam_name}_%d-%m-%Y_%H-%M-%S’ IS VALID
[WyzeBridge] [MTX] Will record 1800s clips for voortuin to /Record/%path/%path_%d-%m-%Y_%H-%M-%S where %path will be voortuin
[WyzeBridge] [MTX] starting MediaMTX 1.12.3
[WyzeBridge] 
2 streams enabled
2025/11/18 23:57:34 INF MediaMTX v1.12.3
2025/11/18 23:57:34 INF configuration loaded from /app/mediamtx.yml
2025/11/18 23:57:34 INF [path achtertuin] runOnInit command started
2025/11/18 23:57:34 INF [path voortuin] runOnInit command started
2025/11/18 23:57:34 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
[WyzeBridge] 
Received event: Init for achtertuin
[WyzeBridge] 
MediaMTX Initializing WyzeCam V4 - Achtertuin on 192.168.178.169
[WyzeBridge] Received event: Init for voortuin
[WyzeBridge] MediaMTX Initializing WyzeCam V4 - Voortuin on 192.168.178.163
[WyzeBridge] 
Connecting to WyzeCam V4 - Achtertuin on 192.168.178.169
2025/11/18 23:57:34 INF [RTMP] listener opened on :1935
2025/11/18 23:57:34 INF [HLS] listener opened on :8888
2025/11/18 23:57:34 INF [WebRTC] listener opened on :8889 (HTTP), :8189 (ICE/UDP)
2025/11/18 23:57:34 INF [SRT] listener opened on :8890 (UDP)
[WyzeBridge] Connecting to WyzeCam V4 - Voortuin on 192.168.178.163
2025/11/18 23:57:40 INF [RTSP] [conn 195.240.59.44:64454] opened
2025/11/18 23:57:40 INF [RTSP] [conn 195.240.59.44:64454] closed: no stream is available on path ‘voortuin’
2025/11/18 23:57:40 INF [RTSP] [conn 195.240.59.44:61904] opened
2025/11/18 23:57:40 INF [RTSP] [conn 195.240.59.44:61904] closed: no stream is available on path ‘achtertuin’
2025/11/18 23:57:50 INF [RTSP] [conn 195.240.59.44:62053] opened
2025/11/18 23:57:50 INF [RTSP] [conn 195.240.59.44:62053] closed: no stream is available on path ‘voortuin’
2025/11/18 23:57:50 INF [RTSP] [conn 195.240.59.44:63581] opened
2025/11/18 23:57:50 INF [RTSP] [conn 195.240.59.44:63581] closed: no stream is available on path ‘achtertuin’
[WyzeBridge] 
Timed out connecting to Achtertuin.
[WyzeBridge] Timed out connecting to Voortuin.
2025/11/18 23:58:00 INF [RTSP] [conn 195.240.59.44:64716] opened
2025/11/18 23:58:00 INF [RTSP] [conn 195.240.59.44:64716] closed: no stream is available on path ‘voortuin’
2025/11/18 23:58:00 INF [RTSP] [conn 195.240.59.44:62808] opened
2025/11/18 23:58:00 INF [RTSP] [conn 195.240.59.44:62808] closed: no stream is available on path ‘achtertuin’
[WyzeBridge] Connecting to WyzeCam V4 - Achtertuin on 192.168.178.169
[WyzeBridge] Connecting to WyzeCam V4 - Voortuin on 192.168.178.163
2025/11/18 23:58:10 INF [RTSP] [conn 195.240.59.44:64900] opened
2025/11/18 23:58:10 INF [RTSP] [conn 195.240.59.44:64900] closed: no stream is available on path ‘voortuin’
2025/11/18 23:58:10 INF [RTSP] [conn 195.240.59.44:60945] opened
2025/11/18 23:58:10 INF [RTSP] [conn 195.240.59.44:60945] closed: no stream is available on path ‘achtertuin’
I totally understand but were you attempting to run this as a Home Assistant addon? I tried a couple of different ways running on my underpowered NAS also on a VM Docker instance but ultimately the easiest and also best performing way I found was running it as an addon in HA. I have multiple Wyze Cam v4 cams working with this fork of Wyze Bridge and then passing onto Frigate for local detection (also using Google Coral TPU). Also, I am very much looking forward to NOT using the Wyze Bridge anymore and having direct RTSP integration with the firmware.
It is running in a separate Docker container on a Raspberry Pi 5.
I’m excited that this is a work in progress and hope it eventually makes it to the bulb camera. I bought one a couple weeks ago, and love everything about it except my inability to get it working with scrypted. it’s a great camera and I want to buy more Wyze stuff, and am kind of waiting to see how this RTSP project ends up before pulling the trigger on replacing some of my other cameras.
Well, tried it within HOAS with the following setup:
ENABLE_AUDIO: false
ON_DEMAND: true
MOTION_API: false
CAM_OPTIONS:
MEDIAMTX:
- WB_AUTH=false
WB_AUTH: false
WYZE_EMAIL: blablabla@gmail.com
WYZE_PASSWORD: blablabla
API_ID: blablabla
API_KEY: blablabla
WB_IP: 192.168.178.120
But no succes.
Also have Frigate in HOAS and also a Coral TPU
I did not configure any custom settings in HA addon (possibly try that later). I just browsed to the Docker Wyze Bridge add on and clicked on “open web ui”. Then, through the GUI… I added the wyze api id and key. It may not hurt to reset/refresh the key first too.
Well, Frigate is working. Added Frigate+ just for the heck of it.
Support if nothing else.
Fine tuned model added for Coral edgetpu USB.
One Pan Cam V3, in it, 2nd Pan Cam V3 wouldn’t flash, reverts to previous firmware,
3rd Pan Cam V3 did flash but won’t stream in Frigate yet…
One Reolink added. (Sorry lol),
That’s where I’m at.
The Pan V3 that is in Frigate is a little bit dirty/noisy so far in comparing.
For the “reverts to previous firmware” after you flash to rtsp firmware… did you try disabling automatic updates on that camera?
Thanks, I did not try that, but have turned it off now and will try reflashing, when old age energy level permits. LOL
I may also remove the RTSP from the one that doesn’t stream to Frigate and I’ll turn off auto updates there as well and try reflashing. Or just try reflashing again.
By the way, Welcome to Wyze.
Eric has been working wonders at Wyze for over 4 years. 
Tried that and its a no. I’ll try a different format on the SD but it’s already Fat.
That Pan Cam just restarts, held 6 seconds, not blinking, nothing. tried factory reset also, accidentally lol. that doesn’t help either.
No luck at all Think i have to wait for an upgrade or RTSP Firmware
What hardware are you running HA on then? My concern is that currently I am only using Home Assistant Green as the hardware, which is basically like a raspberry pi with fairly limited resources for processor and RAM, etc. having docker wise bridge or frigate as local add-ons for such limited resources feels like it could quickly get overwhelmed, especially for those of us who have dozens of cameras. That is my concern. But I got that hardware when I was still pretty new to home assistant. I’m not opposed to upgrading to something Superior now that I know it’s going to be a long-term primary system for me. I am just not sure how intensive things are going to get locally hosting some of those add-ons and how much I need to compensate for it.
I do have a Google coral USB device, I know the home assistant green only has USB 2 slots and the coral works better with USB 3, so even with connecting up a separate USB splitter that can support USB. 3, the connection will still ultimately bottleneck at usb2 . So I still may need to upgrade The hardware anyway. The question is how much of an upgrade do I really need to consider. That is where I’m hesitating right now and trying to figure out a reasonable guess. (Don’t worry, I will not take anybody’s estimates or suggestions or personal use cases as anything other than data for me to make my own choice, and will absolutely not blame anybody if I ultimately choose wrong for my own situation. I’m just trying to get a feel for what is likely needed, and then we’ll probably do something a little bit higher than that for a little bit of future proofing. Currently, I’m leaning toward a fairly strong mini PC with the coral TPU attached, or I might just do like cyber dog and get a full-on server)