Shawn Siefkas

@xcz011 late reply here, but wanted to check if this is in anyway related to problems users are experiencing with wyze api and local camera connections in the last 24...

> I am running on the latest Linux LTS. I use Docker with the run command. Adding --network host isnores my mapping of port 5000 to port 91, but even...

A wyze team member has posted [here](https://github.com/mrlt8/docker-wyze-bridge/issues/1438#issuecomment-2679316161) about potential real fix. In the meantime, you'd have to change your network configuration to one LAN to mitigate.

Same problem here today. My floodlights, v4, and doorbell cams all went down in the last few hours.

I can confirm that moving the docker-wyze-bridge and an affected camera onto the exact same LAN mitigates the issue. In my case, this required 2 steps: 1. Set `network_mode: host`...

@domeng83 @grinddking try the workaround that @delmlund pointed out if you can. Move all components onto the same LAN directly. Also, can anyone else confirm start time around 10:20 UTC...

@domeng83 I'm not familiar with running as an HA addon. The key seems to be having docker-wyze-bridge run on a network interface on the same LAN network as the camera(s)...

> I am not using Wyze Docker and my camera went blank this morning after the update. They are both on the same network, same account and all and I...

> > I started to see the same on all 3 of my v3 cams today. Cam feeds are fine in the Wyze app. > > Cam firmware: 4.36.13.0416 Wyze-bridge:...

@mrlt8 there was some sort of change further restricting network sources that can open the wyze cam streams earlier today. If this proves to be an intentional change it may...