Could you please confirm if you’re on Android or IOS , and what WyzeBeta app version you’re running. Thanks
Sure, Android 16, Samsung S24 Ultra. Beta RTSP app. 3.9.0.a905 Regular Beta app (b727)
I am running exact same phone and app version. If you get black screens in frigate, then something is just slightly off…
Are you sure that intel iGPU passthrough is working right? Are the reolink cams pulling in fine and showing up?
I would check these out in your config the input_args) :
wyze_pan_v3:
ffmpeg:
inputs:
- path: rtsp://USERNAME:PASSWORD@192.168.x.x:554/stream0
input_args: - -rtsp_transport
- tcp
- -stimeout
- “5000000”
roles: - detect
- record
detect:
enabled: true
width: 640
height: 360
fps: 5
objects:
track: - person
motion:
threshold: 25
contour_area: 30
Also, if unsure about the iGPU passthough, comment that out with # before that line and restart frigate.
Grab some logs if needed and drop here.
Can literally just copy and paste out of there.
1 Like
Appreciate it. Checking into it. I didn’t have issues until I added 3 Pan V3s today.
Further, all 5 cams pull in fine, its detections and reviews in Frigate web ui that are black.
Coral Usb Edgetpu, Frigate+.
My GPU is resident in the host machine. Whatever HP stuck it. It is a 6 core, 12 threads. Resident supposedly integrated Intel UHD Graphics 630.
I’ve been living dangerously and using Grok 4.1 Beta. Grok is a bit better than Gpt for me. Often Ai uses old data, but I’ve learned to cross check him with Gpt5, read docs, search etc.
So when problems pop up, I take my time now no blind copy & pasting, I broke Frigate enough already.
Groks last drop in suggestion;
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
detect: -threads 2 -f rawvideo -pix_fmt yuv420p
Adding these two lines might have fixed it.
output_args:
detect: -threads 2 -f rawvideo -pix_fmt yuv420p
Let me know if that stays stable for you. Nothing wrong with using AI. Like you said l, verify what it says and make sure it can be reversed, snapshot etc.
According to GPT those lines are baked into the default config of frigate, and the detect block may have had incorrect output_args. Not sure on that front.
1 Like
I can’t ever get Gpt and Grok to agree. Sometimes I throw the same yml at them, they just wrote and they find fixes.
It’s still throwing errors. Feeds are good.
I’ll have to dig to find the issues.
Finicky, just changed an object mask, restarted, logs are clear.
IOS users,
Update:
Unfortunately, that didn’t do the trick. I’m still getting (code -36). Btw, the camera is connected to the Wi-Fi. It has solid blue light. I think Wyze has to update.
I just got 32GB in the mail. I’ll flash the Pan V3 again. Hopefully that’ll make it work. Automagically!
1 Like
That’s one of my favorite parts of AI. “You just old me this 5 seconds ago, why are you backtracking GPT?”
Gotta love it!
1 Like
Latest running pretty good. So far.
mqtt:
enabled: true
host: IP
user: name
password: ************
go2rtc:
streams:
reolink_sub:
- rtsp://admin:************@IP:554/Preview_01_sub
reolink_main:
- rtsp://admin:************@IP:554/Preview_01_main
reolink2_sub:
- rtsp://admin:************@IP:554/Preview_01_sub
reolink2_main:
- rtsp://admin:************@IP:554/Preview_01_main
wyze_pan_v3:
- ffmpeg:rtsp://MyWyzeRTSP:************@IP:554/stream0#video=copy#audio=opus#audio=pcma
wyze_pan_v3_2:
- ffmpeg:rtsp://PanV3BasementWindows:************@IP:554/stream0#video=copy#audio=opus#audio=pcma
wyze_pan_v3_3:
- ffmpeg:rtsp://PanV3BasementDoor:************@IP:554/stream0#video=copy#audio=opus#audio=pcma
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
detect: -threads 2 -f rawvideo -pix_fmt yuv420p
detectors:
coral:
type: edgetpu
device: usb
model:
path: plus://************************ #custom model
cameras:
reolink_4k:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/reolink_sub
input_args: -rtsp_transport tcp
roles:
- detect
hwaccel_args: -c:v h264_qsv -hwaccel none
- path: rtsp://127.0.0.1:8554/reolink_main
input_args: -rtsp_transport tcp
roles:
- record
detect:
enabled: true
width: 640
height: 360
fps: 5
stationary:
interval: 50
threshold: 50
# … (rest of your reolink_4k config unchanged)
reolink_4k_2:
# … unchanged
wyze_pan_v3:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/wyze_pan_v3
roles:
- detect
- record
input_args: preset-rtsp-restream
# … unchanged
wyze_pan_v3_2:
# … unchanged
wyze_pan_v3_3:
# … unchanged
record:
enabled: true
retain:
days: 3
mode: motion
alerts:
pre_capture: 12
post_capture: 8
retain:
days: 3
mode: active_objects
detections:
pre_capture: 12
post_capture: 8
retain:
days: 3
mode: motion
snapshots:
enabled: true
timestamp: true
bounding_box: true
clean_copy: true
retain:
default: 3
detect:
enabled: true
version: 0.16-0
```
1 Like
Give it a minute 
1 Like
IOS Users;
App 3.9.0 Build (4) is out, still no fix for Pan V3 error (Code -36).
Cam v3 seems to be working fine.
Wyze? Any update on this for the IOS would be greatly appreciated.
Thank you!
Still get some log errors popping, nothing serious, still mostly same config, small numbers tweaks. Did update ffmpeg etc as @gnomos suggested this morning. I think latest is a Dec. 3rd, release. Mine was ancient, 6.1.1, lol. Just gonna let it run without messing with it a few hours, tired of zoning out junk that’s not a person.
1 Like
After some record block edits most of which was wrong I think. No detection and alerts etc. just record. So far. Lol,. And after turning off all cameras record to SD, which steals camera power, haven’t tried pan tilt either. locked in place for now.
2 Likes
I updated to the new build of the Beta App and now can’t see the camera I setup with RTSP. Anyone else experiencing this?
Is that beta app made for the main release beta, or is it meant for the RTSP beta release branch, if they are even branching it out like that. They do not have that clarified on the forum post. Could someone from Wyze specify?
Whoops looks like I have 2 beta apps now. The main release beta (build 4) won’t show the stream. The beta app (b23) downloaded using the doc provided shows the cam.
They’re supposedly working on combining the apps. There’s been two apps since RTSP release.
Standard beta app and RTSP app.
Beta app gets error 36 when trying to open an RTSP flashed camera.
But, RTSP flashed cameras open fine in the RTSP app. RTSP seems to only open flashed RTSP cameras.
I even read rumors of over the air RTSP instead of using an SD. TBD.
As far as I know, I’m no expert. And I’m using Android.
Plus, there was a hotfix for RTSP app to fix stuff.
1 Like
The general release app I encountered the error 36 when trying to view an RTSP cam. Tried the other app and it work fine. With the RTSP app I was able to see all my cams, until I updated one to the beta firmware available (non-rtsp cam). Then in the RTSP app I was unable to see it, but in the general release app I was able to see the stream.
And I’ve heard the same rumors of OTA RTSP firmware, saw it on a @WyzeDave post on reddit. Hoping it isn’t 2+ years before we see OTA RTSP firmware.
1 Like