in android , app info>clear cache and or data.
stream1 more stable than 0 but still getting video artifacts, no disconnects though, i think its issues with their wifi driver in the beta rtsp fw
I’m only using stream 1 for detection and only recording events. Been very reliable so far.
On that note, Wyze, I’d love to have the ability to pass parameters via the query URL (?fps , etc). For detection, I’m happy to use 10-15 fps, don’t need to use that extra bandwidth.
What is supposed to be the difference between stream numbers?
stream1 is the substream, lower quality video stream, less bandwidth, less bitrate, smaller resolution, good for monitoring stream but not good for recording, in blue iris you can stream/view using substream but record using the main stream, stream0. im still getting some video artifacts, flicker, using substream stream1 in blue iris with panv3
I would love to find a solution to this as well.
I updated one of my V3’s to 14.36.16.5654 and TinyCam can no longer connect. I also tried using the RTSP feed in TinyCam without any luck
i had no luck with tinycam, but “ ip cam viewer “ for android works flawlessly
This appears to be a tinycam issue. Tinycam appears to be abandonware, unfortunately. Has not been updated in a while.
im running an old version of ip cam viewer, so its not about updates its about the url syntax thats not working, in blue iris i had to set it to http and vlc for it to work which is not the typical way for it to work, it works and hope wyze updates will fix it
@G2740 I’m having problems with frigate go2rtc and V3.
Can you share your frigate camera settings?
Sure, but be aware that what I have produces nothing but errors in Frigate and go2rtc in the logs.
Still works, displays cameras in Frigate and Home Assistant, detects etc. never have gotten there completely. Mine are all Pan V3s. Still a work in progress when or if I feel like fighting with it again. It got tiresome.
‘‘‘
mqtt:
enabled: true
host: 172.16.0.57
user: mqtt-user
password: REDACTED
go2rtc:
streams:
wyze_pan_v3:
- ffmpeg:rtsp://MyWyzeRTSP:REDACTED@172.16.0.35:554/stream0
wyze_pan_v3_2:
- ffmpeg:rtsp://PanV3BasementWindows:REDACTED@172.16.0.34:554/stream0
wyze_pan_v3_3:
- ffmpeg:rtsp://PanV3BasementDoor:REDACTED@172.16.0.33:554/stream0
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
detect: -threads 3 -f rawvideo -pix_fmt yuv420p
input_args:
- -rtsp_transport
- tcp
- -timeout
- '10000000'
detectors:
coral:
type: edgetpu
device: usb
model:
path: plus://a1b0949e2c7233c9e367ff8caada5d5a
cameras:
wyze_pan_v3:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/wyze_pan_v3
roles: [detect, record]
input_args: preset-rtsp-restream
detect:
width: 640
height: 360
fps: 5
objects:
track: [person]
filters:
person:
min_score: 0.20
threshold: 0.28
min_area: 50
motion:
threshold: 15
contour_area: 5
improve_contrast: true
mask: 0.721,0.929,0.724,0.983,0.984,0.987,0.979,0.928
wyze_pan_v3_2:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/wyze_pan_v3_2
roles: [detect, record]
input_args: preset-rtsp-restream
detect:
width: 640
height: 360
fps: 5
objects:
track: [person]
filters:
person:
min_score: 0.50
threshold: 0.58
mask:
0.91,0.074,1,0.077,0.995,0.994,0.369,0.988,0.502,0.838,0.597,0.753,0.73,0.778,0.839,0.678,0.891,0.591,0.906,0.392
motion:
threshold: 30
contour_area: 10
mask: 0.723,0.938,0.725,0.985,0.98,0.981,0.972,0.925
wyze_pan_v3_3:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/wyze_pan_v3_3
roles: [detect, record]
input_args: preset-rtsp-restream
detect:
width: 640
height: 360
fps: 5
objects:
track: [person]
filters:
person:
min_score: 0.60
threshold: 0.68
motion:
threshold: 30
contour_area: 10
mask: 0.721,0.977,0.981,0.982,0.977,0.934,0.716,0.929
record:
enabled: true
alerts:
pre_capture: 10
post_capture: 7
retain:
days: 10
mode: active_objects
detections:
pre_capture: 10
post_capture: 7
retain:
days: 10
mode: motion
snapshots:
enabled: true
timestamp: true
bounding_box: true
clean_copy: true
retain:
default: 10
detect:
enabled: true
‘‘‘
@G2740 Thanks for the config.
I think I my issue was that I had the special character ‘+’ in password, changing to ‘=’ seems to have fixed the issue . I also tried ‘+’ as %2B but neither worked
1 Like
I used ^.
My latest messing with this shows cleaner logs by adding this after each stream0 in Frigate config. Seems to help the Wyze disconnects or flaky RTSP…
#video=copy#audio=copy#audio=opus#reconnect=10s#reconnect_streamed=10s#timeout=30s
And my global ffmpeg changes.
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
detect: -threads 3 -f rawvideo -pix_fmt yuv420p
input_args:
- -rtsp_transport
- tcp
- -timeout
- ‘30000000’ # increase from 10s to 30s
- -fflags
- nobuffer
- -flags
- low_delay
- -strict
- experimental
Of course I had to push it and add a Reolink Lumas Pro 4k WiFi back into things. 
So far nothing major in the logs. One Wyze error.
I should be more patient, but I’m not. If the Reolink introduces more log errors I can always revert and hash it out again.
Frigate is running in Docker, and HAOS in an Ubuntu KVM VM. Coral USB, so far. All on the same PC.
Only a few bours in, will see what overnight brings.
Is there anywhere we can download the 5654 firmware for the Pan V3?
as far as I can tell, there is no link on there for 5654 firmware for the Pan v3
youre right, sorry did not notice that
For some reason, I have been able to install Wyze Cam v3 Firmware 4.36.16.5654 on 2 of my 5 cameras. But the last 3 are stuck on version 4.36.15.4389.
I have the Wyze Beta App on my Android Phone.
I’ve tried resetting the cameras that won’t update several times, in attempts to trigger the update.
Could these 3 v3 cameras have slightly different hardware, causing them to lag behind?
I would update the firmware manually, but couldn’t fine a download link to firmware 4.36.16.5654.
I think this is an incremental release based on MAC addresses. Give it some time, it will be available eventually.
1 Like
Will do.
Thanks!
1 Like
i had one v3 camera i could not successfully do all the incremental updates to get up to the rtsp fw, one of the updates soft bricked the cam and had to manually reset it to get it back up, will manually flash it eventually as it is not currently part of my active cameras