Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Discussion: Wyze may have locked down real-time previews with a new update #1432

Closed
AaronMcGuirk007 opened this issue Feb 21, 2025 · 281 comments
Closed

Discussion: Wyze may have locked down real-time previews with a new update #1432

AaronMcGuirk007 opened this issue Feb 21, 2025 · 281 comments

Comments

@AaronMcGuirk007
Copy link

AaronMcGuirk007 commented Feb 21, 2025 •
edited
Loading

I recently noticed that my Wyze Bridge (v2.10.3) and Frigate servers stopped receiving camera feeds as of 5 PM EST on 2/20/2025.

To determine whether the issue stemmed from a network-related problem or a misconfiguration during my VM migration to VMware, I accessed my Wyze dashboard. Upon doing so, I encountered the following message:

"Start live stream this camera for free.
Wyze offers free web live streaming for one camera. After you pick a camera, live streaming will be unlocked for the rest of this month. But don’t worry—you can switch it or pick a new one for free next month.
Ready to start web live streaming on this camera now?"

While I cannot confirm whether this change is the root cause of the issue, the previews displayed in my Wyze Dashboard match exactly what is seen in my Wyze bridge.

Given this, I suspect Wyze may be restricting access for non-paying users who were previously utilizing this open-source functionality.

EDIT: I am currently running V3 Cam (v.4.36.10.4054) and V3 Cam Pans (v.4.50.5.0587) and my V3 Cam that is working has the same firmware as my other V3 Cam. I don't believe it to be a firmware issue but rather an issue with the API call to wherever the cameras feed is being streamed. Likely they imposed a new feature to save resources on whatever cloud instance they are hosting their servers on but this is my pure speculation.

[front-door-cam] [-13] IOTC_ER_TIMEOUT [driveway-cam] [-13] IOTC_ER_TIMEOUT [WyzeBridge] 10.10.30.136 - - [21/Feb/2025 18:53:52] "GET /snapshot/backyard-cam.jpg?1740164012727 HTTP/1.1" 200 - [backyard-cam] [-13] IOTC_ER_TIMEOUT [WyzeBridge] 10.10.30.136 - - [21/Feb/2025 18:53:52] "GET /snapshot/front-door-cam.jpg?1740164012728 HTTP/1.1" 200 - [WyzeBridge] 🎉 Connecting to WyzeCam Pan V3 - Front Door Cam on 10.10.30.234 [WyzeBridge] 🎉 Connecting to WyzeCam Pan V3 - Backyard Cam on 10.10.30.193 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - Driveway Cam on 10.10.30.241 [WyzeBridge] 10.10.30.136 - - [21/Feb/2025 18:53:52] "GET /snapshot/front-door-cam.jpg?1740164012728 HTTP/1.1" 304 - [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... [backyard-cam] [-13] IOTC_ER_TIMEOUT [front-door-cam] [-13] IOTC_ER_TIMEOUT

@jringuette
Copy link

Same issue here. Both my cameras stopped working with the bridge at 00:00 EST on 2/21/2025. Since then, i keep seeing these log entries over and over:

2025-02-21 18:05:58.948464+00:00[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.2.74
2025-02-21 18:05:58.950889+00:00[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Patio on 192.168.2.75
2025-02-21 18:05:58.960266+00:00[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.2.74
2025-02-21 18:05:58.962664+00:00[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Patio on 192.168.2.75
2025-02-21 18:06:18.506867+00:00[garage] [-13] IOTC_ER_TIMEOUT
2025-02-21 18:06:18.512910+00:00[garage-sub] [-13] IOTC_ER_TIMEOUT
2025-02-21 18:06:18.512967+00:00[patio-sub] [-13] IOTC_ER_TIMEOUT
2025-02-21 18:06:18.521055+00:00[patio] [-13] IOTC_ER_TIMEOUT

Restarted everything (cameras, router, AP, container) but without changing anything. Everything works fine via the wyze android app.

@spasmodic1
Copy link

Seeing the same thing "[-13] IOTC_ER_TIMEOUT"

@guaycuru
Copy link

I'm seeing the same thing, but I'm a Wyze Unlimited subscriber, so I don't think I would / should be restricted

@carldanley
Copy link

Same thing here :(

@cheme75
Copy link

cheme75 commented Feb 21, 2025

Same error now with V1 Doorbell cam - it pulls snapshot from yesterday, no rotation and an odd square format. Wont refresh snapshot either.

@swarshah
Copy link

It's been out for at least a few months, so it's not likely due to this new thing.

@industrial64
Copy link

Same thing on all 'local' V4/V2/Pan's
Perhaps we need to roll back the Cam firmware, like I had to for 'remote' cameras to continue working with WyzeBridge.

@jringuette
Copy link

I don't think it is related to the cam firmware. I'm using two V3 and both are using version 4.36.13.0416 which was released on 7/8/2024

@industrial64
Copy link

Copy that!
I stand corrected - Just checked on all V2 camera's and they haven't gotten a FW upgrade since [4.9.9.3006] (January 16, 2024)
V4's got an update months ago and also continued working until today: [4.52.9.1134] (November 1, 2024)
Hopefully someone has an idea, but this might be some mischief inside Wyze, killing the real usefulness of their products (again).

@industrial64
Copy link

One more useful tidbit of info:
My V2 and V3 cameras that are not local, but still continue to work remotely by staying locked to the functional [4.36.11.7095] (October 25, 2023) firmware, with auto-updates disabled = continue to work right-now.
This may help our dev @mrlt8 diagnose what has happened.

@1fastt2
Copy link

1fastt2 commented Feb 21, 2025

FWIW - I tried creating a new API ID/Key to no avail. 🤦🏼‍♂️

@AaronMcGuirk007
Copy link
Author

AaronMcGuirk007 commented Feb 21, 2025 •
edited
Loading

It's been out for at least a few months, so it's not likely due to this new thing.

I wasn't aware, hence the discussion, but was just curious if they implemented any back-end updates. I appreciate the feedback!

@AaronMcGuirk007
Copy link
Author

I'm seeing the same thing, but I'm a Wyze Unlimited subscriber, so I don't think I would / should be restricted

This is great to know! Thank you for the feedback.

@AaronMcGuirk007 AaronMcGuirk007 mentioned this issue Feb 21, 2025
Open
@cheme75
Copy link

cheme75 commented Feb 21, 2025

From my time using wyze since before subscriptions, they seem to be more and more desperate to rope customers into subscriptions. Not surprised they'd do something to block or limit 3rd party access.

@cheme75
Copy link

cheme75 commented Feb 21, 2025

I'm seeing the same thing, but I'm a Wyze Unlimited subscriber, so I don't think I would / should be restricted

don't think your subscriber access has anything to do with 3rd party access - you don't need a 3rd party ID and Key to use camplus or other wyze subscriptions - different access than 3rd parties.

@jringuette
Copy link

Even with debug log, i don't see much more. Relevant part:

2025-02-21 19:17:13.004217+00:0019:17:13 [INFO][WyzeBridge] 🎬 4 streams enabled
2025-02-21 19:17:19.456734+00:0019:17:19 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.2.74
2025-02-21 19:17:19.477348+00:0019:17:19 [WARNING][WyzeBridge] WARNING: This process (pid=1) is multi-threaded, use of fork() may lead to deadlocks in the child.
2025-02-21 19:17:19.477833+00:0019:17:19 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam V3 - Patio on 192.168.2.75
2025-02-21 19:17:19.480412+00:0019:17:19 [WARNING][WyzeBridge] WARNING: This process (pid=1) is multi-threaded, use of fork() may lead to deadlocks in the child.
2025-02-21 19:17:19.480770+00:0019:17:19 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage on 192.168.2.74
2025-02-21 19:17:19.484030+00:0019:17:19 [WARNING][WyzeBridge] WARNING: This process (pid=1) is multi-threaded, use of fork() may lead to deadlocks in the child.
2025-02-21 19:17:19.484122+00:0019:17:19 [DEBUG][garage-sub] Connect via IOTC_Connect_ByUIDEx
2025-02-21 19:17:19.484134+00:0019:17:19 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam V3 - Patio on 192.168.2.75
2025-02-21 19:17:19.486414+00:0019:17:19 [WARNING][WyzeBridge] WARNING: This process (pid=1) is multi-threaded, use of fork() may lead to deadlocks in the child.
2025-02-21 19:17:19.487878+00:0019:17:19 [DEBUG][patio-sub] Connect via IOTC_Connect_ByUIDEx
2025-02-21 19:17:19.490296+00:0019:17:19 [DEBUG][garage] Connect via IOTC_Connect_ByUIDEx
2025-02-21 19:17:19.491927+00:0019:17:19 [DEBUG][patio] Connect via IOTC_Connect_ByUIDEx
2025-02-21 19:17:39.504921+00:0019:17:39 [WARNING][WyzeBridge] ⏰ Timed out connecting to Patio.
2025-02-21 19:17:39.509110+00:0019:17:39 [WARNING][garage] [-13] IOTC_ER_TIMEOUT
2025-02-21 19:17:39.518709+00:0019:17:39 [WARNING][patio] [-13] IOTC_ER_TIMEOUT
2025-02-21 19:17:39.519716+00:0019:17:39 [WARNING][garage-sub] [-13] IOTC_ER_TIMEOUT
2025-02-21 19:17:39.520448+00:0019:17:39 [WARNING][patio-sub] [-13] IOTC_ER_TIMEOUT

@Powell-Kevin
Copy link

Mine just went down on 2/21/25 at 11:48 MST. I have 5 V4 cams, and there hasn't been any firmware updates for those for a few months. I am on the "Cam Unlimited" plan so I don't think it's related to that either. It does show it's still getting the camera names from the API:

wyze-bridge | [WyzeBridge] Press CTRL+C to quit
wyze-bridge | [WyzeBridge] [+] Adding Dining Room West [HL_CAM4]
wyze-bridge | [WyzeBridge] [+] Adding Indoor Living Room [HL_CAM4]
wyze-bridge | [WyzeBridge] [+] Adding Living Room West [HL_CAM4]
wyze-bridge | [WyzeBridge] [+] Adding Living Room [HL_CAM4]
wyze-bridge | [WyzeBridge] [MTX] starting MediaMTX 1.8.5
wyze-bridge | [WyzeBridge] 🎬 5 streams enabled
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room West on 10.0.20.66
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room on 10.0.20.65
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Dining Room West on 10.0.20.68
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor Living Room on 10.0.20.67
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Master Bedroom North on 10.0.20.64
wyze-bridge | [living-room-west] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
wyze-bridge | [WyzeBridge] [API] Fetched [5] cameras
wyze-bridge | [WyzeBridge] 💾 Saving 'cameras' to local cache...
wyze-bridge | [living-room] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room West on 10.0.20.66
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room on 10.0.20.65
wyze-bridge | [dining-room-west] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [indoor-living-room] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [master-bedroom-north] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Dining Room West on 10.0.20.68
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor Living Room on 10.0.20.67
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Master Bedroom North on 10.0.20.64
wyze-bridge | [living-room-west] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [living-room] [-13] IOTC_ER_TIMEOUT

Only thing I can think of that changed on my end was updating the app on iPad yesterday, but I can't see that affecting anything...

@netninja71
Copy link

Same thing happening to me as of last night, generating a new API Key doesn’t seem to make a difference.

@dreadnought-0
Copy link

For some reason, as I tinker with a few things on the preview page like restarting mtx server, clear cache and reconnect, etc. I can get random previews to appear that are current, but still no streams. Maybe every 10 - 15 minutes I can get a current preview.

@AaronMcGuirk007 AaronMcGuirk007 mentioned this issue Feb 21, 2025
Open
@AaronMcGuirk007
Copy link
Author

For some reason, as I tinker with a few things on the preview page like restarting mtx server, clear cache and reconnect, etc. I can get random previews to appear that are current, but still no streams. Maybe every 10 - 15 minutes I can get a current preview.

I am able to replicate the same thing, likely just snapshot previews of the Wyze API restream

@AaronMcGuirk007
Copy link
Author

Mine just went down on 2/21/25 at 11:48 MST. I have 5 V4 cams, and there hasn't been any firmware updates for those for a few months. I am on the "Cam Unlimited" plan so I don't think it's related to that either. It does show it's still getting the camera names from the API:

wyze-bridge | [WyzeBridge] Press CTRL+C to quit wyze-bridge | [WyzeBridge] [+] Adding Dining Room West [HL_CAM4] wyze-bridge | [WyzeBridge] [+] Adding Indoor Living Room [HL_CAM4] wyze-bridge | [WyzeBridge] [+] Adding Living Room West [HL_CAM4] wyze-bridge | [WyzeBridge] [+] Adding Living Room [HL_CAM4] wyze-bridge | [WyzeBridge] [MTX] starting MediaMTX 1.8.5 wyze-bridge | [WyzeBridge] 🎬 5 streams enabled wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room West on 10.0.20.66 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room on 10.0.20.65 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Dining Room West on 10.0.20.68 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor Living Room on 10.0.20.67 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Master Bedroom North on 10.0.20.64 wyze-bridge | [living-room-west] [-13] IOTC_ER_TIMEOUT wyze-bridge | [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... wyze-bridge | [WyzeBridge] [API] Fetched [5] cameras wyze-bridge | [WyzeBridge] 💾 Saving 'cameras' to local cache... wyze-bridge | [living-room] [-13] IOTC_ER_TIMEOUT wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room West on 10.0.20.66 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Living Room on 10.0.20.65 wyze-bridge | [dining-room-west] [-13] IOTC_ER_TIMEOUT wyze-bridge | [indoor-living-room] [-13] IOTC_ER_TIMEOUT wyze-bridge | [master-bedroom-north] [-13] IOTC_ER_TIMEOUT wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Dining Room West on 10.0.20.68 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Indoor Living Room on 10.0.20.67 wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Master Bedroom North on 10.0.20.64 wyze-bridge | [living-room-west] [-13] IOTC_ER_TIMEOUT wyze-bridge | [living-room] [-13] IOTC_ER_TIMEOUT

Only thing I can think of that changed on my end was updating the app on iPad yesterday, but I can't see that affecting anything...

Thank you for the logs! Your iPad update is likely not the issue, it (what we appear to believe) seems be an API issue on the Wyze server end that is blocking the connection of our API auth keys,

@AaronMcGuirk007
Copy link
Author

I'm seeing the same thing, but I'm a Wyze Unlimited subscriber, so I don't think I would / should be restricted

don't think your subscriber access has anything to do with 3rd party access - you don't need a 3rd party ID and Key to use camplus or other wyze subscriptions - different access than 3rd parties.

This is a great point.

@hodgesp
Copy link

hodgesp commented Feb 21, 2025

This is the same error as another thread, try changing the WyzeBridge container networking from the default bridge mode to host mode. It means there may be port conflicts and is not ideal, but may be a workaround if this is the same issue with a different manifestation.

#1429

@isometimescode
Copy link

I just tested adding network_mode: host and all four of my cameras came back online.

@FeatherKing
Copy link

for me, host mode didnt solve the issue. My cameras are all on a different VLAN/subnet. Inside the container i do have connectivity to the cameras (via ping/nmap/netcat) but wyze-bridge still throws "IOTC_ER_TIMEOUT"

could be some logic to lock down to the same subnet. it wasnt a firmware update though, nothing has been updated here.

@hodgesp
Copy link

hodgesp commented Feb 21, 2025 •
edited
Loading

Yeah, that is another limitation. I think they are doing some blocking outside of the camera's vlan/subnet since host works but bridge and vlans do not work.

Hopefully someone smarter than me can sort it out.

@shawnsi
Copy link

shawnsi commented Feb 21, 2025

Yes @FeatherKing it does appear they need to be on the same exact network segment. Several users, myself included, found this to be the case and discussed in another bug issue filed.

In my case, I had to move all my cameras onto a new wifi radio that mapped to the same vlan as the server hosting docker-wyze-bridge. Also had to switch to host mode. Then it all came back online.

@FeatherKing
Copy link

so having the docker container on the same VLAN didnt work

networks:
macvlan_br0:
driver: macvlan
driver_opts:
parent: br0.100
ipam:
config:
- subnet: 10.0.1.0/24
gateway: 10.0.1.1
ip_range: 10.0.1.0/24

services:
wyze-bridge:
container_name: wyze-bridge
image: mrlt8/wyze-bridge:latest
restart: unless-stopped
networks:
- macvlan_br0

im not using host networking like this. let me try host network and moving one of the cameras to my main vlan

@talormanda
Copy link

@xcz011 - any update you can tell us about this ongoing issue?

@motoridersd
Copy link

My wyze-bridge docker container stopped being able to get video from my WyzeCam v3 after I did a firmware upgrade on my router/firewall (OPNSense) yesterday.

I don't know if the reboot causing all connections from the Wyze Camera to the cloud caused it to download a new set of policies that prevented the original network configuration in the docker container from working. It was using bridge mode/default before, but kept seeing timeouts in the logs.

Following some of the diagnostics in these threads, I added

    network_mode: "host"

to my stack and that allowed wyze-bridge to work again. I run it on an LXC container in Proxmox that has an IP in the same subnet as the camera, but when using the internal docker 172 subnet it was just not working anymore. WIth host mode turned on, wyze-bridge is now on the same broadcast domain/subnet as the camera.

@roverpixel
Copy link

Note to anybody that changes network_mode to host on a Docker host that also runs Frigate. Make sure you deconflict the ports such as 8554 and 5000.
For instance, if you start wyze-bridge second you will see

2025/03/01 16:32:24 ERR listen tcp :8554: bind: address already in use

@Nhscan
Copy link

Nhscan commented Mar 1, 2025

My wyze-bridge docker container stopped being able to get video from my WyzeCam v3 after I did a firmware upgrade on my router/firewall (OPNSense) yesterday.

I don't know if the reboot causing all connections from the Wyze Camera to the cloud caused it to download a new set of policies that prevented the original network configuration in the docker container from working. It was using bridge mode/default before, but kept seeing timeouts in the logs.

Following some of the diagnostics in these threads, I added

    network_mode: "host"

to my stack and that allowed wyze-bridge to work again. I run it on an LXC container in Proxmox that has an IP in the same subnet as the camera, but when using the internal docker 172 subnet it was just not working anymore. WIth host mode turned on, wyze-bridge is now on the same broadcast domain/subnet as the camera.

If you're not running your cameras on the same subnet using host mode you will not be able to view the cameras are you running cameras on different works and use VPNs on some of them and they're no longer working with host mode again this is not a fix by any means because a lot of people are running cameras not on the same networks especially when you're trying to keep your IoT stuff separate.

@Nhscan
Copy link

Nhscan commented Mar 1, 2025

I'm a Wyze engineer, and I want to address the concerns regarding the real-time preview issue. We’re aware of the problem and are actively working with our P2P provider to help resolve this issue.

In the meantime, please note the following:

  • No Firmware Changes: We have not released any firmware updates intended to block P2P connections via third-party plugins like this.
  • Investigation Underway: The issue seem related to our P2P provider, TUTK. We are in the process of working with them to understand whether there is a changes or not and will update you as soon as we have more information.

Thank you for your patience and understanding.

Okay then please push 2023 firmware to all my cameras! As they are unaffected and a lot of my cameras I can't even get to to put a memory card into flash it back. So obviously something has changed and we probably should figure it out and address it so we can move on past this. @wyze I have been very faithful and installing these cameras for many many people including myself prior to this I was using reolink which has no problem with home assistant or any other software you choose to use and their cloud service works flawlessly as well. I don't understand why with the amount of money we pay per year and where you are at as a company you can't listen to the people. Give us a way to at least update our cameras to whatever firmware we choose to use even if that's rolling back right now but give it to us through the app so we don't need to force it through a memory card. What would be even better is if you gave this handful of people a RTSP firmware for all our cameras then this way most people that are just buying your subscription and cameras won't even know about the alternative software and I would still continue to use your cloud service because I only want this for my home assistant portals really in my case.

@christcb03
Copy link

Has anyone gotten this fix to work on a QNAP NAS? I have tried all the suggestions I could find but so far just keep getting the error. [driveway-cam] [-13] IOTC_ER_TIMEOUT

I am using host network in the container settings and have the options set for Network_Mode: Host for environment settings.

@xcz011
Copy link

xcz011 commented Mar 3, 2025 •
edited
Loading

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

How to flash your Wyze Cam firmware manually

The last update to the TUTK SDK was in early 2024 to address some security issues. However, we’re still unsure why this problem has only recently started affecting the community.

We are still commit to find solution for this issue with everyone here.

Thanks so much for understanding !!!

Legal disclaimer:
While this is one possible workaround, Wyze is not recommending this approach, as reverting to an earlier firmware version will cause you to miss out on the latest bug fixes and important security updates. Any reversion to an earlier firmware version is done at your own risk.

@glenviewjeff
Copy link

glenviewjeff commented Mar 3, 2025 via email

@talormanda
Copy link

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

How to flash your Wyze Cam firmware manually

The last update to the TUTK SDK was in early 2024 to address some security issues. However, we’re still unsure why this problem has only recently started affecting the community.

We are still commit to find solution for this issue with everyone here.

Thanks so much for understanding !!!

Legal disclaimer: While this is one possible workaround, Wyze is not recommending this approach, as reverting to an earlier firmware version will cause you to miss out on the latest bug fixes and important security updates. Any reversion to an earlier firmware version is done at your own risk.

Once you figure out what changes in the firmware to undo / adjust, I do have all my cams enrolled in the beta firmware, so you could push that and I should be able to update all and test it. Just need to know what firmware # I need to be running to verify it's correct.

@DrVlikhell
Copy link

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

How to flash your Wyze Cam firmware manually

The last update to the TUTK SDK was in early 2024 to address some security issues. However, we’re still unsure why this problem has only recently started affecting the community.

We are still commit to find solution for this issue with everyone here.

Thanks so much for understanding !!!

Legal disclaimer: While this is one possible workaround, Wyze is not recommending this approach, as reverting to an earlier firmware version will cause you to miss out on the latest bug fixes and important security updates. Any reversion to an earlier firmware version is done at your own risk.

@xcz011 Last week I reverted some of my Wyze V3 cameras back to 4.36.11.7071 and that solved the issue. I know it's not the version you're asking about but it's the one directly after it, so maybe that will help? Previously I tried 4.36.11.8391 and that did not solve it. I will try 4.36.11.5859 on one of my cameras when I get some spare time. Thank you for your continued efforts!

@cheme75
Copy link

cheme75 commented Mar 3, 2025

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

How to flash your Wyze Cam firmware manually

The last update to the TUTK SDK was in early 2024 to address some security issues. However, we’re still unsure why this problem has only recently started affecting the community.

We are still commit to find solution for this issue with everyone here.

Thanks so much for understanding !!!

Legal disclaimer:
While this is one possible workaround, Wyze is not recommending this approach, as reverting to an earlier firmware version will cause you to miss out on the latest bug fixes and important security updates. Any reversion to an earlier firmware version is done at your own risk.

It would be most helpful if wyze would be able assist us doorbell non-sd card users like the v1 db3 cam to roll back fw either by signup to receive it like a beta or if there is a fw loader that can utilize the usb connection (unless the port is strictly for power without data).

@kenneallyh
Copy link

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

Jumping in to add that rolling back firmware also resolved the issue for my v2 cameras.

Wyze Cam v2

4.9.9.3006 (latest) = IOTC_ER_TIMEOUT errors, cannot connect to streams

4.9.9.2847 (Nov 2023) = Everything works, no timeout errors reported

@johnnyv5
Copy link

johnnyv5 commented Mar 3, 2025

I was able to resolve issues with all my cameras by installing the DWB addon that enabled host mode. I also had to revert changes made to my ubiquiti WiFi.

@Menz01
Copy link

Menz01 commented Mar 3, 2025

I was able to resolve issues with all my cameras by installing the DWB addon that enabled host mode. I also had to revert changes made to my ubiquiti WiFi.

what is the DWB addon?

@cto-mike
Copy link

cto-mike commented Mar 3, 2025

Wanted to add that switching to the host mode fork allowed snapshot jpg to work again but stream did not automatically work. Cameras (v1, v2, v4) were in a separate IoT subnet but worked fine previously with HA in another subnet. With the host mode true (thanks @jdeath) the cameras need to be directly on the network so added a usb wifi adapter to my Virtualbox running homeassistant. Now I had ethernet for the normal network and wifi for the IoT. Once IP to IoT subnet was available then generic camera RTSP video stream is working again.

Link to how to enable Wifi directly in Home Assistant:
https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md#enabling-wi-fi

@AngusNB
Copy link

AngusNB commented Mar 3, 2025

what is the DWB addon?

There is no addon, that I know of. There is a version of DWB with host mode already enabled. There is a link in this thread.

@johnnyv5
Copy link

johnnyv5 commented Mar 4, 2025 via email

@Menz01
Copy link

Menz01 commented Mar 4, 2025

Docker Wyze Bridge. There is a modified version that changes to host
mode. Installing that and changing settings on my ubiquiti WiFi worked for
me.
…

On Mon, Mar 3, 2025, 2:41 PM Menz01 @.***> wrote:
I was able to resolve issues with all my cameras by installing the DWB
addon that enabled host mode. I also had to revert changes made to my
ubiquiti WiFi.

what is the DWB addon?

—
Reply to this email directly, view it on GitHub
<#1432 (comment)>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQABPTTKERRQGS7XWMAU3D2STLCXAVCNFSM6AAAAABXTYS44OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVG4ZTCOJUGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
[image: Menz01]Menz01 left a comment (mrlt8/docker-wyze-bridge#1432)
<#1432 (comment)>

I was able to resolve issues with all my cameras by installing the DWB
addon that enabled host mode. I also had to revert changes made to my
ubiquiti WiFi.

what is the DWB addon?

—
Reply to this email directly, view it on GitHub
<#1432 (comment)>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQABPTTKERRQGS7XWMAU3D2STLCXAVCNFSM6AAAAABXTYS44OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVG4ZTCOJUGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

what did you have to change on your unifi router?

@johnnyv5
Copy link

johnnyv5 commented Mar 4, 2025

what did you have to change on your unifi router?

I disabled Multicast and Broadcast Control for the SSID.

@Littleaton
Copy link

Got a work around for home assistant people: Make sure you have the Samba Addon. From a windows machine go to: \\HA_IP\addons\ where HA_IP is your home assistant IP. Make a directory called docker_wyze_bridge or any name you want

download this config.yml file and put it in there: https://raw.githubusercontent.com/mrlt8/docker-wyze-bridge/refs/heads/main/home_assistant/config.yml

add the line: host_network: true above the ports: line.

Refresh addon store and install this version (you'll know its different because it doesn't have an icon) Go to your old one addon, stop it, copy the configuration as yaml (3 dots at top) paste config into new addon.

start new addon, everything works. Not sure if bad for security. Thanks for figuring out it is a a host network thing. Once I saw that, I looked at home assistant docs and noticed it was a parameter you can change in an add-on.

I did all that and still get this same error:

Image

@christcb03
Copy link

what did you have to change on your unifi router?

I disabled Multicast and Broadcast Control for the SSID.

I had already done all the host network settings with no luck, but as soon as I disabled this setting I am starting to get images again. Thank you!

@talormanda
Copy link

what did you have to change on your unifi router?

I disabled Multicast and Broadcast Control for the SSID.

I had already done all the host network settings with no luck, but as soon as I disabled this setting I am starting to get images again. Thank you!

I already have this disabled and it still doesn't work.

@chenjie
Copy link

chenjie commented Mar 6, 2025

4.49.3.4054 fixed the problem for my Wyze Cam Pan v2.

@twoolston60
Copy link

Which firmware version for the v4 cameras. I have 2 and both stopped working. My v3 cameras still work because they are on the rstp version.

@umairatstride
Copy link

Same issue, stopped working for Doorbell v2.
I've already changed all my other cams to Reolink because I couldn't deal with Wyze's approach to locking down their CAMS, I was using NET_MODE=LAN option in WyzeBridge to make sure that I connect to it only via lan and not through Wyze.
Unfortunately I still use the Wyze FrontDoor bell v2 and the reason is I haven't switched to something else is because Reolink isn't giving me a good option yet, I need wired power (not battery) and works with Existing mechanical chime, please correct me if I am wrong but they don't have this combination yet.
It's like I am being forced to find an alternative now :(

Try downgrading the firmware to something from 2023 for your doorbell, at least until you can find a suitable replacement. That's what I did to get my V3 cams working since I run Docker Desktop in Windows and host mode networking is not a working solution for that scenario.

For a replacement doorbell, there are poe solutions for that, but for the existing mechanical chime, if you run Home Assistant like many here do, or some other home automation system, I would connect a smart switch/iot relay to the existing doorbell chime and have it trigger on the button press for the doorbell camera.

Where can I get the older firmware for DBV2? Porfa

@WarrenSchultz
Copy link

@xcz011

I flashed this version on a v3 cam, and it has resolved the issue. This camera is also on my dedicated camera VLAN, which is why applying the Docker container networking change didn't resolve the issue.

Thanks for looking into this. Hopefully it can be sorted out soon.

Also, I'd like to request that (as someone who is a Cam Unlimited subscriber) that Wyze extend its other firmware types to support LAN connectivity, so that WB and other projects can stream locally without internet bandwidth usage for continuous operation.

Sorry for the delayed response. We’ve been working hard over the past week to understand how this issue occurred.

I’d like to ask for some help—could anyone try reverting their V3 firmware back to 4.36.11.5859 to see if it resolves the issue?

How to flash your Wyze Cam firmware manually

The last update to the TUTK SDK was in early 2024 to address some security issues. However, we’re still unsure why this problem has only recently started affecting the community.

We are still commit to find solution for this issue with everyone here.

Thanks so much for understanding !!!

Legal disclaimer: While this is one possible workaround, Wyze is not recommending this approach, as reverting to an earlier firmware version will cause you to miss out on the latest bug fixes and important security updates. Any reversion to an earlier firmware version is done at your own risk.

@talormanda
Copy link

@xcz011 - any update to this problem?

@jsanox
Copy link

jsanox commented Mar 20, 2025

any updates on this? still same issues with my v4

@HomeAssistbs
Copy link

HomeAssistbs commented Mar 21, 2025 via email

@albi-t albi-t mentioned this issue Mar 24, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests