-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Camera streams and snapshots no longer work after 2.3.5 with any Wyze cameras #902
Comments
Do you have the camera data cached? Can you run the container with FRESH_DATA or clear the data from the webUI using the |
It looks like it, I still have snapshots showing on the cameras from over a week ago. The restart does not seem to work anymore either, I’m getting "Restart all - The string did not match the expected pattern.” For both "clear cache and reconnect" and "connection to cameras"
… On Jul 6, 2023, at 11:27 PM, mrlt8 ***@***.***> wrote:
Do you have the camera data cached? Can you run the container with FRESH_DATA or clear the data from the webUI using the /restart/all endpoint?
—
Reply to this email directly, view it on GitHub <#902 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABT5Z4JY2QSQQRZLY54PVMDXO6F3PANCNFSM6AAAAAA2BHH7UQ>.
You are receiving this because you authored the thread.
|
Just an update, I noticed this error in the logs when trying a restart and clear cache:
|
Can you post the version of the bridge you're using when getting that error? |
This is tested against 2.3.5+ with the error message there being from 2.3.10. |
Thanks @ZacTyAdams! The threading issue should be fixed in the next release. |
Perfect thank you @mrlt8, I'll test again with the next release and the cameras on a new router as well. |
* cache build * Catch and disable MQTT on name resolution error * Doorbell quick response * Set camera time zone #916 * Set timezone on camera #916 * OSD toggle for logo/timestamp * Add K10006 auth #742 * Fix /time_zone/get and return offset #916 * convert TZ offset to hours #916 * custom video filter #919 * Resend discovery message on HA online #907 #920 * Revert K10006 for WYZEDB3 #742 * Add more MQTT entities #921 #922 * Return json response/value for commands #835 * Fix threading issue on restart #902 * Fix SET cruise_points over MQTT * SET cruise_point #835 * split into multiple jobs * changelog
I updated to 2.3.11 since I was also having the same issue but now the container does not start with "RuntimeError: can't start new thread" Full snip of output is below
|
Yeah, no change here. I've changed routers in the home and removed then readded the camera to my Wyze app but still getting that timeout issue.
|
@ZacTyAdams I think we may have different issues with similar symptoms, my container wont even stay up :) |
@DrDavy Yeah this issue from the beginning seems to be something with the Wyze API. The restart and clear cache was one of the roadblocks though. |
Bridge is able to query api for list of cameras, but when connecting for a snapshot or stream, the log shows:
IOTC_ER_TIMEOUT
[WyzeBridge] ⏰ Timed out connecting to Living Room Cam.
[WyzeBridge] ⏰ Timed out connecting to Backyard Camera.
Have tested against versions 2.3.5 -> 2.3.8
The cameras do have a connection to Wyze servers and are viewable from the mobile app. Streams and snapshots stopped working roughly around 6/30/23 and no other errors show in the logs outside of the timeout error.
The text was updated successfully, but these errors were encountered: