mrlt8 / docker-wyze-bridge

WebRTC/RTSP/RTMP/LL-HLS bridge for Wyze cams in a docker container
GNU Affero General Public License v3.0
2.58k stars 158 forks source link

Lose Cam Connections - Cam/server connection times out after XXX of time, usually up no more than 12 hours #649

Open guywholikestobreakthings opened 1 year ago

guywholikestobreakthings commented 1 year ago

I was having this issue before and thought it was solved w/ running as Admin w/ SU rights. The issue is still persisting though and after a few hours, I lose connections to the cameras and get the below errors.

I've tried to follow this issue w/ no luck: https://github.com/mrlt8/docker-wyze-bridge/issues/605

2022/12/27 15:59:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 15:59:28] "GET /img/master-cam.jpg HTTP/1.1" 304 - 2022/12/27 15:59:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 15:59:28] "GET /img/pan-cam.jpg HTTP/1.1" 304 - 2022/12/27 15:59:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 15:59:28] "GET /img/front-porch-cam.jpg HTTP/1.1" 304 - 2022/12/27 15:59:33 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... 2022/12/27 15:59:48 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... 2022/12/27 16:00:01 [WyzeBridge] HTTPSConnectionPool(host='api.wyzecam.com', port=443): Max retries exceeded with url: /app/v2/home_page/get_object_list (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fd508024f70>: Failed to establish a new connection: [Errno 113] No route to host')) 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/master-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/pan-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/front-porch-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/master-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/pan-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:09 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:09] "GET /img/front-porch-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:10 [WyzeBridge] HTTPSConnectionPool(host='api.wyzecam.com', port=443): Max retries exceeded with url: /app/v2/home_page/get_object_list (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fd507fc9db0>: Failed to establish a new connection: [Errno 113] No route to host')) 2022/12/27 16:00:26 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/master-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/pan-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/front-porch-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/pan-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/master-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:28 [WyzeBridge] 172.17.0.1 - - [27/Dec/2022 16:00:28] "GET /img/front-porch-cam.jpg HTTP/1.1" 304 - 2022/12/27 16:00:35 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...

mrlt8 commented 1 year ago

Is this with docker desktop? Rolling back to v4.12.0 seems to help with some of the docker-desktop related issues: https://docs.docker.com/desktop/release-notes/#4120

shizenyasuya commented 1 year ago

I am having the same issue. and I am on docker desktop. Actually I've never gotten it to start successfully after this issue came up for me. I tried restaring the camera and the service (container). Once I finally got it going, it worked great for about a day and then it just stopped and I can't get it back. I'll try rolling back to 4.12.0 and see if it makes a difference.

phdavis commented 1 year ago

Was running in the same issue/s. Cams would work fine for a few hours up to a day or so then just stop responding. Restarting the container was usually enough to get them back going. This morning I noticed they were stopped again and after restarting couldn't get them going again. After checking the logs I was also getting the 'Max retries exceeded' message.

I went ahead and uninstalled Docker Desktop (latest) and installed 4.12.0. Running on Windows Server 2022 with a local V3 cam and another V2 cam in another state. I've also added the tokens volume mentioned elsewhere.

So far so good and the performance seems better too. Previously viewing in Blue Iris was extremely slow or several seconds behind real-time. I'll update here if this changes over the weekend but thought I'd post my data.

guywholikestobreakthings commented 1 year ago

Uninstalled v4.15 and just installed v4.12. Let's see how it goes! Thanks for the update.

guywholikestobreakthings commented 1 year ago

Is this with docker desktop? Rolling back to v4.12.0 seems to help with some of the docker-desktop related issues: https://docs.docker.com/desktop/release-notes/#4120

It is. Just reverted to v4.12 and will update. So far, it does seem like the feed is a little faster and not as choppy. Before, it would freeze after a few seconds and have to refresh the localhost:5000 page.

shizenyasuya commented 1 year ago

I also have not had any failure since reverting to 4.12.0. I think that is the solution for this issue.

phdavis commented 1 year ago

Not quite 24 hours but both of my cams are still going strong. No issues this morning.

guywholikestobreakthings commented 1 year ago

Can also confirm, still working... Longest it's stayed online.

guywholikestobreakthings commented 1 year ago

Still going strong...