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.47k stars 151 forks source link

Sub stream compatibility for Doorbell Cam WYZEDB3 #742

Open plewenson opened 1 year ago

plewenson commented 1 year ago

Great job on the development of this awesome app! I was excited to see you released the new 2.0 version today, so I updated my container to test out the new sub-stream functionality and wanted to report my experience.

While I was able to force the 2nd stream (since my firmware wasn't explicitly listed as supported) both streams seem to keep "rebooting" every few seconds.

Here's my setup:

Before updating, switching between HD,SD and 480P options in Wyze app didn't affect the stream in your bridge so I forced the 2nd stream with the new release env variable 'SUBSTREAM_FRONT_DOOR=True'.

However, when reviewing the restarted container in the web dashboard, the substream sometimes stutters and it seems both streams alternatively "reboot" every few seconds (i.e., I'm getting the "disconnected warning" on the webpage).

I did try restarting the camera from Wyze App and also tested the 'FORCE_ENCODE=true' but it did not make any difference.

Let me know if there's anything I can help test/debug.

1fastt2 commented 1 year ago

Sound like something possibly with the doorbell camera.

I'm running 3 V3 Pro's and 2 V3's through Blueiris running sub streams and everything seems to be working nicely. To note, I'm running the docker via HA.

How did you configure Blueiris? Blueiris will record both streams. It uses the sub-stream for remote viewing and motion detection however when viewing or reviewing recorded clips will display the main stream. You should not have to force the sub-stream.

I'm not sure if any othis this helps or not. I'm far from an expert at this.

dimmanramone commented 1 year ago

Sound like something possibly with the doorbell camera.

I'm running 3 V3 Pro's and 2 V3's through Blueiris running sub streams and everything seems to be working nicely. To note, I'm running the docker via HA.

How did you configure Blueiris? Blueiris will record both streams. It uses the sub-stream for remote viewing and motion detection however when viewing or reviewing recorded clips will display the main stream. You should not have to force the sub-stream.

I'm not sure if any othis this helps or not. I'm far from an expert at this.

@1fastt2 I have two v3 but my substream is not working. How did you configured it? Which firmware version are your cameras running?

plewenson commented 1 year ago

@1fastt2 I believe it's related to the resolution that's being requested when provisioning the substream for the doorbell camera.

In my logs, I can see the following errors: [front-door-sub] 📡 Getting 30kb/s SD stream (H264/20fps) via LAN mode (WiFi: 78%) FW: 4.25.1.314 🔒 (DTLS) (2/3) [front-door-sub] WARNING: Wrong resolution (frame_size=3) Requesting frame_size=1 and bitrate=30

..and also this: [front-door-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE

1fastt2 commented 1 year ago

Sound like something possibly with the doorbell camera. I'm running 3 V3 Pro's and 2 V3's through Blueiris running sub streams and everything seems to be working nicely. To note, I'm running the docker via HA. How did you configure Blueiris? Blueiris will record both streams. It uses the sub-stream for remote viewing and motion detection however when viewing or reviewing recorded clips will display the main stream. You should not have to force the sub-stream. I'm not sure if any othis this helps or not. I'm far from an expert at this.

@1fastt2 I have two v3 but my substream is not working. How did you configured it? Which firmware version are your cameras running?

I’m running the most recent Wyze firmware.

Here is my configuration for one of the cams running subs. FCF59CE9-91C9-4B34-A55D-634EFA107A2E

1fastt2 commented 1 year ago

@1fastt2 I believe it's related to the resolution that's being requested when provisioning the substream for the doorbell camera.

In my logs, I can see the following errors: [front-door-sub] 📡 Getting 30kb/s SD stream (H264/20fps) via LAN mode (WiFi: 78%) FW: 4.25.1.314 🔒 (DTLS) (2/3) [front-door-sub] WARNING: Wrong resolution (frame_size=3) Requesting frame_size=1 and bitrate=30

..and also this: [front-door-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE

That may be specific to the door bell cam. The native resolution I have the cameras set at in the Wyze app makes no difference to the streaming profile. Unfortunately, I have not seen that error in my set up. You may want to reset all of your parameters back to default and try again. 🤷🏼‍♂️

mrlt8 commented 1 year ago

You'd typically see something like this if you try to access both streams at the same time and the firmware doesn't support multiple streams:

wyze-bridge  | Requesting frame_size=0 and bitrate=180
wyze-bridge  | Requesting frame_size=1 and bitrate=30
wyze-bridge  | Requesting frame_size=0 and bitrate=180
wyze-bridge  | Requesting frame_size=1 and bitrate=30
wyze-bridge  | Requesting frame_size=0 and bitrate=180

@plewenson Can you access front-door and front-door-sub individually?

plewenson commented 1 year ago

@mrlt8 Hi, yes, I can access them individually, but as soon as I try to access them both simultaneously, they start to compete with each other and randomly start/stop the streams. So, I gather the doorbell cam doesn't support the substream functionality?

I've attached my log in case you see something of interest and I can help in any way...

_wyze-bridge_logs-5.txt

dimmanramone commented 1 year ago

Sound like something possibly with the doorbell camera. I'm running 3 V3 Pro's and 2 V3's through Blueiris running sub streams and everything seems to be working nicely. To note, I'm running the docker via HA. How did you configure Blueiris? Blueiris will record both streams. It uses the sub-stream for remote viewing and motion detection however when viewing or reviewing recorded clips will display the main stream. You should not have to force the sub-stream. I'm not sure if any othis this helps or not. I'm far from an expert at this.

@1fastt2 I have two v3 but my substream is not working. How did you configured it? Which firmware version are your cameras running?

I’m running the most recent Wyze firmware.

Here is my configuration for one of the cams running subs. FCF59CE9-91C9-4B34-A55D-634EFA107A2E

Did you configured them globally with SUBSTREAM=True or every cam separately with SUBSTREAM_CAM_NAME=True ?

EDIT: Setting them up separately seems to work

1fastt2 commented 1 year ago

Did you configured them globally with SUBSTREAM=True or every cam separately with SUBSTREAM_CAM_NAME=True ?

EDIT: Setting them up separately seems to work

I have them globally set up.

mrlt8 commented 1 year ago

Thanks for the logs @plewenson! The doorbell typically uses 3 and 4 as the frame sizes for the HD and SD streams, but I noticed some weird entries in your logs:

[front-door-sub] WARNING: Skipping smaller frame at start of stream (frame_size=12)
...
[front-door] WARNING: Skipping smaller frame at start of stream (frame_size=11)

Not really sure what is going on here. I'll have to look into the app to see if the doorbell might be using some other frame_sizes.

I know you mentioned that you were previously able to switch resolutions in the app without affecting the stream in the bridge. Do you think you could try that again with a single stream in the bridge and switching between the HD and 360p stream in the app to see if you get any similar messages in the logs?

plewenson commented 1 year ago

@mrlt8 Sure thing... See attached. I restarted the container so we have isolated logs. I used VLC to first test the HD stream while simultaneously switching resolutions in the Wyze app from my iPhone (from HD to SD to 480p, etc.). The VLC resolution never changed and stayed hi-res. Same procedure for testing the substream feed. Feed in VLC didn't change.

I know you mentioned 360P as the substream from the other cameras, but is there a difference with the 480P lo-res feed from the doorbell cam with your implementation of substreams? _wyze-bridge_logs.txt

mrlt8 commented 1 year ago

Thanks! I'll have to look check the app again to see if we're missing something for the doorbell connection. But your test seems to confirm that it should be possible to have multiple streams at the same time.

I believe all cameras after the v1 have a low and high stream. The "SD" stream is usually just the high stream with a lower bitrate.

plewenson commented 1 year ago

Just to make sure we're on the same page, I took screenshots of the same embedded watermark in both the iPhone app and in my BlueIris NVR to confirm they're two different resolutions (as noted by the pixelization of the Wyze timestamp).

BlueIris HD Wyze Cam 480p

gtxaspec commented 11 months ago

@mrlt8 any progress on this?

[doorbell-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
[doorbell] 📡 Getting 255kb/s HD stream (H264/20fps) via LAN mode (WiFi: 66%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
[doorbell] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
[doorbell] 📹 Will record 60s mp4 clips to /record/doorbell/
[doorbell] WARNING: Skipping smaller frame at start of stream (frame_size=4)
[WyzeBridge] ❌ '/doorbell-sub' stream is down
[WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 10.x
[WyzeBridge] ✅ '/doorbell stream is UP! (3/3)
[doorbell] WARNING: AV_ER_SESSION_CLOSE_BY_REMOTE
[doorbell] WARNING: Audio pipe closed
[doorbell] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
[doorbell-sub] 📡 Getting 255kb/s SD stream (H264/20fps) via LAN mode (WiFi: 65%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
[doorbell-sub] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
[WyzeBridge] ❌ '/doorbell' stream is down
[WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 10.x
[doorbell-sub] WARNING: Wrong resolution (frame_size=3)
Requesting frame_size=1 and bitrate=255
[doorbell-sub] WARNING: Skipping smaller frame at start of stream (frame_size=3)
[WyzeBridge] ✅ '/doorbell-sub stream is UP! (3/3)
[doorbell-sub] WARNING: AV_ER_SESSION_CLOSE_BY_REMOTE
[doorbell-sub] WARNING: Audio pipe closed
[WyzeBridge] ❌ '/doorbell-sub' stream is down
[doorbell] 📡 Getting 255kb/s HD stream (H264/20fps) via LAN mode (WiFi: 65%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
[doorbell] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
[doorbell] 📹 Will record 60s mp4 clips to /record/doorbell/
[doorbell] WARNING: Skipping smaller frame at start of stream (frame_size=4)
[doorbell] WARNING: Skipping smaller frame at start of stream (frame_size=11)
[doorbell-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
[WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 10.x
[WyzeBridge] ✅ '/doorbell stream is UP! (3/3)
[doorbell] WARNING: AV_ER_SESSION_CLOSE_BY_REMOTE
[doorbell] WARNING: Audio pipe closed
[doorbell-sub] 📡 Getting 255kb/s SD stream (H264/20fps) via LAN mode (WiFi: 66%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
[doorbell-sub] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
[doorbell-sub] WARNING: Wrong resolution (frame_size=3)
Requesting frame_size=1 and bitrate=255
[WyzeBridge] ❌ '/doorbell' stream is down
[doorbell-sub] WARNING: Skipping smaller frame at start of stream (frame_size=3)
[doorbell] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE

When using the DB3, with MAIN and SUB stream.
If SUB is disabled, then MAIN works ok. If both are enabled, MAIN never works, SUB works for a while, then it reconnects, and works for a bit again until it cycles.

wyze-bridge  | [doorbell-sub] WARNING: AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | [doorbell-sub] WARNING: Audio pipe closed
wyze-bridge  | [WyzeBridge] ✅ '/doorbell-sub stream is UP! (3/3)
wyze-bridge  | [doorbell-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | [doorbell] 📡 Getting 255kb/s HD stream (H264/20fps) via LAN mode (WiFi: 56%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
wyze-bridge  | [doorbell] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
wyze-bridge  | [doorbell] 📹 Will record 60s mp4 clips to /record/doorbell/
wyze-bridge  | [doorbell] WARNING: Skipping smaller frame at start of stream (frame_size=4)
wyze-bridge  | [WyzeBridge] ❌ '/doorbell-sub' stream is down
wyze-bridge  | [WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 10.x
wyze-bridge  | [WyzeBridge] ✅ '/doorbell stream is UP! (3/3)
wyze-bridge  | [doorbell] WARNING: AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | [doorbell] WARNING: Audio pipe closed
wyze-bridge  | [WyzeBridge] ❌ '/doorbell' stream is down
wyze-bridge  | [doorbell] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | [doorbell-sub] 📡 Getting 255kb/s SD stream (H264/20fps) via LAN mode (WiFi: 57%) FW: 4.25.1.315 🔒 (DTLS) (2/3)
wyze-bridge  | [doorbell-sub] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
wyze-bridge  | [doorbell-sub] WARNING: Wrong resolution (frame_size=3)
wyze-bridge  | Requesting frame_size=1 and bitrate=255
wyze-bridge  | [doorbell-sub] WARNING: Skipping smaller frame at start of stream (frame_size=3)
mrlt8 commented 11 months ago

Still need to look into this. I believe we're using a different tutk message (K10052 vs K10056) to adjust the frame size/bitrate for the doorbell and outdoor cams. I wonder if that could potentially be causing the issue?

mrlt8 commented 11 months ago

Ok, so after some more debugging, it seems like using the old authentication method K10002ConnectAuth is the limiting factor.

Most of the other cameras use the newer K10008ConnectUserAuth, however, it seems like the v1, doorbell, and outdoor cams don't support K10008. There seems to be another authentication method K10006 that supports a substream, but it is marked as deprecated for some reason.

Could someone try the dev branch to see if the doorbell supports K10006?

gtxaspec commented 11 months ago

no dice yet:

wyze-bridge  | 21:11:51 [WARNING][WyzeBridge] WARNING: invalid escape sequence '\d'
wyze-bridge  | 21:11:51 [WARNING][WyzeBridge] WARNING: invalid escape sequence '\w'
wyze-bridge  | 
wyze-bridge  | 🚀 DOCKER-WYZE-BRIDGE v2.3.10 [LOCAL BUILD]
wyze-bridge  | 
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] ♻️ Clearing local cache...
wyze-bridge  | 
wyze-bridge  | 21:11:51 [DEBUG][WyzeBridge] Using xx for webrtc
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] 🔍 Could not find local cache for 'auth'
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
wyze-bridge  |  * Serving Flask app 'frontend'
wyze-bridge  |  * Debug mode: off
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
wyze-bridge  |  * Running on all addresses (0.0.0.0)
wyze-bridge  |  * Running on http://127.0.0.1:5000
wyze-bridge  |  * Running on http://172.26.0.2:5000
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] Press CTRL+C to quit
wyze-bridge  | 21:11:51 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): auth-prod.api.wyze.com:443
wyze-bridge  | 21:11:51 [DEBUG][WyzeBridge] https://auth-prod.api.wyze.com:443 "POST /api/user/login HTTP/1.1" 200 None
wyze-bridge  | 21:11:51 [WARNING][WyzeBridge] WARNING: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:11:51 [WARNING][WyzeBridge] WARNING: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] 💾 Saving 'auth' to local cache...
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] 🔍 Could not find local cache for 'user'
wyze-bridge  | 21:11:51 [INFO][WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
wyze-bridge  | 21:11:51 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 21:11:52 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/user/get_user_info HTTP/1.1" 200 240
wyze-bridge  | 21:11:52 [WARNING][WyzeBridge] WARNING: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:11:52 [WARNING][WyzeBridge] WARNING: The `parse_obj` method is deprecated; use `model_validate` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:11:52 [INFO][WyzeBridge] 💾 Saving 'user' to local cache...
wyze-bridge  | 21:11:52 [INFO][WyzeBridge] 🔍 Could not find local cache for 'cameras'
wyze-bridge  | 21:11:52 [INFO][WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
wyze-bridge  | 21:11:52 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 21:11:53 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/v2/home_page/get_object_list HTTP/1.1" 200 35734
wyze-bridge  | 21:11:53 [INFO][WyzeBridge] 💾 Saving 'cameras' to local cache...
wyze-bridge  | 21:11:53 [INFO][WyzeBridge] 🪄 FILTER ALLOWING: 1 of 20 cams
wyze-bridge  | 21:11:53 [INFO][WyzeBridge] [+] Adding Doorbell [WYZEDB3]
wyze-bridge  | 21:11:53 [ERROR][WyzeBridge] Doorbell may not support multiple streams!!
wyze-bridge  | 21:11:53 [INFO][WyzeBridge] starting MediaMTX 0.23.7
wyze-bridge  | 21:11:53 [INFO][WyzeBridge] 🎬 2 streams enabled
wyze-bridge  | 21:11:54 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:11:54 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:11:54 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:11:54 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:11:55 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:11:55 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:11:55 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:11:55 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03\x9f\x17+\x03\xbd\xce\x93\xe3!\xd4\xa4\xbc\xf5\xab\xff,'
wyze-bridge  | 21:11:55 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03h $T#n\x1f\xe3\x9cg\xd6\x9d?.\x189'
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\xcaZ\x8cp\x95\x91)\x89\x7f\xd7\xd6\x8d\xa6\xe0\x91{9d85\x01\x01\x071743586'
wyze-bridge  | 21:11:55 [DEBUG][doorbell] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:11:55 [DEBUG][doorbell] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\xab\x97\xbc3m\x8a@\x06\x8fH\x0c\x04\xf5\xf9\x1b|119d\x01\x01\x071743586'
wyze-bridge  | 21:11:55 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:11:55 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:12:14 [WARNING][WyzeBridge] ⏰ Timed out connecting to Doorbell.
wyze-bridge  | 21:12:14 [WARNING][WyzeBridge] ⏰ Timed out connecting to Doorbell.
wyze-bridge  | 21:12:15 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:15 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:15 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:15 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:16 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:16 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:16 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:16 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:16 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03\xf08\x9d\x1c\x12\x98\xa6\xce\xfb1\x02\xeb\xb7 <x'
wyze-bridge  | 21:12:16 [DEBUG][doorbell] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:12:16 [DEBUG][doorbell] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\xd0\xfd\xed\xb7X\x17|\xe9\xe7\x02HCt*ZJ119d\x01\x01\x071743586'
wyze-bridge  | 21:12:16 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03<\xc1\xb5\xc9\x9d\xd78\xf7cl\x99\x14\x9ds\x18\xa0'
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\x97a\xe9U-\x90\xde\xceY\x80\xec$\xff\xac\xb6O9d85\x01\x01\x071743586'
wyze-bridge  | 21:12:16 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:12:27 [WARNING][WyzeBridge] WARNING: The `dict` method is deprecated; use `model_dump` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:12:27 [WARNING][WyzeBridge] WARNING: The `dict` method is deprecated; use `model_dump` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:12:27 [WARNING][WyzeBridge] WARNING: The `dict` method is deprecated; use `model_dump` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:12:27 [WARNING][WyzeBridge] WARNING: The `dict` method is deprecated; use `model_dump` instead. Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.0.3/migration/
wyze-bridge  | 21:12:27 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:27] "GET / HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/loading.svg HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/site.js HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/webrtc.js HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/site.css HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /api/sse_status HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] ☁️ Pulling "doorbell" thumbnail to /img/doorbell.jpg
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /img/doorbell-sub.jpg HTTP/1.1" 307 -
wyze-bridge  | 21:12:28 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): wyze-device-alarm-file-face.s3.us-west-2.amazonaws.com:443
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/notavailable.svg HTTP/1.1" 200 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /img/doorbell-sub.jpg HTTP/1.1" 307 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /static/notavailable.svg HTTP/1.1" 304 -
wyze-bridge  | 21:12:28 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:28] "GET /favicon.ico HTTP/1.1" 404 -
wyze-bridge  | 21:12:28 [DEBUG][WyzeBridge] https://wyze-device-alarm-file-face.s3.us-west-2.amazonaws.com:443 "GET /7C78B216A3DC/2023-07-15/7C78B216A3DC131689408614_1689408614000_10_1_0/6114bd2921af42fba6066423177f7246_-1.jpg?X-Amz-Expires=1200&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJNFQFXEM46KZVY7A/20230716/us-west-2/s3/aws4_request&X-Amz-Date=20230716T041147Z&X-Amz-SignedHeaders=host&X-Amz-Signature=d68afb10d5d15072b848fa7eb1007a8736fdca71e3cc99b06b6d12cb0a10860b HTTP/1.1" 200 71723
wyze-bridge  | 21:12:29 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:29] "GET /img/doorbell.jpg HTTP/1.1" 200 -
wyze-bridge  | 21:12:29 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:29] "GET /img/doorbell.jpg HTTP/1.1" 304 -
wyze-bridge  | 21:12:32 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:32] "GET /signaling/doorbell?webrtc HTTP/1.1" 200 -
wyze-bridge  | 21:12:35 [WARNING][WyzeBridge] ⏰ Timed out connecting to Doorbell.
wyze-bridge  | 21:12:35 [WARNING][WyzeBridge] ⏰ Timed out connecting to Doorbell.
wyze-bridge  | 21:12:36 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:36 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:36 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:36 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:37 [WARNING][doorbell-sub] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | 21:12:37 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:37 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:37 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:37 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x076\x07\xeek#Q0\x18*\xb0e\x80j\xe7\x153'
wyze-bridge  | 21:12:37 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:37 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:37 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:12:38 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:38 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:39 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:39 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:12:39 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:39 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\xf6::\xaf\xb5k2\x9a>\x96I\xceC~\x85\x81'
wyze-bridge  | 21:12:39 [WARNING][doorbell-sub] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:39 [WARNING][doorbell-sub] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:39 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:39 [WARNING][doorbell-sub] AUTH_FAILED
wyze-bridge  | 21:12:39 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:40 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:40 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:40 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:40 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\xa6l\xcf1\xd6.\xc5TI\x04!\xc02*\xf6j'
wyze-bridge  | 21:12:40 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:40 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:40 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:12:41 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:41 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:41 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:41 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:42 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:42 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:12:42 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:42 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\x9f\x1f\xc1m\xc2\x97RU\xbdg\xc3\xa7r~xI'
wyze-bridge  | 21:12:42 [WARNING][doorbell-sub] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:42 [WARNING][doorbell-sub] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:42 [WARNING][doorbell-sub] AUTH_FAILED
wyze-bridge  | 21:12:43 [WARNING][doorbell] [-20015] AV_ER_SESSION_CLOSE_BY_REMOTE
wyze-bridge  | 21:12:43 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:44 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:44 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:44 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:12:44 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:44 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07M\xfa:QEaU \xf8\xca7\xfc\x1d\xe7\x0c\x9d'
wyze-bridge  | 21:12:44 [WARNING][doorbell-sub] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:44 [WARNING][doorbell-sub] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:44 [WARNING][doorbell-sub] AUTH_FAILED
wyze-bridge  | 21:12:45 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:45 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:45 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:45 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:45 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:45 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03\xdc\x85\xc5\xa8\xdb\xe0\x1am\x08\xe5\xce\xe7\xe8GlK'
wyze-bridge  | 21:12:45 [DEBUG][doorbell] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:12:45 [DEBUG][doorbell] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\xee\xab\x11\xd02X\xd4\xc1\x8d\xfb\x01\x07\xcb\x80\xaa9119d\x01\x01\x071743586'
wyze-bridge  | 21:12:45 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:12:46 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:46 [INFO][doorbell-sub] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] Now listening on channel id 0
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x03C\xb8\xaa\xff9\xa8\xed\x82CxNr\xe3`\xfal'
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] Sending response: <K10006ConnectUserAuth code=10006 resp_code=10007>
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] SEND <K10006ConnectUserAuth code=10006 resp_code=10007> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10006 txt_len=30> b'\xb3J\xf6N\x86!\xf5\x99\x1bH\xe1]\x180\x7f\x1e9d85\x01\x01\x071743586'
wyze-bridge  | 21:12:46 [DEBUG][doorbell-sub] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=1 txt_len=2>: b"\x16'"
wyze-bridge  | 21:12:49 [INFO][WyzeBridge] [CONTROL] SET doorbell state=disable
wyze-bridge  | 21:12:49 [INFO][WyzeBridge] Disabling doorbell
wyze-bridge  | 21:12:49 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:49] "GET /api/doorbell/state/disable HTTP/1.1" 200 -
wyze-bridge  | 21:12:50 [INFO][WyzeBridge] [CONTROL] SET doorbell state=stop
wyze-bridge  | 21:12:50 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:50] "GET /api/doorbell/state/stop HTTP/1.1" 200 -
wyze-bridge  | 21:12:51 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:51 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:51 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:51 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:51 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:51 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\x98\x01\x007\x96\xe7\xb4$\xd1ZL\xf8\xf4z~g'
wyze-bridge  | 21:12:51 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:51 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:52 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:12:54 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:54 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:54 [INFO][WyzeBridge] 192.168.1.3 - - [15/Jul/2023 21:12:54] "GET /signaling/doorbell-sub?webrtc HTTP/1.1" 200 -
wyze-bridge  | 21:12:54 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:54 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:54 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:54 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07j\xc2\xcah\xe5\xd6\xa7\xa8EA5\xda\xa3B\x15\xb5'
wyze-bridge  | 21:12:54 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:54 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:54 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:12:56 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:56 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:56 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:56 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:56 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:57 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\xc4\x1c\x86KWu35"lq\n\x10\x11@\xf8'
wyze-bridge  | 21:12:57 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:57 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:57 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:12:58 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:12:58 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:12:58 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:12:58 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:12:58 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:12:58 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07\xd4\x94\x14\xe1+\x9a\xc4Y\x91\xce.W\xed\x0f\x07\x87'
wyze-bridge  | 21:12:58 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:12:58 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:12:59 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:13:00 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:13:00 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 21:13:00 [INFO][doorbell] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 21:13:00 [DEBUG][doorbell] Now listening on channel id 0
wyze-bridge  | 21:13:00 [DEBUG][doorbell] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 21:13:01 [DEBUG][doorbell] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=11 code=10001 txt_len=17>: b'\x07l\xb3y^V\x9e\n\xb4\xffK\x9a\xbd\x0f \xda\xeb'
wyze-bridge  | 21:13:01 [WARNING][doorbell] Unexpected mode for connect challenge response (10001): 7
wyze-bridge  | 21:13:01 [WARNING][doorbell] Connection closed by remote. Closing connection.
wyze-bridge  | 21:13:01 [WARNING][doorbell] AUTH_FAILED
wyze-bridge  | 21:13:03 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Doorbell on 192.168.1.2
wyze-bridge  | 21:13:03 [DEBUG][doorbell] Connect via IOTC_Connect_ByUIDEx
mrlt8 commented 11 months ago

Thank you, will keep digging!

tdashmike commented 6 months ago

Is there any progress on this issue? I enabled the sub stream but it won't load.

[doorbell] 📡 Getting 180kb/s HD stream (H264/20fps) via LAN mode (WiFi: 93%) FW: 4.25.1.316 🔒 (DTLS) (2/3)
[doorbell] 🔊 Audio Enabled - PCM > LIBOPUS/8,000Hz
[doorbell] WARNING: Skipping smaller frame at start of stream (frame_size=4)
Bosswaffle commented 6 months ago

@tdashmike I'm experiencing the same issue, no substream will start for my doorbellv1