BUG: Bridge not connecting to Doorbell v1 cam

[mholl1983]

Describe the bug

As of today, I noticed Wyze Bridge doesn't seem to want to connect to any streams from our Doorbell v1 cam. Let me know if I can provide any further details that would help.

Affected Bridge Version

v2.10.3

Bridge type

Docker Run/Compose

Affected Camera(s)

Wyze Doorbell v1

Affected Camera Firmware

4.25.1.333

docker-compose or config (if applicable)

services:
    wyze-bridge:
        container_name: wyze-bridge
        restart: unless-stopped
        image: mrlt8/wyze-bridge:latest
        ports:
            - 1935:1935 # RTMP
            - 8554:8554 # RTSP
            - 8888:8888 # HLS
            - 8889:8889 #WebRTC
            - 8189:8189/udp # WebRTC/ICE
            - 5000:5000 # WEB-UI
        environment:
            # [OPTIONAL] Credentials can be set in the WebUI
            # API Key and ID can be obtained from the wyze dev portal: 
            # https://developer-api-console.wyze.com/#/apikey/view
            - WYZE_EMAIL=
            - WYZE_PASSWORD= 
            - API_ID=
            - API_KEY= 
            - ROTATE_CAM_BACK_DOOR=True
            # [OPTIONAL] IP Address of the host to enable WebRTC e.g.,:
            # - WB_IP=192.168.1.122
            # WebUI and Stream authentication:
            - WB_AUTH=False # Set to false to disable web and stream auth.
            # WB_USERNAME=
            # WB_PASSWORD=

[cheme75]

Yesterday I noticed HomeKit stopped displaying my orig db cam, checked scrypted and same. It’s now my only Wyze cam so got no others connected to compare where glitches originated. Anyway, saw a long list of failures to connect in docker log with a final error something to the effect of too many attempts to connect so blocked. I uncommented fresh data=true in yml, restarted bridge and all was ok again. I don’t check Wyze app much anymore so not sure if it was a Wyze glitch but intuition tells me Wyze glitch most likely.

[mholl1983]

Yesterday I noticed HomeKit stopped displaying my orig db cam, checked scrypted and same. It’s now my only Wyze cam so got no others connected to compare where glitches originated. Anyway, saw a long list of failures to connect in docker log with a final error something to the effect of too many attempts to connect so blocked. I uncommented fresh data=true in yml, restarted bridge and all was ok again. I don’t check Wyze app much anymore so not sure if it was a Wyze glitch but intuition tells me Wyze glitch most likely.

Interesting, thanks for sharing. I'm not sure if something changed on Wyze's end but I can see the feed again. I'll keep the fresh data flag in mind, though, thanks for letting me know about that, and glad yours is working again too!

[cheme75]

Yesterday I noticed HomeKit stopped displaying my orig db cam, checked scrypted and same. It’s now my only Wyze cam so got no others connected to compare where glitches originated. Anyway, saw a long list of failures to connect in docker log with a final error something to the effect of too many attempts to connect so blocked. I uncommented fresh data=true in yml, restarted bridge and all was ok again. I don’t check Wyze app much anymore so not sure if it was a Wyze glitch but intuition tells me Wyze glitch most likely.

Interesting, thanks for sharing. I'm not sure if something changed on Wyze's end but I can see the feed again. I'll keep the fresh data flag in mind, though, thanks for letting me know about that, and glad yours is working again too!

Fwiw, my normal instincts point to glitches originating from Wyze unless it’s new bridge release with something related to authentication. But when things run well for weeks or months, and then something goes wrong, I look for something Wyze related first.

Anyway, not sure the fresh data was necessary or not but figured it can’t hurt.