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

Cannot connect to WyzeCam V2 since September 27 #1367

Open
alexplatform opened this issue Oct 2, 2024 · 4 comments
Open

Cannot connect to WyzeCam V2 since September 27 #1367

alexplatform opened this issue Oct 2, 2024 · 4 comments

Comments

@alexplatform
Copy link

alexplatform commented Oct 2, 2024

Something changed(?) last week and for the life of me I cant get video from my camera. I downgraded to 2.9.12, 2.10.3, and the behavior is always the same-

🚀 DOCKER-WYZE-BRIDGE v2.9.12 X86_64

[WyzeBridge] 🔍 Could not find local cache for 'auth'
[WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
 * 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.21.0.2:5000
[WyzeBridge] Press CTRL+C to quit
[WyzeBridge] 💾 Saving 'auth' to local cache...
[WyzeBridge] 🔍 Could not find local cache for 'user'
[WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
[WyzeBridge] 💾 Saving 'user' to local cache...
[WyzeBridge] 🔍 Could not find local cache for 'cameras'
[WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
[WyzeBridge] [API] Fetched [2] cameras
[WyzeBridge] 💾 Saving 'cameras' to local cache...
[WyzeBridge] 🪄 FILTER BLOCKING: 1 of 2 cams
[WyzeBridge] [+] Adding geyser front yard [WYZEC1-JZ]
[WyzeBridge] starting MediaMTX 1.1.1
[WyzeBridge] 🎬 1 stream enabled
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:29:30] "GET /api/sse_status HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - geyser front yard on 172.31.0.106
[geyser-front-yard] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - geyser front yard on 172.31.0.106
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:03] "GET / HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /static/site.js HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /static/loading.svg HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /static/bulma.css HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /static/site.css HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /static/bulma-toast.js HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:04] "GET /api/sse_status HTTP/1.1" 200 -
[WyzeBridge] ☁️ Pulling "geyser-front-yard" thumbnail to /img/geyser-front-yard.jpg
[WyzeBridge] ☁️ Pulling "geyser-front-yard" thumbnail to /img/geyser-front-yard.jpg
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:05] "GET /img/geyser-front-yard.jpg HTTP/1.1" 200 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:05] "GET /img/geyser-front-yard.jpg HTTP/1.1" 304 -
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:05] "GET /snapshot/geyser-front-yard.jpg?1727908201656 HTTP/1.1" 200 -
[geyser-front-yard] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - geyser front yard on 172.31.0.106
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:34] "GET /snapshot/geyser-front-yard.jpg?1727908235498 HTTP/1.1" 200 -
[WyzeBridge] [geyser-front-yard] Snapshot timed out
[WyzeBridge] 192.168.10.102 - - [02/Oct/2024 22:30:49] "GET /snapshot/geyser-front-yard.jpg?1727908235498 HTTP/1.1" 304 -
[geyser-front-yard] [-13] IOTC_ER_TIMEOUT

the camera thumbnail pulls one dated 9-27 but no current video.

my docker-compose.yml:

version: '2.4'
services:
    wyze-bridge:
        container_name: wyze-bridge
        restart: unless-stopped
        image: mrlt8/wyze-bridge:2.9.12
#        volumes:
            #- /config/wyze-bridge/mfa_token.txt:/tokens/totp
        ports:
            - 1935:1935 # RTMP
            - 8554:8554 # RTSP
            - 8888:8888 # HLS
            - 8889:8889 #WebRTC
            - 8189:8189/udp # WebRTC/ICE
            - 5000:5000 # WEB-UI
        environment:
            # [OPTIONAL] (Can be set in the WebUI):
            - WYZE_EMAIL=redacted
            - WYZE_PASSWORD= redacted
#           - TOTP_KEY=redacted
            # [OPTIONAL] IP Address of the host to enable WebRTC e.g.,:
            # [OPTIONAL] Wyze API credentials:
            - API_ID=redacted
            - API_KEY=redacted
            - WB_AUTH=False
            - FILTER_NAMES=Front Door
            - FILTER_BLOCK=true

I tried the same thing with no configuration, but same results.

@mrlt8
Copy link
Owner

mrlt8 commented Oct 3, 2024

Are the cameras on the same network as the bridge (can they ping each other)? I believe wyze was pushing some forced updates recently, and some of the newer firmware breaks remote connections so that only cameras on the same network are accessible.

@alexplatform
Copy link
Author

That was it! Thank you!

data point; now that I regained access visual quality is NOTICEABLY worse- although checking the Wyze app shows the same picture quality so not anything to do with wyze-bridge... looks like I will be looking for a different camera.

@teixeluis
Copy link

Same problem here, and both cameras are on the same network. The two cameras have the 4.36.13.0416 firmware. Running docker wyze bridge 2.10.3.

Whenever one of the cameras becomes unavailable in the bridge I get the following:

[south-cam] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - south-cam on 192.168.1.90
[south-cam] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - south-cam on 192.168.1.90

On the wyze app I can connect to the camera without problems.

@deCryptid
Copy link

deCryptid commented Oct 26, 2024

Yeah, hitting the same issue on my Pi 5. Everything is on the same network, the camera is running 4.52.8.0648 firmware. I can see it clear as day on Wyze but I get a single frame on the webUI and then get hit with the IOTC_ER_TIMEOUT. Odd thing is if I run Docker Desktop on my desktop, it works great. Weird one.

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