Skip to content

I have 12 cameras 3 Pro all of them stopped recording on the server yesterday. What’s happening? #1433

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

Open
ehabnt opened this issue Feb 21, 2025 · 7 comments
Labels
bug Something isn't working

Comments

@ehabnt
Copy link

ehabnt commented Feb 21, 2025

Describe the bug

I have 12 cameras 3 Pro all of them stopped recording on the server yesterday. What’s happening?

Affected Bridge Version

image ID: 518e804f6636

Bridge type

Docker Run/Compose

Affected Camera(s)

12 cameras v3 pro

Affected Camera Firmware

Lastest version 4.58.13.1321

docker-compose or config (if applicable)

---
services:
    wyze-bridge:
        container_name: wyze-bridge
        restart: unless-stopped
        image: mrlt8/wyze-bridge:latest
        ports:
            - 1935:1935 # RTMP
            - 8554:8554 # RTSP
            - 8888:8888 # HLS
            - 8889:8889 # WebRTC
            - 8189:8189/udp # WebRTC/ICE            
            - 5000:5000 # WEB-UI
            - 9997:9997 # Expose port for API
        environment:
            - WYZE_EMAIL=xxxxxxxxxxxxxxxxxxxx
            - WYZE_PASSWORD=xxxxxxxxxxxxxxx
            - API_ID=xxxxxxxxxxxxxxxxxxxxxxx
            - API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
            - WB_IP=xxxxxxxxxxxxxxxxxx
            - WB_AUTH=True
            - WB_USERNAME=xxxxxxxxxxxxxxxx
            - WB_PASSWORD=xxxxxxxxxxxxxxx
            - NET_MODE=LAN
            - ON_DEMAND=False
            - TZ=xxxxx/xxxxx
            - RECORD_ALL=True
            - RECORD_LENGTH=3600s
            - RECORD_PATH=/record/{cam_name}/{cam_name}_%Y-%m-%d_%H-%M-%S
            - ENABLE_AUDIO=True
            - RECORD_KEEP=0s
            - IGNORE_OFFLINE=true
            - FPS_FIX=true
            - ENABLE_BOA=true
        volumes:
            - /xxxx/xxxx/xxxx/xxxx:/xxxx/
@ehabnt ehabnt added the bug Something isn't working label Feb 21, 2025
@AaronMcGuirk007
Copy link

Hi there, we have an on-going thread of the same issue here if you would like to add to it Discussion: Wyze may have locked down real-time previews with a new update #1432

@jdeath
Copy link
Contributor

jdeath commented Feb 22, 2025

Fix posted: #1432 (comment) and a PR was made

@ehabnt
Copy link
Author

ehabnt commented Feb 23, 2025

The issue was resolved by adding network_mode: host and removing all ports.

Everything is working now, but the only drawback is that I can no longer change the ports as before.

Previously, it was possible to change the ports freely, but now we are restricted.

The only way to change the port is by using NGINX

For docker-compose.yaml file


services:
wyze-bridge:
container_name: wyze-bridge
restart: unless-stopped
image: mrlt8/wyze-bridge:latest
network_mode: host
environment:
- WYZE_EMAIL=xxxxxxxxxxxxxxxxxxxx
- WYZE_PASSWORD=xxxxxxxxxxxxxxx
- API_ID=xxxxxxxxxxxxxxxxxxxxxxx
- API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- WB_IP=xxxxxxxxxxxxxxxxxx
- WB_AUTH=True
- WB_USERNAME=xxxxxxxxxxxxxxxx
- WB_PASSWORD=xxxxxxxxxxxxxxx
- NET_MODE=LAN
- ON_DEMAND=False
- TZ=xxxxx/xxxxx
- RECORD_ALL=True
- RECORD_LENGTH=3600s
- RECORD_PATH=/record/{cam_name}/{cam_name}%Y-%m-%d%H-%M-%S
- ENABLE_AUDIO=True
- RECORD_KEEP=0s
- IGNORE_OFFLINE=true
- FPS_FIX=true
- ENABLE_BOA=true
volumes:
- /xxxx/xxxx/xxxx/xxxx:/xxxx/

Thank you AaronMcGuirk007

@jjyu420
Copy link

jjyu420 commented Feb 24, 2025

Confirmed adding that network_mode: host to the configuration file fixed this issue for me also. I did not remove any of the port information also.

@rhankins77
Copy link

remove port statements and adding host statements has fixed the problem for me.

services:
wyze-bridge:
container_name: wyze-bridge
restart: unless-stopped
image: mrlt8/wyze-bridge:latest
network_mode: host

@c0f
Copy link

c0f commented Feb 24, 2025

remove port statements and adding host statements has fixed the problem for me.

Hi, do you have ufw running?

'network_mode: host' only works for me if I disable ufw entirely with 'ufw disable'.

I've even added rules to allow ports 5000, 1935, 8554, 8888, 8889 and 8189. The moment I disable ufw the feeds spring back into life (with host mode enabled).

My ufw rules are quite permissive e.g.: ufw allow from any to any port XXXX

Edit: Based on an earlier comment I enabled ufw and added a rule to allow all UDP from my camera's IP addresses:

sudo ufw allow from 10.0.0.xxx to any proto udp

This allows me to enable ufw and successfully run Wyzebridge in host mode.

It looks like each camera is trying to connect to Wyzebridge on a random UDP port. My five cameras are all using UDP ports over 30,000 to connect to Wyzebridge (tcpdump -i enp1s0 src 10.0.0.xxx).

@awwbaker
Copy link

Image

I am not that technical but I have 2 Wyze Spotlight Cameras that have been successfully feeding into Frigate for many months. All of a sudden that seems to be failed. I noted on the display that the cameras are still showing a capture from 14 February. Would anyone be willing to point me in the right direction to begin trouble shooting? Any push would be appreciated. Thank You,Anthony Baker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants