Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Wyze Cam V4 [2K] #1172

Closed
towerrh opened this issue May 2, 2024 · 25 comments
Closed

Issue with Wyze Cam V4 [2K] #1172

towerrh opened this issue May 2, 2024 · 25 comments

Comments

@towerrh
Copy link

towerrh commented May 2, 2024

Hello,
I just added a camera to the docker wyze bridge. A wyze cam v4. I cannot get it to work, it will connect but it will not display an image or video. This is the indoor grow camera. I have confirmed it works fine on the wyze cloud. I am seeing the following errors:

[indoor-grow-camera] WARNING: Wrong (frame_info.frame_size=4) [indoor-grow-camera] Requesting frame_size=3, bitrate=180, fps=0 [indoor-grow-camera] WARNING: Skipping wrong frame_size at start of stream [frame_size=4] [WyzeBridge] 192.168.1.155 - - [02/May/2024 17:52:47] "GET /snapshot/indoor-grow-camera.jpg?1714690363007 HTTP/1.1" 200 - [WyzeBridge] 📕 Client stopped reading from my-room [WyzeBridge] 192.168.1.155 - - [02/May/2024 17:52:47] "GET /snapshot/my-room.jpg?1714690363008 HTTP/1.1" 200 - [WyzeBridge] 192.168.1.155 - - [02/May/2024 17:52:48] "GET /snapshot/indoor-grow-camera.jpg?1714690363007 HTTP/1.1" 304 - [WyzeBridge] 📖 New client reading from my-room [WyzeBridge] 📕 Client stopped reading from my-room [indoor-grow-camera] WARNING: Still waiting for first frame. Updating frame size. [indoor-grow-camera] Requesting frame_size=3, bitrate=180, fps=0 [indoor-grow-camera] WARNING: Audio pipe closed [indoor-grow-camera] [Exception] Did not receive a frame for 20s [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor Grow Camera on 192.168.1.200 [WyzeBridge] 📖 New client reading from my-room [indoor-grow-camera] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 70%) FW: 4.52.3.9455 🔒 [indoor-grow-camera] 🔊 Audio Enabled - AAC_ELD/16,000Hz [indoor-grow-camera] WARNING: Wrong (frame_info.frame_size=4) [indoor-grow-camera] Requesting frame_size=3, bitrate=180, fps=0 [WyzeBridge] 📕 Client stopped reading from my-room [indoor-grow-camera] WARNING: Skipping wrong frame_size at start of stream [frame_size=4]

I am not sure how to troublshoot further. Any advice would greatly be appreciated!

@towerrh
Copy link
Author

towerrh commented May 4, 2024

`

audio true
apartalarmParm { "heightY": "50", "longX": "50", "startX": "25", "startY": "25", "type": "0" }
audioParm { "sampleRate": "16000" }
basicInfo { "firmware": "4.52.3.9455", "hardware": "0.0.0.0", "mac": "80482C2E1777", "model": "HL_CAM4", "type": "camera", "wifidb": "70" }
channelResquestResult { "audio": "1", "video": "1" }
recordType { "type": "1" }
sdParm { "capacity": "488109", "detail": "0", "free": "248133", "status": "1" }
settingParm { "location": "1", "logSd": "1", "logUdisk": "1", "nightVision": "3", "osd": "1", "stateVision": "1", "telnet": "2", "tz": "-5" }
uDiskParm { "capacity": "0", "free": "0", "status": "2" }
videoParm { "bitRate": "30", "fps": "20", "horizontalFlip": "1", "logo": "1", "resolution": "2", "time": "1", "type": "H264", "verticalFlip": "1" }
connected true
dtls 1
enabled true
firmware_ver 4.52.3.9455
hls_url http://192.168.1.8:8888/indoor-grow-room...
img_time 1714835191000
img_url img/indoor-grow-room.jpg
ip 192.168.1.200
is_2k true
is_battery false
mac 80482C2E1777
model_name V4
motion false
motion_ts 0
name_uri indoor-grow-room
nickname Indoor grow room
on_demand true
p2p_type 3
parent_dtls 0
parent_mac  
product_model HL_CAM4
record false
req_bitrate 180
req_frame_size 3
rtmp_url rtmp://192.168.1.8:1935/indoor-grow-room...
rtsp_fw false
rtsp_fw_enabled false
rtsp_url rtsp://192.168.1.8:8554/indoor-grow-room...
snapshot_url snapshot/indoor-grow-room.jpg
start_time 1714839768.8054006
status 3
stream_auth false
substream false
thumbnail *************************
thumbnail_url thumb/indoor-grow-room.jpg
timezone_name America/Chicago
webrtc true
webrtc_url null
audio true apartalarmParm { "heightY": "50", "longX": "50", "startX": "25", "startY": "25", "type": "0" } audioParm { "sampleRate": "16000" } basicInfo { "firmware": "4.52.3.9455", "hardware": "0.0.0.0", "mac": "80482C2E1777", "model": "HL_CAM4", "type": "camera", "wifidb": "70" } channelResquestResult { "audio": "1", "video": "1" } recordType { "type": "1" } sdParm { "capacity": "488109", "detail": "0", "free": "248133", "status": "1" } settingParm { "location": "1", "logSd": "1", "logUdisk": "1", "nightVision": "3", "osd": "1", "stateVision": "1", "telnet": "2", "tz": "-5" } uDiskParm { "capacity": "0", "free": "0", "status": "2" } videoParm { "bitRate": "30", "fps": "20", "horizontalFlip": "1", "logo": "1", "resolution": "2", "time": "1", "type": "H264", "verticalFlip": "1" } connected true dtls 1 enabled true firmware_ver 4.52.3.9455 hls_url [http://192.168.1.8:8888/indoor-grow-room...](http://192.168.1.8:8888/indoor-grow-room/) img_time 1714835191000 img_url [img/indoor-grow-room.jpg](http://192.168.1.8:5000/img/indoor-grow-room.jpg) ip 192.168.1.200 is_2k true is_battery false mac 80482C2E1777 model_name V4 motion false motion_ts 0 name_uri indoor-grow-room nickname Indoor grow room on_demand true p2p_type 3 parent_dtls 0 parent_mac product_model HL_CAM4 record false req_bitrate 180 req_frame_size 3 rtmp_url [rtmp://192.168.1.8:1935/indoor-grow-room...](rtmp://192.168.1.8:1935/indoor-grow-room) rtsp_fw false rtsp_fw_enabled false rtsp_url [rtsp://192.168.1.8:8554/indoor-grow-room...](rtsp://192.168.1.8:8554/indoor-grow-room) snapshot_url [snapshot/indoor-grow-room.jpg](http://192.168.1.8:5000/snapshot/indoor-grow-room.jpg) start_time 1714839768.8054006 status 3 stream_auth false substream false thumbnail ******************** thumbnail_url [thumb/indoor-grow-room.jpg](http://192.168.1.8:5000/thumb/indoor-grow-room.jpg) timezone_name America/Chicago webrtc true webrtc_url null`

Could I be missing something? My v3 works perfectly fine. I am beating my head trying to troubleshoot this.

@mrlt8
Copy link
Owner

mrlt8 commented May 4, 2024

What version of the bridge are you using? The 2k stream on the v4 has a different frame size so you need to be running v2.8.x of the bridge.

@towerrh
Copy link
Author

towerrh commented May 4, 2024

Hi there,
I am running the latest from the main branch. Aldo try dev just to see if it would help. But unfortunately no luck.

@mrlt8
Copy link
Owner

mrlt8 commented May 5, 2024

Can you post the version number of the bridge from the logs?

@towerrh
Copy link
Author

towerrh commented May 5, 2024

🚀 DOCKER-WYZE-BRIDGE v2.8.3 X86_64
I apologize for my late response. See above.

@1fastt2
Copy link

1fastt2 commented May 6, 2024

I haven't been able to get my new V4 cams to work either. Also running 2.8.3.

@mrlt8
Copy link
Owner

mrlt8 commented May 6, 2024

Could you see if the latest dev builds work better?

@1fastt2
Copy link

1fastt2 commented May 6, 2024

Could you see if the latest dev builds work better?

I would love to however I have zero idea how to load the dev build using HA. I remember I’ve tried before but just gave up on it. If you could point me to a quick how to I’ll get it done. Thanks.

@widapro
Copy link

widapro commented May 6, 2024

It does not work on the latest dev build with sha256:6dfc89eba3a711be2c766d22c6da213b873b0c1de6f29eacc722b1d454301b5b

debug logs when WyzeBridge start:

22:27:00 [DEBUG][back-yard-cam] Connect via IOTC_Connect_ByUIDEx 22:27:01 [INFO][back-yard-cam] AV Client Start: chan_id=0 expected_chan=0 22:27:01 [DEBUG][back-yard-cam] Now listening on channel id 0 22:27:01 [DEBUG][back-yard-cam] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b'' 22:27:01 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10001 txt_len=17>: b'\x03\xc8\x03e\x8d\xaa\xebm>\xd8\xb4\xb6\xf2:\x90i'
22:27:01 [DEBUG][back-yard-cam] Sending response:
22:27:01 [DEBUG][back-yard-cam] SEND <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10008 txt_len=30> b'\xe1f\x8c\x9a]\xb5\x83mYy$\xc3\x9b\xc4\xf7\xba6f5a\x01\x01\x079959972'
22:27:01 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10009 txt_len=747>: b'{"connectionRes":"1","cameraInfo":{"audioParm":{"sampleRate":"16000"},"videoParm":{"type":"H264","bitRate":"30","resolution":"2","fps":"20","horizontalFlip":"1","verticalFlip":"1","logo":"2","time":"1"},"settingParm":{"stateVision":"2","nightVision":"3","osd":"1","logSd":"1","logUdisk":"1","telnet":"2","tz":"-4","location":"1"},"basicInfo":{"firmware":"4.52.3.9455","type":"camera","hardware":"0.0.0.0","model":"HL_CAM4","mac":"D03F27DE9FBA","wifidb":"49"},"channelResquestResult":{"video":"1","audio":"1"},"recordType":{"type":"1"},"sdParm":{"status":"1","capacity":"121922","free":"36445","detail":"0"},"uDiskParm":{"status":"2","capacity":"0","free":"0"},"apartalarmParm":{"type":"0","startX":"25","longX":"50","startY":"25","heightY":"50"}}}'
22:27:01 [DEBUG][back-yard-cam] SEND <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10056 txt_len=3> b'\x04\xfa\x00'
22:27:02 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10057 txt_len=1>: b'\x01'
22:27:03 [DEBUG][back-yard-cam] No longer listening on channel id 0
22:27:03 [DEBUG][back-yard-cam] [videoParm] {'type': 'H264', 'bitRate': '30', 'resolution': '2', 'fps': '20', 'horizontalFlip': '1', 'verticalFlip': '1', 'logo': '2', 'time': '1'}
22:27:03 [DEBUG][back-yard-cam] [cameraInfo] {'audioParm': {'sampleRate': '16000'}, 'videoParm': {'type': 'H264', 'bitRate': '30', 'resolution': '2', 'fps': '20', 'horizontalFlip': '1', 'verticalFlip': '1', 'logo': '2', 'time': '1'}, 'settingParm': {'stateVision': '2', 'nightVision': '3', 'osd': '1', 'logSd': '1', 'logUdisk': '1', 'telnet': '2', 'tz': '-4', 'location': '1'}, 'basicInfo': {'firmware': '4.52.3.9455', 'type': 'camera', 'hardware': '0.0.0.0', 'model': 'HL_CAM4', 'mac': 'D03F27DE9FBA', 'wifidb': '49'}, 'channelResquestResult': {'video': '1', 'audio': '1'}, 'recordType': {'type': '1'}, 'sdParm': {'status': '1', 'capacity': '121922', 'free': '36445', 'detail': '0'}, 'uDiskParm': {'status': '2', 'capacity': '0', 'free': '0'}, 'apartalarmParm': {'type': '0', 'startX': '25', 'longX': '50', 'startY': '25', 'heightY': '50'}}
22:27:03 [INFO][back-yard-cam] 📡 Getting 250kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 49%) FW: 4.52.3.9455 🔒
22:27:04 [WARNING][back-yard-cam] [Exception] Unable to identify audio.
22:27:31 [DEBUG][back-yard-cam] Connect via IOTC_Connect_ByUIDEx`

debug logs when I try connect to camera stream using VLC:

22:29:51 [DEBUG][back-yard-cam] [CONTROL] Attempting to GET: param_info 22:29:51 [DEBUG][back-yard-cam] Now listening on channel id 0 22:29:51 [DEBUG][back-yard-cam] SEND <K10020CheckCameraParams code=10020 resp_code=10021> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10020 txt_len=10> b'\t\x01\x02\x05\x06\x07\x15\x16\x1b2' 22:29:51 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10051 txt_len=6>: b'\xfa\x00\x04\x14\x01\x01' 22:29:51 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10021 txt_len=61>: b'{"1":2,"2":3,"5":20,"6":1,"7":1,"21":1,"22":-4,"27":2,"50":1}' 22:29:51 [DEBUG][back-yard-cam] No longer listening on channel id 0 22:29:51 [DEBUG][back-yard-cam] [CONTROL] response={'1': 2, '2': 3, '5': 20, '6': 1, '7': 1, '21': 1, '22': -4, '27': 2, '50': 1} 22:29:51 [DEBUG][back-yard-cam] [CONTROL] Attempting to GET: bitrate 22:29:51 [DEBUG][back-yard-cam] Now listening on channel id 0 22:29:51 [DEBUG][back-yard-cam] SEND <K10050GetVideoParam code=10050 resp_code=10051> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10050 txt_len=0> b'' 22:29:51 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10051 txt_len=6>: b'\xfa\x00\x04\x14\x01\x01' 22:29:51 [DEBUG][back-yard-cam] No longer listening on channel id 0 22:29:51 [DEBUG][back-yard-cam] [CONTROL] response=250 22:29:56 [DEBUG][back-yard-cam] [video] slow gap=1.3784780502319336 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.0415449142456055 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] Flushed 8192 from audio pipe 22:29:56 [DEBUG][back-yard-cam] Flushed 2366 from audio pipe 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.0815529823303223 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.1615700721740723 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.2015869617462158 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.281606912612915 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] Flushed 3547 from audio pipe 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.3616180419921875 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.4016389846801758 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-2.1611669063568115 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.5216701030731201 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.6016860008239746 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] Flushed 3536 from audio pipe 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.6817009449005127 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.721709966659546 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.8017261028289795 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.8417320251464844 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.9217579364776611 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] Flushed 3510 from audio pipe 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-2.0017690658569336 22:29:56 [DEBUG][back-yard-cam] flushing audio 22:29:56 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-2.0417799949645996 22:29:56 [DEBUG][back-yard-cam] flushing audio

mrlt8 added a commit that referenced this issue May 7, 2024
@mrlt8
Copy link
Owner

mrlt8 commented May 7, 2024

@widapro Does it work if you disable the audio?
Your first log showed [Exception] Unable to identify audio. but your second log shows that it was able to identify it..?

Can you try the latest build to see if it's able to identify the audio more consistently?

@1fastt2 if you're using a docker-compose.yml, you can edit the image tag to dev:

    image: mrlt8/wyze-bridge:dev

You can pull new images by running these commands:

docker-compose pull # Pull new image
docker-compose up -d # Restart container in detached mode
docker image prune # Remove old images

or if using docker run:

docker run -p 8554:8554 -p 8888:8888 -p 5000:5000 mrlt8/wyze-bridge:dev

@towerrh
Copy link
Author

towerrh commented May 7, 2024

This is what I am currently seeing... Like i said, the v3 looks fine. The v4... After the dev upload, still nothing.

[WyzeBridge] Press CTRL+C to quit [WyzeBridge] [+] Adding My room [WYZE_CAKP2JFUS] [WyzeBridge] starting MediaMTX 1.1.1 [WyzeBridge] 🎬 2 streams enabled [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor grow room on 192.168.1.200 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - My room on 192.168.1.186 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - My room on 192.168.1.186 [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET / HTTP/1.1" 200 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /static/bulma.css HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /static/site.css HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /static/bulma-toast.js HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /static/site.js HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /img/my-room.jpg HTTP/1.1" 200 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /img/indoor-grow-room.jpg HTTP/1.1" 200 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /img/indoor-grow-room.jpg HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /img/my-room.jpg HTTP/1.1" 304 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:04] "GET /api/sse_status HTTP/1.1" 200 - [indoor-grow-room] 📡 Getting 180kb/s 2K stream (H264/10fps) via LAN mode (WiFi: 70%) FW: 4.52.3.9455 🔒 [indoor-grow-room] 🔊 Audio Enabled - AAC_ELD/16,000Hz [my-room] 📡 Getting 180kb/s HD stream (H264/15fps) via LAN mode (WiFi: 98%) FW: 4.36.11.8391 🔒 [my-room] 🔊 Audio Enabled - ALAW/16,000Hz [indoor-grow-room] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [my-room] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [WyzeBridge] ✅ '/my-room stream is UP! (3/3) [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... [WyzeBridge] [API] Fetched [2] cameras [WyzeBridge] 💾 Saving 'cameras' to local cache... [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:09] "GET /snapshot/indoor-grow-room.jpg?1715051166147 HTTP/1.1" 200 - [WyzeBridge] 192.168.1.155 - - [06/May/2024 22:06:09] "GET /snapshot/indoor-grow-room.jpg?1715051166147 HTTP/1.1" 304 -

@mrlt8
Copy link
Owner

mrlt8 commented May 7, 2024

It looks like it's correctly identifying the audio now:

[indoor-grow-room] 🔊 Audio Enabled - AAC_ELD/16,000Hz

does it eventually connect? the skipping wrong frame size is normal when connecting to the camera:

 [indoor-grow-room] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] 

Try setting ON_DEMAND=False to see if that will help maintain the connection?

@towerrh
Copy link
Author

towerrh commented May 7, 2024

I currently have On_Demand=False enabled, aswell as RTSP60. The v3 is updating the screenshot as expected and is being seen (although, rstp is no longer working either) but I am not getting a screenshot or live feed on the v4 aka indoor-grow-room

@towerrh
Copy link
Author

towerrh commented May 7, 2024

Capture2

I am currently use Unraid, Docker.

@towerrh
Copy link
Author

towerrh commented May 7, 2024

Here is what it looks like on my side,
I am getting a snapshot that is pretty old. Left is v4. Right is v3.

Capture

@mrlt8
Copy link
Owner

mrlt8 commented May 7, 2024

Sorry, I'm not sure if I understand the issue. It looks like the cameras are connecting as expected.

Is it just the snapshot not updating in the WebUI? can you manually refresh it with the green rotate icon?

@towerrh
Copy link
Author

towerrh commented May 7, 2024

Im so sorry, I know this looks confusing. Although the cameras are showing connecting, I am not able to get a snapshot (updated). Its not respecting the parameters, either. Also, selecting the green rotate icon does nothing. If I power cycle the camera (v4) I can get a snapshot as you see above. But, I have to unplug the camera and plug it back in.

@towerrh
Copy link
Author

towerrh commented May 7, 2024

I am also not getting a video on it either, it just spins.

@towerrh
Copy link
Author

towerrh commented May 7, 2024

Looking over these logs, what happens to the indoor grow room? It dissapears after attempting to connect?

@towerrh
Copy link
Author

towerrh commented May 7, 2024

Capture

@mrlt8
Copy link
Owner

mrlt8 commented May 8, 2024

@towerrh try setting ON_DEMAND=False. You may also want to use the WebRTC or HLS stream to monitor the streams instead of snapshots.

@towerrh
Copy link
Author

towerrh commented May 8, 2024

Please see my unraid screen shot above with the parameters.

I have tried webrtc and hls to no result. Works fine on the v3 camera but does not on the v4.

@towerrh
Copy link
Author

towerrh commented May 9, 2024

I seem to have discovered part of the issue at least with the snapshots....

I am still not able to get rotating snapshots. But I have discovered if a event occurs on wyze the camera will snapshot the event. That even then seems to update on the wyze bridge snapshot. But only seems to happen 'on event' rather than respecting the 'SNAPSHOT' and 'ON DEMAND' parameters.

mrlt8 added a commit that referenced this issue May 12, 2024
* Sign motion event request #1125

* use device id instead of mac #1125

* remove wrong flags from mkfifo #1174

* less aggressive flush #1159 #1167

* Use K10052 for setting FPS #1161

* Refactor bits for going above 255 for quality

* Revert ffmpeg changes #1159 #1167

* version is obsolete

* default quality to hd180

* Update Wyze iOS App version from v2.44.5.3 to v2.50.6.1 (#1176)

* use struct pack

* Token based auth over the webUI

* Fix redirect for Home Assistant Ingress

* Use request headers to fix redirect for HA

* Change GET to POST for webhooks data

* Deprecate ifttt_webhook in favor of webhooks

* use yml for HA config and make credentials optional

* keep trying to identify audio #1172

* Snapshot on motion and push to mqtt #709 #970

* Add event time to motion message

* refactor auth

* EVENT_API option #1125

* Add additional headers  #1125

* Audio sync with higher bitrate

* Debug api request #1125

* Update api.py

* only debug on error

* Tweak audio sync

* don't raise error on lost frame

* clear buffer if out of sync

* Unique macs only #1125

Co-Authored-By: Cameron <32912464+kiwi-cam@users.noreply.github.com>

* Require auth by default and block non-ingress access #1181

* Allow non-ingress access with auth #1181

* Remove retain flag from commands #1182

* update webrtc to work with auth streams

* Add WB_API and rename WEB to WB #1181

WEB_USERNAME > WB_USERNAME
WEB_PASSWORD > WB_PASSWORD

* HA move /config/wyze-bridge/ to /config/

* Don't notify substream event and remove v2 #1125

* WebUI Auth related config for HA

* Don't retain discovery message? #1182

* Case sensitive credentials for WebUI

* changelog and readme

---------

Co-authored-by: Cameron <32912464+kiwi-cam@users.noreply.github.com>
@widapro
Copy link

widapro commented May 13, 2024

Thank you mrlt8, V4 camera now works on Wyze_bridge v2.9.1 but only with ENABLE_AUDIO=false or at all without ENABLE_AUDIO env parameter. When I enabled the audio, the stream in VLC never started and in Wyze_bridge logs I have the following lines:

15:49:21 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-4.924490213394165 15:49:21 [DEBUG][back-yard-cam] flushing audio 15:49:21 [DEBUG][back-yard-cam] [audio] out of sync gap=-5.490377187728882 15:49:21 [WARNING][back-yard-cam] WARNING: clear buffer 15:49:21 [DEBUG][back-yard-cam] flushing audio 15:49:21 [DEBUG][back-yard-cam] sync camera time 15:49:21 [DEBUG][back-yard-cam] Now listening on channel id 0 15:49:21 [DEBUG][back-yard-cam] SEND <K10092SetCameraTime code=10092 resp_code=10093> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10092 txt_len=4> b'\x816Bf' 15:49:21 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10093 txt_len=1>: b'\x01' 15:49:21 [DEBUG][back-yard-cam] No longer listening on channel id 0 15:49:22 [DEBUG][back-yard-cam] [CONTROL] Attempting to GET: bitrate 15:49:22 [DEBUG][back-yard-cam] Now listening on channel id 0 15:49:22 [DEBUG][back-yard-cam] SEND <K10050GetVideoParam code=10050 resp_code=10051> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10050 txt_len=0> b'' 15:49:22 [DEBUG][back-yard-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10051 txt_len=6>: b'\xb4\x00\x04\x14\x01\x01' 15:49:22 [DEBUG][back-yard-cam] No longer listening on channel id 0 15:49:22 [DEBUG][back-yard-cam] [CONTROL] response=180 15:49:24 [DEBUG][back-yard-cam] [audio] rushing ahead of video.. gap=-1.0136516094207764

@towerrh
Copy link
Author

towerrh commented May 15, 2024

I was able to resolve my issue sorta. The v4 for some reason will NOT work on unraid as a docker. So my homeassistant, I ran as a add on and worked perfectly. So i have no idea.

@towerrh towerrh closed this as completed May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants