BUG: IOTC_ER_TIMEOUT

[recoveringlawyer]

Describe the bug

I have seen a lot of action on this topic, but no solutions that work for me (and I assume for other non-expert users). I would like to be comforted that this will be resolved, so I must ask, mrlt8, are you working on this? Please say yes!

Thanks!

Affected Bridge Version

V2.10.3

Bridge type

Docker Run/Compose

Affected Camera(s)

No response

Affected Camera Firmware

No response

docker-compose or config (if applicable)

[LEOBOESE]

i was having the same problem so i downgraded my wyze pan v3 to firmware 4.50.4.7252 and the live video started working again

[marciogranzotto]

I have the same issue, with my Wyze Cam Pan on fw 4.10.9.3006

[tabooki]

Also having this issue. Firmware 4.36.13.0416. Wyzecam v3

[Peter919pan]

Same here with firmware 4.36.13.0416 wyzecam v3

But my another v2 having old firmware (4.28.4.49) which support rtsp works fine

[LEOBOESE]

Also having this issue. Firmware 4.36.13.0416. Wyzecam v3

Install the rtsp firmware, I have a v3 with rtsp firmware 4.61.0.1 and works fine here.

https://download.wyzecam.com/firmware/rtsp/demo_v3_RTSP_4.61.0.1.zip

https://support.wyze.com/hc/en-us/articles/360051619871-Does-Wyze-Cam-v3-support-RTSP

[Peter919pan]

v3 with rtsp firmware 4.61.0.1 doesn't work to me.

Problem fixed by v3 firmware v.4.36.11.7071

https://download.wyzecam.com/firmware/v3/demo_wcv3_4.36.11.7071.bin.zip

[albi-t]

Upgraded my v2 cam's firmware to 4.9.9.3006 and it stopped working. Getting the same error ([-13] IOTC_ER_TIMEOUT)

The rest of the cams are still working fine since I didn't upgrade their firmware, still on 4.9.9.2351.

[albi-t]

Upgraded my v2 cam's firmware to 4.9.9.3006 and it stopped working. Getting the same error ([-13] IOTC_ER_TIMEOUT)

The rest of the cams are still working fine since I didn't upgrade their firmware, still on 4.9.9.2351.

Used the fork from @jdeath #1432 (comment) and it worked

[Abcmsaj]

Looks like it may be related to the firmware update (there’s a Wyze engineer on that thread that asks people to rollback to November 2024 firmware and it solves the problem.

But Jdeath’s fix for the HomeAssistant addon (turning on host mode) works well for now. I also use Tailscale on my server so that may be why the cameras aren’t reachable with the default addon anymore

[blueharford]

is there a fix for this when running in unraid? and not just HASS?

[letrain02]

Yup. I've posted before. Unsure how to link to it. Select br0 interface, assign an IP address that is in the same subnet. It's been working fine for me. Even webrtc works.

is there a fix for this when running in unraid? and not just HASS?

[brianchesko]

But Jdeath’s fix for the HomeAssistant addon (turning on host mode) works well for now. I also use Tailscale on my server so that may be why the cameras aren’t reachable with the default addon anymore

I'm running under WSL2 and found a StackOverflow post that mentioned support for a new "mirrored" mode that I had to enable in addition to host networking, which ended up working. See https://learn.microsoft.com/en-us/windows/wsl/networking#mirrored-mode-networking or https://superuser.com/a/1830244

Though I don't love the use of host networking in the first place... kind of removes some of the security Docker is offering.

[Flyinace2000]

Yup. I've posted before. Unsure how to link to it. Select br0 interface, assign an IP address that is in the same subnet. It's been working fine for me. Even webrtc works.

is there a fix for this when running in unraid? and not just HASS?

Really? No luck for my cameras. Docker is running on the same subnet as the camera's and the hub. Even if my laptop is on the same subnet I get the same errors

[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/driveway.jpg HTTP/1.1" 304 -
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 -
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/patio.jpg HTTP/1.1" 304 -
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/front-yard.jpg HTTP/1.1" 304 -
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/back-yard-cam.jpg HTTP/1.1" 304 -
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:10] "GET /img/driveway.jpg HTTP/1.1" 304 -
[driveway] [-13] IOTC_ER_TIMEOUT
[back-yard-cam] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] [CONTROL] SET patio state=start
[WyzeBridge] 🎉 Connecting to WyzeCam V4 - Patio on 10.0.3.129
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:12] "GET /api/patio/start HTTP/1.1" 200 -
[patio] [-90] IOTC_ER_DEVICE_OFFLINE
[WyzeBridge] 👻 Patio is offline.
[WyzeBridge] Patio will cooldown for 10s.
[WyzeBridge] ⏰ Timed out connecting to Front Yard.
[WyzeBridge] [CONTROL] SET front-yard state=start
[front-yard] [-13] IOTC_ER_TIMEOUT
[WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Yard on 10.0.3.128
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:15] "GET /api/front-yard/start HTTP/1.1" 200 -
[WyzeBridge] [CONTROL] SET back-yard-cam state=start
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard Cam on 10.0.3.104
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:16] "GET /api/back-yard-cam/start HTTP/1.1" 200 -
[WyzeBridge] [CONTROL] SET driveway state=start
[WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - Driveway on 10.0.3.148
[WyzeBridge] 10.0.3.111 - - [30/Mar/2025 20:42:17] "GET /api/driveway/start HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V4 - Patio on 10.0.3.129
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard Cam on 10.0.3.104
[WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Yard on 10.0.3.128
[WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - Driveway on 10.0.3.148
[patio] [-90] IOTC_ER_DEVICE_OFFLINE
[WyzeBridge] 👻 Patio is offline.
[WyzeBridge] Patio will cooldown for 10s.