-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Comments
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 |
Fix posted: #1432 (comment) and a PR was made |
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: Thank you AaronMcGuirk007 |
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. |
remove port statements and adding host statements has fixed the problem for me. services: |
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). |
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 |
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)
The text was updated successfully, but these errors were encountered: