docker-wyze-bridge icon indicating copy to clipboard operation
docker-wyze-bridge copied to clipboard

Published 20 hours ago • verified publisher icon mrlt8

Lost connection to the bridge...

Open lviciedo opened this issue 2 years ago • 5 comments

Anyone else seeing this after yesterdays update?

lviciedo avatar Sep 07 '23 21:09 lviciedo

Same thing here. Loses connection all the time.

asinla avatar Sep 09 '23 00:09 asinla

Can you post some of the logs?

mrlt8 avatar Sep 11 '23 01:09 mrlt8

I get the "Lost connection to the bridge..." error when connecting via Nginx Proxy Manager (NPM) but I don't get the error if I connect directly to the WebUI port of my Docker container. So in my case this feels like an NPM configuration issue.

Wyze-bridge starts working again after refreshing the page. The 'Lost connection' error comes back after 90 seconds.

Only the WebUI is affected, wyze-bridge continues to record and take snapshots while the 'Lost connection' error is displayed.

There are no error messages in my wyze-bridge logs, just the 'client stopped reading' and 'new client reading' messages.

` 🚀 DOCKER-WYZE-BRIDGE v2.3.17

[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.18.0.11: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] 💾 Saving 'cameras' to local cache... [WyzeBridge] 🪄 FILTER BLOCKING: 1 of 6 cams [WyzeBridge] [+] Adding cam1 [WYZE_CAKP2JFUS] [WyzeBridge] [+] Adding cam2 [WYZE_CAKP2JFUS] [WyzeBridge] [+] Adding cam3 [WYZE_CAKP2JFUS] [WyzeBridge] [+] Adding cam4 [WYZE_CAKP2JFUS] [WyzeBridge] [+] Adding cam5 [WYZEC1-JZ] [WyzeBridge] starting MediaMTX 1.0.3 [WyzeBridge] 🎬 5 streams enabled [WyzeBridge] 🎉 Connecting to WyzeCam V3 - cam1 on 10.0.0.124 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - cam2 on 10.0.0.120 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - cam3 on 10.0.0.121 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - cam4 on 10.0.0.122 [WyzeBridge] 🎉 Connecting to WyzeCam V2 - cam5 on 10.0.0.123 [cam2] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 75%) FW: 4.36.11.5859 🔒 (DTLS) (2/3) [cam2] 📹 Will record 600s mp4 clips to /record/cam2/ [cam2] WARNING: Skipping smaller frame at start of stream (frame_size=1) [cam3] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 97%) FW: 4.36.11.5859 🔒 (DTLS) (2/3) [cam3] 📹 Will record 600s mp4 clips to /record/cam3/ [cam3] WARNING: Skipping smaller frame at start of stream (frame_size=1) [cam4] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 99%) FW: 4.36.11.5859 🔒 (DTLS) (2/3) [cam4] 📹 Will record 600s mp4 clips to /record/cam4/ [cam4] WARNING: Skipping smaller frame at start of stream (frame_size=1) [WyzeBridge] ✅ '/cam3 stream is UP! (3/3) [cam5] 📡 Getting 120kb/s HD stream (H264/15fps) via LAN mode (WiFi: 95%) FW: 4.9.9.1851 🔒 (DTLS) (2/3) [cam5] 📹 Will record 600s mp4 clips to /record/cam5/ [WyzeBridge] ✅ '/cam5 stream is UP! (3/3) [cam1] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 32%) FW: 4.36.11.5859 🔒 (DTLS) (2/3) [cam1] 📹 Will record 600s mp4 clips to /record/cam1/ [cam1] WARNING: Skipping smaller frame at start of stream (frame_size=1) [WyzeBridge] ✅ '/cam2 stream is UP! (3/3) [WyzeBridge] ✅ '/cam4 stream is UP! (3/3) [WyzeBridge] ✅ '/cam1 stream is UP! (3/3) [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET / HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /static/site.css HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /static/site.js HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam1.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam2.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam3.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam4.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam5.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam2.jpg HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam1.jpg HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam4.jpg HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam3.jpg HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /img/cam5.jpg HTTP/1.1" 304 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:53:51] "GET /api/sse_status HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.1 - - [21/Sep/2023 08:54:00] "GET / HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:10] "GET / HTTP/1.1" 200 - [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:21] "GET /img/cam4.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:21] "GET /img/cam5.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:21] "GET /img/cam3.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:21] "GET /img/cam2.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:21] "GET /img/cam1.jpg HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:51] "GET /img/cam4.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:51] "GET /img/cam2.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:51] "GET /img/cam3.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:51] "GET /img/cam1.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:54:51] "GET /img/cam5.jpg HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.1 - - [21/Sep/2023 08:55:00] "GET / HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:10] "GET / HTTP/1.1" 200 - [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:21] "GET /img/cam4.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:21] "GET /img/cam1.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:21] "GET /img/cam2.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:21] "GET /img/cam3.jpg HTTP/1.1" 200 - [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:55:21] "GET /img/cam5.jpg HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.1 - - [21/Sep/2023 08:56:01] "GET / HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:56:10] "GET / HTTP/1.1" 200 - [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 172.18.0.1 - - [21/Sep/2023 08:57:01] "GET / HTTP/1.1" 200 - [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 172.18.0.15 - - [21/Sep/2023 08:57:10] "GET / HTTP/1.1" 200 - [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam4 [WyzeBridge] 📖 New client reading from cam3 [WyzeBridge] 📖 New client reading from cam4 [WyzeBridge] 📖 New client reading from cam1 [WyzeBridge] 📖 New client reading from cam2 [WyzeBridge] 📖 New client reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam2 [WyzeBridge] 📕 Client stopped reading from cam5 [WyzeBridge] 📕 Client stopped reading from cam3 [WyzeBridge] 📕 Client stopped reading from cam1 [WyzeBridge] 📕 Client stopped reading from cam4 `

c0f avatar Sep 21 '23 08:09 c0f

My version of this issue is solved. No idea if it will work for others. TL;DR below.

This, at least in my case, is caused by Nginx not handling event-stream content without further configs, and further aggravated by default 60s read timeouts for proxied traffic.

In short, you need to add the following config options to whichever server is proxying your WebUI/API traffic:

proxy_buffering off;
proxy_cache off;
proxy_read_timeout <very_high_value>; # e.g. 3600

I'm also seeing similar behaviour to this, only through Nginx when using it as a reverse proxy (direct access is fine). I've tried setting an upstream with keepalives, but no luck. I'll consistently get Lost connection to the bridge... pop up in the UI after a minute and all my streams freeze until I do a manual refresh.

This seems to be rooted in requests that go to <host>:5000/api/sse_status. This works fine without the proxy, but will consistently fail with it in place.

Adding an explicit proxy_pass for /api in the nginx config to attempt to handle this results in a timeout only for the sse_status endpoint. Everything else works fine :shrug:

> GET /api/sse_status HTTP/1.1
> Host: <host>:5000
> User-Agent: curl/8.4.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/1.1 200 OK
< Server: nginx/1.25.2
< Date: Sun, 15 Oct 2023 16:13:20 GMT
< Content-Type: text/event-stream; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
<
* TLSv1.3 (IN), TLS alert, close notify (256):
* transfer closed with outstanding read data remaining
* Closing connection
* TLSv1.3 (OUT), TLS alert, close notify (256):
curl: (18) transfer closed with outstanding read data remaining

Initial suspicion is that this is just spinning forever on the infinite sleep loop here if the status can't be retrieved:

def sse_generator(sse_status: Callable) -> Generator[str, str, str]:
    """Generator to return the status for enabled cameras."""
    cameras = {}
    while True:
        if cameras != (cameras := sse_status()):
            yield f"data: {json.dumps(cameras)}\n\n"
        sleep(1)

I'll keep poking at this and update if I figure anything out...

Update: This issue seems to be something to do with nginx handling event-stream data. Setting this endpoint to return a hardcoded string (example below) avoids the scenario being seen here since it's sufficient to satisfy the comparison at https://github.com/mrlt8/docker-wyze-bridge/blob/33fe98e1b01a822223b4df5c378f327d05a2c7ab/app/wyzebridge/web_ui.py#L16

   @app.route("/api/sse_status")
    def sse_status():
        return Response(
            "foo"
        )

Update 2: Got it, kinda. After tracking this down to event-stream data being the problem, the solution for me appears to be adding the following headers to the location directive used for /api in my nginx config:

proxy_buffering off;
proxy_cache off;

Source: https://stackoverflow.com/questions/13672743/eventsource-server-sent-events-through-nginx, though note that the rest of the config options noted don't appear to be needed in my case.

I still get intermittent "Lost connection to the bridge..." errors, but they seem to automatically recover when the UI does its next applyPreferences or update_img which happens every few seconds, so it's good enough for me until someone can do a more in-depth investigation here.

Here's the full config (with some redactions) that should allow this all to work with basic auth, TLS, and some access restrictions based on the network it runs on (note this is trivial to spoof). docker-compose.yml is mostly stock other than setting WB_HLS_URL to https://<HOST>:8888/ and setting all port bindings to 127.0.0.1:<PORT>:<PORT>.

  server {
        listen <HOST_IP>:5000 ssl;
        ssl_certificate /etc/letsencrypt/live/<HOST>/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/<HOST>/privkey.pem;
        allow 192.168.1.0/24;
        deny all;

        location /api {
                proxy_buffering off;
                proxy_cache off;
                proxy_pass      http://127.0.0.1:5000/api;
        }

        location / {
                auth_basic      "You didn't say the magic word...";
                auth_basic_user_file /etc/nginx/.htpasswd;
                proxy_pass      http://127.0.0.1:5000/;
        }
  }

  server {
        listen <HOST_IP>:8888 ssl;
        ssl_certificate /etc/letsencrypt/live/<HOST>/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/<HOST>/privkey.pem;
        allow 192.168.1.0/24;
        deny all;
        location / {
                proxy_pass      http://127.0.0.1:8888/;
        }
  }

But yeah, not sure what's causing the "Lost connection" issues at this point as there are no errors in the browser console or wyze-bridge container logs :shrug: At least it's just an annoyance at this point :neutral_face: AFAICT this is still due to intermittent failures to retrieve sse_status that show NS_ERROR_NET_PARTIAL_TRANSFER in the network tab of the browser after waiting for a response for 60 seconds. When the response finally arrives (a minute later) the payload will appear in the Response tab, however this correlates directly with the "Lost connection to the bridge..." error, and then resolves itself as soon as the next request is opened.

Update 3: Looks like the intermittent drops, with everything above considered and still required, are related to Nginx proxy timeouts. Notably, since adding proxy_read_timeout 3600; (or other arbitrarily high value) for the server directive handling docker-wyze-bridge this seems to be "resolved". Quite possible this is also affecting default configs of Nginx Proxy Manager if a suitably high read timeout isn't being set.

maclarel avatar Oct 15 '23 15:10 maclarel

I'm seeing this same issue, do you know where I would go to set the parameters you specified when running the wyze bridge as a Home Assistant Add-On?

waltershome avatar Dec 01 '23 18:12 waltershome