BUG: Cam v3, Pan Cam v3, Doorbell Stopped working in bridge last week

[jplwoodward]

Describe the bug

Running WyzeBridge on the same syste successfully for weeks...stopped working last week sometime. In the GUI (port 91), the doorbells are not rotated as they had always been. Cameras show old previews but are never live. All cameras show live in the Wyze app.

• Cam v3 firmware 4.36.13.0416
• Doorbell firmware 4.251.333
• Cam Pan v3 firmware 4.50.5.1318

Affected Bridge Version

2.10.3

Bridge type

Docker Run/Compose

Affected Camera(s)

Cam 3, Pan Cam v3, Doorbell Cam

Affected Camera Firmware

• Cam v3 firmware 4.36.13.0416 * Doorbell firmware 4.251.333 * Cam Pan v3 firmware 4.50.5.1318

docker-compose or config (if applicable)

[letrain02]

Please read other bugs. This is A wide spread issue with everyone using the wyze bridge. Change network mode to "host" for a temporary fix. Wyze changed something and it's made everyone have issues.

[jplwoodward]

Thank you. I have now read thw other thread. Changing to host has no effect for me.

[cheme75]

Posts really need to specify OS at a minimum. There are a couple of workarounds but any potential success is OS dependent. None work for Windows directly.

It gets really old reading HA or Linux users tout workaround solutions as an end all, telling everyone that posts an issue or bug to just see the fix in post #xxxx without qualifying that it only works for xxx.

Seems like everyone, particularly the higher end techs, could employ a greater level of understanding and tolerance of the casual user to at least qualify and explain a bit more about their workaround suggestions.

I'm not sure how it could be done now that there's a handful of mixed threads, but it sure would be helpful if they could be segmented into Windows, Linux, HA, OSX, Others.

I do understand most can't dedicate the time, I can't nor do I have enough expertise to do much good, so grateful for all those who post info that's shared.

Just frustrating to get dozens of notifications about posts that do not apply - in my case to windows or a non-rollback-able fw device.

Hopefully some insights here will help the developer to fix the bridge for all.

[c0f]

Thank you. I have now read thw other thread. Changing to host has no effect for me.

Which operating system are you running Docker on?

[ScottySTL]

Yes, I would like an easy to understand answer on how to get a work-around working for Docker in a Windows host.

[c0f]

Unfortunately I can't help with Windows but the workaround that worked for me might be similar.

Once you have enabled 'network_mode: host' in docker-compose.yml try temporarily disabling your firewall on your Windows computer. Don't forget to restart your container once you've set 'network_mode: host'.

I've found that, in my case, 'network_mode: host' isn't enough to workaround the problem.

I'm on Linux and I also needed to make firewall changes (specifically, allowing all inbound UDP traffic from my camera's IP addresses along with the usual ports 5000, 1935, 8554, 8888, 8889, 8189.)

Temporarily disabling your Windows firewall will help to work out if Windows firewall changes might help with the workaround.

[ScottySTL]

Unfortunately I can't help with Windows but the workaround that worked for me might be similar.

Once you have enabled 'network_mode: host' in docker-compose.yml try temporarily disabling your firewall on your Windows computer. Don't forget to restart your container once you've set 'network_mode: host'.

I've found that, in my case, 'network_mode: host' isn't enough to workaround the problem.

I'm on Linux and I also needed to make firewall changes (specifically, allowing all inbound UDP traffic from my camera's IP addresses along with the usual ports 5000, 1935, 8554, 8888, 8889, 8189.)

Temporarily disabling your Windows firewall will help to work out if Windows firewall changes might help with the workaround.

Yeah I already had my Windows firewall disabled and it didn't do anything in either host mode or lan mode.
LAN mode i get the connection error from the Wyzecams, Host mode I get nothing trying to connect.

[ScottySTL]

Actually, I just made progress...from another post that was just posted in another thread....
On the windows version of Docker I have to go into Docker settings->resources-> advanced-> network and check the box for "Enable host networking"...now at least when in run the container in host mode the cameras are trying to connect (I just need to bring them back onto my main VLAN instead of IOT

[jplwoodward]

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 accessing the gui via port 5000 does not work.

[shawnsi]

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 accessing the gui via port 5000 does not work.

Are your cameras on the same exact LAN subnet at your docker-wyze-bridge? That's also a requirement right now.

[Jeppedy]

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 accessing the gui via port 5000 does not work.

Are your cameras on the same exact LAN subnet at your docker-wyze-bridge? That's also a requirement right now.

Mine are absolutely not. I have my cams on an IoT network, and HA on my core network.
Any suggestions? Anything I can share to help with diagnosing the issue?

[shawnsi]

A wyze team member has posted here about potential real fix. In the meantime, you'd have to change your network configuration to one LAN to mitigate.

[Jeppedy]

A wyze team member has posted here about potential real fix. In the meantime, you'd have to change your network configuration to one LAN to mitigate.

Thanks! I'll wait for new developments and hopefully a fix.

[ScottySTL]

Yeah at this point I am just going to wait for a fix on the back end