Hundreds of i/o errors with Wyze v3

[robuck86]

My Wyze V3s are working pretty good with Thingino, but I get a lot (hundreds) of go2rtc errors like this github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error="read tcp 172.19.0.2:52382->192.168.0.167:554: i/o timeout" url=rtsp://thingino:thingino@192.168.0.167:554/ch0

I tried pinging the cams for a few minutes from a terminal, and I get about 10% packet loss. When I SSH to the cam and ping outward, I get 0% packet loss. I don't know why that's happening, but I assume this is why my frigate recordings are choppy.

I understand that WiFi isn't going to be as smooth as PoE, but are there any tweaks I can do to improve streams or is this just a limitation of the Wyze hardware? Should I change the GOP or framerate and if so, what's are good settings to try?

[cstout1]

I've got an issue open for trouble with Wyze v3 too. Connectivity and reliability issues with this hardware currently. #1045

[robuck86]

I wonder if the problem is weak WiFi on Wyze. Have you checked the signal strength? I ssh'ed to the cam and ran iwconfig to compare the signal strength of my wyze cams near the router (30/100) to a 'Defender Guard' brand camera in the same location which had a signal strength of 70/100 and an Arenti 110~ft away which just says 'Great' (whatever that means)

I don't know if 30-40% is 'acceptable', but it seems low to me.

[alan5ab]

I haven't had any issues with the V3s , including the ones running the 2-23 release . Try to keep within 30ft of an access point, lower the bitrate some..255/vbr and run go2rtc on the camera if you can.

[kovbalazs89]

Try to use UDP protocol as workaround. Maybe the camera is having problems interleaving TCP packets, because of the poor wi-fi performance.

go2rtc#1758

I'm using it without any problem, and there are no errors in go2rtc logs:

go2rtc:
  streams:
    galayou:
      - rtsp://thingino:thingino@192.168.0.208:554/ch0#transport=udp
      - ffmpeg:galayou#audio=opus

Frigate is also working, with recordings.