-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Comments
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. |
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. |
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:
On the wyze app I can connect to the camera without problems. |
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. |
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-
the camera thumbnail pulls one dated 9-27 but no current video.
my docker-compose.yml:
I tried the same thing with no configuration, but same results.
The text was updated successfully, but these errors were encountered: