search

mrlt8 / docker-wyze-bridge

WebRTC/RTSP/RTMP/LL-HLS bridge for Wyze cams in a docker container
GNU Affero General Public License v3.0
2.64k stars 162 forks source link

VDB returns to SD mode in Wyze app #366

Closed cheme75 closed 2 years ago

cheme75 commented 2 years ago

I tend to think this is a Wyze firmware issue, I’m on the fw beta x.1.060, posting here just in case. When I view the doorbell in the wyze app first time, it’s set back to SD. Once I select HD it stays. Then next morning when I check it, it’s back to SD. Other cams stay in HD. Frankly, I’m not a coder and can’t do much reviewing the source code, but logically Insee no reason this bridge would cause it since it’s just reading data. Just odd.

mrlt8 commented 2 years ago

Yeah, this seems to be another weird wyze bug that affects some cameras. I noticed some of my cams will always attempt to use the SD first while others will always just use whatever the last resolution was.

The bridge should be able to detect when this happens and change it back to whatever is set in your docker environment or use the default HD120 for cams and HD180 for the doorbell. You'll typically see something like this in the logs the first time it happens:

[Front] WARNING: Wrong resolution (frame_size=1)
[Front] Requesting frame_size=0 and bitrate=120
[Front] WARNING: Skipping smaller frame at start of stream (frame_size=1)

The change usually happens within a few frames but can sometimes cause the bridge to restart the process for that camera.

If you look at the timestamp in the app, you can usually see the font change when it switches back to the HD stream even if it still says 360p or SD.

cheme75 commented 2 years ago

It’s a bit weird that I only notice it with the main db cam. I haven’t added the 2 beta db cams to HomeKit yet, but in the wyze app they seem to retain the HD. The two beta db cams seem to have a lot of issues in the docker log. I haven’t had time to sit and go through the log but I think there’s lots of timeouts from the 2 betas, much more than the retail db. I’ll have to play with some settings and if they remain flaky, I’ll filter them out. The two v2 cams look solid last I saw after getting the 1.4.1 update. So far no chance to test the audio. Maybe tomorrow.

cheme75 commented 2 years ago

Update: may have been an app issue - got an updated beta and so far not seeing any returns to SD. Also so far sound seems to be working ok.