Client Stopped Reading From Camera

[krusej23]

Describe the bug

I have suddenly started having the issue where my wyze cam v4s won't show up in Frigate. I started to investigate and it looks like wyze docker bridge is having some trouble. The RTSP15 setting is working because the image is update in the bridge but the stream is not working over to Frigate. I am getting this error in Frigate. OpenCV(4.7.0) /io/opencv/modules/videoio/src/cap_images.cpp:253: error: (-5:Bad argument) CAP_IMAGES: can't find starting number (in the name of file): rtsp://192.168.86.42:554/sideyard?video=copy&audio=aac in function 'icvExtractPattern' frigate.video ERROR : sideyard: Unable to read frames from ffmpeg process. 2024-05-22 14:23:08.780298178 [2024-05-22 09:23:08] frigate.video ERROR : sideyard: ffmpeg process is not running. exiting capture thread... ffmpeg.sideyard.detect ERROR : [rtsp @ 0x5616d18892c0] method DESCRIBE failed: 401 Unauthorized 2024-05-22 14:23:28.780958321 [2024-05-22 09:23:28] ffmpeg.sideyard.detect ERROR : rtsp://192.168.86.42:554/sideyard?video=copy&audio=aac: Server returned 401 Unauthorized (authorization failed)

Environment (if applicable)

• Affected Camera(s): V4
• Affected Camera Firmware: Both 4.52.4.9887 and 4.52.3.9455
• Affected Bridge Version: 2.9.2
• Bridge type:
  • [X] Home Assistant

🚀 DOCKER-WYZE-BRIDGE v2.9.2 X86_64

[WyzeBridge] 📚 Using 'auth' from local cache... [WyzeBridge] 📚 Using 'user' from local cache... [WyzeBridge] 📚 Using 'cameras' from local cache... [WyzeBridge] [+] Adding Garage [WYZE_CAKP2JFUS]

• Serving Flask app 'frontend'
• Debug mode: off [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
• Running on all addresses (0.0.0.0)
• Running on http://127.0.0.1:5000
• Running on http://172.30.33.6:5000 [WyzeBridge] Press CTRL+C to quit [WyzeBridge] [+] Adding Sideyard [HL_CAM4] [WyzeBridge] [+] Adding Back Yard Cam [HL_CAM4] [WyzeBridge] starting MediaMTX 1.1.1 [WyzeBridge] 🎬 3 streams enabled [WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.86.227 [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Sideyard on 192.168.86.248 [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Back Yard Cam on 192.168.86.247 [garage] [-90] IOTC_ER_DEVICE_OFFLINE [WyzeBridge] 👻 Garage is offline. [WyzeBridge] Garage will cooldown for 10s. [back-yard-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 57%) FW: 4.52.4.9887 🔒 [back-yard-cam] Re-encoding audio for compatibility with WebRTC in MTX [back-yard-cam] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [sideyard] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 66%) FW: 4.52.4.9887 🔒 [sideyard] Re-encoding audio for compatibility with WebRTC in MTX [sideyard] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [back-yard-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [sideyard] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [WyzeBridge] ✅ '/back-yard-cam stream is UP! (3/3) [WyzeBridge] ✅ '/sideyard stream is UP! (3/3) [WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.86.227 [garage] [-90] IOTC_ER_DEVICE_OFFLINE [WyzeBridge] 👻 Garage is offline. [WyzeBridge] Garage will cooldown for 10s. [WyzeBridge] 📖 New client reading from sideyard [WyzeBridge] 📖 New client reading from back-yard-cam [WyzeBridge] 📕 Client stopped reading from back-yard-cam [WyzeBridge] 📕 Client stopped reading from sideyard

[mrlt8]

Looks like an authentication problem 401 Unauthorized Did it stop working after upgrading to 2.9.x?

Starting with v2.9.0, WB_AUTH will default to true, and enable authentication for both the web ui and streams.

The username for the stream is wb and the password should be unique API Key displayed at the bottom of your WebUI like this:

You can change the API key by setting the WB_API ENV variable.

If you're running the bridge 100% local, then you can probably set WB_AUTH=False to disable authentication and run it like it was before.

Please see the release log for more info: https://github.com/mrlt8/docker-wyze-bridge/releases/tag/v2.9.0

[krusej23]

I have both the Key ID and API Key codes put in the HA configuration page. I also had my Wyze email and password in there and it was working with that until the latest update I'm guessing. I can get it to work perfectly if I turn WebUI Auth off and restart but I'm guessing that isn't secure at all. I just tried removing my Wyze email and password from the top of the configuration page and putting them in the WebUI Username and Password fields under advanced options but that doesn't work either after turning WebUI Auth back on. What am I doing wrong? I read through the instructions on the Wiki but they are very confusing and jump back and forth and don't have a clear HA instructions page for the new way of authenticating. Thanks!

[mrlt8]

You'll need to update your frigate config to use the wb username and the api key from the web-ui like this:

rtsp://wb:<API key from the webui>@127.0.0.1:8554/<cam-name>