Wyze V4 and V3Pro: IOTC_ER_TIMEOUT

[Flyinace2000]

Does this fork solve the IOTC_ER_TIMEOUT issues?

I've installed the latest but still get the error. Assume it's something on Wyze's end, but was hopefully when I saw this fork that you had a workaround.

Thanks

wyze-bridge | 2025/05/07 00:44:56 INF [RTSP] [conn 127.0.0.1:58322] opened
wyze-bridge | 2025/05/07 00:44:56 INF [path patio] runOnDemand command started
wyze-bridge | [WyzeBridge] [patio] Snapshot timed out
wyze-bridge | [WyzeBridge] 10.0.1.121 - - [07/May/2025 00:45:11] "GET /snapshot/patio.jpg?1746578695771 HTTP/1.1" 200 -
wyze-bridge | [patio] [-13] IOTC_ER_TIMEOUT
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Patio on 10.0.3.160
wyze-bridge | 2025/05/07 00:45:25 INF [RTSP] [conn 127.0.0.1:36466] opened
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Yard on 10.0.3.128
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - Driveway on 10.0.3.108
wyze-bridge | 2025/05/07 00:45:25 INF [RTSP] [conn 127.0.0.1:36482] opened
wyze-bridge | 2025/05/07 00:45:25 INF [path front-yard] runOnDemand command started
wyze-bridge | 2025/05/07 00:45:25 INF [RTSP] [conn 127.0.0.1:36484] opened
wyze-bridge | 2025/05/07 00:45:25 INF [path driveway] runOnDemand command started
wyze-bridge | 2025/05/07 00:45:26 INF [path patio] runOnDemand command stopped: timed out
wyze-bridge | 2025/05/07 00:45:26 INF [path patio] runOnUnDemand command launched
wyze-bridge | 2025/05/07 00:45:26 INF [RTSP] [conn 127.0.0.1:36466] closed: source of path 'patio' has timed out
wyze-bridge | 2025/05/07 00:45:26 INF [RTSP] [conn 127.0.0.1:58322] closed: source of path 'patio' has timed out
wyze-bridge | Error opening input files: Server returned 400 Bad Request
wyze-bridge | [WyzeBridge] 10.0.1.121 - - [07/May/2025 00:45:26] "GET /snapshot/patio.jpg?1746578725848 HTTP/1.1" 200 -
wyze-bridge | [front-yard] [-90] IOTC_ER_DEVICE_OFFLINE
wyze-bridge | [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Patio on 10.0.3.160
wyze-bridge | [WyzeBridge] 👻 Front Yard is offline.
wyze-bridge | [WyzeBridge] Front Yard will cooldown for 10s.
wyze-bridge | 2025/05/07 00:45:27 INF [RTSP] [conn 127.0.0.1:36486] opened
wyze-bridge | 2025/05/07 00:45:27 INF [path patio] runOnDemand command started

[IDisposable]

I don't have a V4 to test against, but probably NOT a fix for that yet. One suggestion is to make sure your router is allowing broadcast traffic.

[IDisposable]

Comments on the main repo say it might, please let me know @Flyinace2000

[ShadowBlade72]

The workaround I found was to set network_mode: host and comment out all port mappings.

If someone finds something more graceful, let me know.

REF: WYZE v4 ver 4.52.9.1134 #1466

services:
    wyze-bridge:
        container_name: iwyze-bridge
        restart: unless-stopped
        image: idisposablegithub365/wyze-bridge:latest
        network_mode: host
          #ports:
          #- 1935:1935 # RTMP rtmp://localhost:1935/mystream?user=myuser&pass=mypass
          #- 1936:1936 # RTMP rtmp://localhost:1936/mystream?user=myuser&pass=mypass
          #- 2935:2935 # RTMPS rtmps://localhost:2935/mystream?user=myuser&pass=mypass
          #- 2936:2936 # RTMPS rtmps://localhost:2936/mystream?user=myuser&pass=mypass
          #- 8189:8189/udp # WebRTC/ICE UDP
          #- 8322:8322 # TCP/TLS/RTSPS rtsps://localhost:8322/mystream
          #- 8554:8554 # RTSP rtsp://localhost:8554/mystream
          #- 8888:8888 # HLS http://localhost:8888/mystream
          #- 8889:8889 # WebRTC http://localhost:8889/mystream and http://localhost:8889/mystream/whep
          #- 8890:8890/udp # SRT UDP srt://localhost:8890?streamid=read:mystream:myuser:mypass
          #- 5000:5000 # WEB-UI http://localhost:5000/mystream

[IDisposable]

I'm no longer seeing any IOTC_ER_TIMEOUT in 3.10.9

[Flyinace2000]

I probably messed something up with my compose file (hosting in unRaid). Container comes up, I get a snapshot (old one), but no video and same timeout error.

services:
    wyze-bridge:
        container_name: wyze-bridge
        restart: unless-stopped
        image: idisposablegithub365/wyze-bridge:latest
        dns:
          - 10.0.3.1
          - 1.1.1.1
          - 1.0.0.1
        networks:
            br0.20:
                ipv4_address: 10.0.3.5
        environment:
            - WYZE_EMAIL=***********@**********.com
            - WYZE_PASSWORD=**********
            - API_ID=DDDDEEEFFFGGGG
            - API_KEY=AAAABBBBBCCCC
            - WB_IP=10.0.3.5
            - WB_AUTH=False
            # - WB_USERNAME=
            # - WB_PASSWORD=

networks:
    br0.20:
        external: true

[IDisposable]

Warning, I've not maintained the unraid\docker-wyze-bridge.xml file in any way since forking the repo as it was already woefully out of date.

I can get that synched up with the config.yml file if that would be helpful.

[Jeppedy]

I'm getting the exact same behavior but for ALL my cameras. I thought this is exactly the issue this fork was meant to resolve. Any ideas?
I'm running 3.10.9 under HAOS
Wyze Cams: A mix of versions

• Wyze Doorbell : Front Doorbell 2
• v3 Cam : Front Cam v3
• v2 Cam : Basement v2
  Do I need to change my Docker config from the standard addon install?

Log Snippet, below:
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:04] "GET /snapshot/lake-boat-cam.jpg?1748268650103 HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - East Cam on 192.168.3.147
2025/05/26 09:11:04 INF [RTSP] [conn 127.0.0.1:53216] opened
2025/05/26 09:11:04 INF [path east-cam] runOnDemand command started
[WyzeBridge] Received event: start for east-cam
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage Cam on 192.168.3.30
2025/05/26 09:11:04 INF [RTSP] [conn 127.0.0.1:53226] opened
2025/05/26 09:11:04 INF [path garage-cam] runOnDemand command started
[WyzeBridge] Received event: start for garage-cam
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:04] "GET /snapshot/starter-cam.jpg?1748268650103 HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:04] "GET /snapshot/front-cam-v3.jpg?1748268650104 HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard v3 on 192.168.3.88
2025/05/26 09:11:04 INF [RTSP] [conn 127.0.0.1:53234] opened
2025/05/26 09:11:04 INF [path back-yard-v3] runOnDemand command started
[WyzeBridge] Received event: start for back-yard-v3
[WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Front Doorbell 2 on 192.168.3.162
2025/05/26 09:11:04 INF [RTSP] [conn 127.0.0.1:53244] opened
2025/05/26 09:11:04 INF [path front-doorbell-2] runOnDemand command started
[WyzeBridge] [makerspace-cam] Snapshot timed out
2025/05/26 09:11:04 INF [RTSP] [conn 127.0.0.1:38570] closed: EOF
2025/05/26 09:11:04 INF [RTSP] [session aff46218] runOnRead command stopped
2025/05/26 09:11:04 INF [RTSP] [session aff46218] runOnUnread command launched
2025/05/26 09:11:04 INF [RTSP] [session aff46218] destroyed: not in use
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:05] "GET /snapshot/makerspace-cam.jpg?1748268650105 HTTP/1.1" 307 -
[WyzeBridge] Received event: start for front-doorbell-2
[WyzeBridge] Received event: Unread for makerspace-cam
[WyzeBridge] 📕 Client stopped reading from makerspace-cam
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard Cam on 192.168.3.111
2025/05/26 09:11:05 INF [RTSP] [conn 127.0.0.1:53258] opened
2025/05/26 09:11:05 INF [path back-yard-cam] runOnDemand command started
[WyzeBridge] Received event: start for back-yard-cam
[carolyn-cam] [-13] IOTC_ER_TIMEOUT
[front-cam-v3] [-13] IOTC_ER_TIMEOUT
[lake-boat-cam] [-13] IOTC_ER_TIMEOUT
2025/05/26 09:11:17 INF [RTSP] [conn 127.0.0.1:48410] closed: read tcp 127.0.0.1:8554->127.0.0.1:48410: i/o timeout
2025/05/26 09:11:17 INF [path makerspace-cam] runOnReady command stopped
2025/05/26 09:11:17 INF [path makerspace-cam] runOnNotReady command launched
2025/05/26 09:11:17 INF [RTSP] [session d1e26e02] destroyed: not in use
[WyzeBridge] Received event: NotReady for makerspace-cam
[makerspace-cam] [IOTC] Audio pipe closed
2025/05/26 09:11:17 INF [RTSP] [conn 127.0.0.1:48610] opened
2025/05/26 09:11:17 INF [RTSP] [session 78d037fa] created by 127.0.0.1:48610
2025/05/26 09:11:17 INF [path makerspace-cam] runOnReady command started
2025/05/26 09:11:17 INF [RTSP] [session 78d037fa] is publishing to path 'makerspace-cam', 2 tracks (H264, G711)
2025/05/26 09:11:17 INF [path makerspace-cam] runOnReady command stopped
2025/05/26 09:11:17 INF [path makerspace-cam] runOnNotReady command launched
2025/05/26 09:11:17 INF [RTSP] [session 78d037fa] destroyed: torn down by 127.0.0.1:48610
2025/05/26 09:11:17 INF [RTSP] [conn 127.0.0.1:48610] closed: EOF
[makerspace-cam] [TUTK] Stream stopped
[WyzeBridge] ❌ '/makerspace-cam' stream is down
[WyzeBridge] Received event: NotReady for makerspace-cam
[WyzeBridge] ❌ '/makerspace-cam' stream is down
2025/05/26 09:11:18 INF [path carolyn-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:18 INF [path carolyn-cam] runOnUnDemand command launched
2025/05/26 09:11:18 INF [RTSP] [conn 127.0.0.1:38530] closed: source of path 'carolyn-cam' has timed out
[WyzeBridge] Received event: stop for carolyn-cam
2025/05/26 09:11:19 INF [path lake-boat-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:19 INF [path lake-boat-cam] runOnUnDemand command launched
2025/05/26 09:11:19 INF [RTSP] [conn 127.0.0.1:38544] closed: source of path 'lake-boat-cam' has timed out
[WyzeBridge] Received event: stop for lake-boat-cam
2025/05/26 09:11:19 INF [path starter-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:19 INF [path starter-cam] runOnUnDemand command launched
2025/05/26 09:11:19 INF [RTSP] [conn 127.0.0.1:38550] closed: source of path 'starter-cam' has timed out
[WyzeBridge] Received event: stop for starter-cam
2025/05/26 09:11:19 INF [path front-cam-v3] runOnDemand command stopped: timed out
2025/05/26 09:11:19 INF [path front-cam-v3] runOnUnDemand command launched
2025/05/26 09:11:19 INF [RTSP] [conn 127.0.0.1:38554] closed: source of path 'front-cam-v3' has timed out
[WyzeBridge] Received event: stop for front-cam-v3
[WyzeBridge] [east-cam] Snapshot timed out
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:19] "GET /snapshot/east-cam.jpg?1748268650105 HTTP/1.1" 200 -
[WyzeBridge] [garage-cam] Snapshot timed out
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - Basement v2 on 192.168.3.100
2025/05/26 09:11:19 INF [RTSP] [conn 127.0.0.1:48614] opened
2025/05/26 09:11:19 INF [path basement-v2] runOnDemand command started
[WyzeBridge] Received event: start for basement-v2
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:19] "GET /snapshot/garage-cam.jpg?1748268650105 HTTP/1.1" 200 -
[WyzeBridge] [back-yard-v3] Snapshot timed out
[WyzeBridge] [front-doorbell-2] Snapshot timed out
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:19] "GET /snapshot/back-yard-v3.jpg?1748268650106 HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /snapshot/front-doorbell-2.jpg?1748268650106 HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /img/west-side-cam.jpg HTTP/1.1" 304 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /img/loading.svg HTTP/1.1" 307 -
[WyzeBridge] [back-yard-cam] Snapshot timed out
[WyzeBridge] [CONTROL] ☁️ get_device_Info for wyze-cam-outdoor via Wyze API
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /img/wyze-cam-outdoor.jpg HTTP/1.1" 307 -
[WyzeBridge] [CONTROL] ☁️ get_device_Info for west-side-cam via Wyze API
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /snapshot/back-yard-cam.jpg?1748268650107 HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /signaling/starter-cam?webrtc HTTP/1.1" 200 -
2025/05/26 09:11:20 INF [WebRTC] [session 810d5d8b] created by 192.168.2.233:63004
2025/05/26 09:11:20 INF [path starter-cam] runOnDemand command started
[WyzeBridge] Received event: start for starter-cam
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Starter Cam on 192.168.3.28
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /api/west-side-cam/battery HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /api/wyze-cam-outdoor/battery HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:20] "GET /signaling/carolyn-cam?webrtc HTTP/1.1" 200 -
2025/05/26 09:11:20 INF [WebRTC] [session 6a082e6d] created by 192.168.2.233:63009
2025/05/26 09:11:20 INF [path carolyn-cam] runOnDemand command started
[WyzeBridge] Received event: start for carolyn-cam
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Carolyn Cam on 10.0.0.98
[WyzeBridge] [CONTROL] ☁️ get_device_Info for wyze-cam-outdoor via Wyze API
[WyzeBridge] [CONTROL] ☁️ get_device_Info for wyze-cam-outdoor via Wyze API
[WyzeBridge] [CONTROL] ☁️ get_device_Info for west-side-cam via Wyze API
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/makerspace-cam HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/wyze-cam-outdoor/battery HTTP/1.1" 200 -
[WyzeBridge] [CONTROL] ☁️ get_device_Info for west-side-cam via Wyze API
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/wyze-cam-outdoor/battery HTTP/1.1" 200 -
[WyzeBridge] [CONTROL] ☁️ get_device_Info for wyze-cam-outdoor via Wyze API
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/west-side-cam/battery HTTP/1.1" 200 -
[WyzeBridge] [CONTROL] ☁️ get_device_Info for west-side-cam via Wyze API
[starter-cam] [-90] IOTC_ER_DEVICE_OFFLINE
2025/05/26 09:11:21 INF [RTSP] [conn 127.0.0.1:48628] opened
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/west-side-cam/battery HTTP/1.1" 200 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:21] "GET /api/wyze-cam-outdoor/battery HTTP/1.1" 200 -
[WyzeBridge] 👻 Starter Cam is offline.
[WyzeBridge] Starter Cam will cooldown for 10s.
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:22] "GET /api/west-side-cam/battery HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V2 - Lake Boat Cam on 192.168.1.219
2025/05/26 09:11:22 INF [RTSP] [conn 127.0.0.1:48640] opened
2025/05/26 09:11:22 INF [path lake-boat-cam] runOnDemand command started
[WyzeBridge] Received event: start for lake-boat-cam
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:22] "GET /snapshot/starter-cam.jpg?1748268680111 HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Front Cam v3 on 192.168.3.215
2025/05/26 09:11:22 INF [RTSP] [conn 127.0.0.1:48646] opened
2025/05/26 09:11:22 INF [path front-cam-v3] runOnDemand command started
[WyzeBridge] Received event: start for front-cam-v3
[WyzeBridge] 🎉 Connecting to WyzeCam V1 - MakerSpace Cam on 192.168.3.37
2025/05/26 09:11:22 INF [RTSP] [conn 127.0.0.1:48658] opened
[garage-cam] [-13] IOTC_ER_TIMEOUT
[front-doorbell-2] [-13] IOTC_ER_TIMEOUT
[back-yard-v3] [-13] IOTC_ER_TIMEOUT
[east-cam] [-13] IOTC_ER_TIMEOUT
[back-yard-cam] [-13] IOTC_ER_TIMEOUT
[makerspace-cam] 📡 Getting 180kb/s HD stream (h264/10fps) via LAN mode (WiFi: 0%) FW: 3.9.4.35
[makerspace-cam] 🔊 Audio Enabled [Source=S16LE/8,000Hz]
[makerspace-cam] [AUDIO] Re-Encode for RTSP compatibility [codec_out='pcm_mulaw']
2025/05/26 09:11:29 INF [RTSP] [conn 127.0.0.1:54592] opened
2025/05/26 09:11:29 INF [RTSP] [session f8ef9009] created by 127.0.0.1:54592
2025/05/26 09:11:29 INF [path makerspace-cam] runOnReady command started
2025/05/26 09:11:29 INF [RTSP] [session f8ef9009] is publishing to path 'makerspace-cam', 2 tracks (H264, G711)
2025/05/26 09:11:29 INF [RTSP] [session de843e39] created by 127.0.0.1:48658
2025/05/26 09:11:29 INF [RTSP] [session de843e39] is reading from path 'makerspace-cam', with TCP, 2 tracks (H264, G711)
2025/05/26 09:11:29 INF [RTSP] [session de843e39] runOnRead command started
[WyzeBridge] Received event: Ready for makerspace-cam
[WyzeBridge] ✅ '/makerspace-cam stream is UP! (3/3)
[WyzeBridge] Received event: Read for makerspace-cam
[WyzeBridge] 📖 New client reading from makerspace-cam
[makerspace-cam] [video] super slow
[makerspace-cam] WARNING: clear buffer
2025/05/26 09:11:34 INF [path east-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:34 INF [path east-cam] runOnUnDemand command launched
2025/05/26 09:11:34 INF [RTSP] [conn 127.0.0.1:53216] closed: source of path 'east-cam' has timed out
[WyzeBridge] Received event: stop for east-cam
2025/05/26 09:11:34 INF [path garage-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:34 INF [path garage-cam] runOnUnDemand command launched
2025/05/26 09:11:34 INF [RTSP] [conn 127.0.0.1:53226] closed: source of path 'garage-cam' has timed out
[WyzeBridge] Received event: stop for garage-cam
[WyzeBridge] [basement-v2] Snapshot timed out
2025/05/26 09:11:34 INF [path back-yard-v3] runOnDemand command stopped: timed out
2025/05/26 09:11:34 INF [path back-yard-v3] runOnUnDemand command launched
2025/05/26 09:11:34 INF [RTSP] [conn 127.0.0.1:53234] closed: source of path 'back-yard-v3' has timed out
[WyzeBridge] Received event: stop for back-yard-v3
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:34] "GET /snapshot/basement-v2.jpg?1748268650107 HTTP/1.1" 200 -
2025/05/26 09:11:34 INF [path front-doorbell-2] runOnDemand command stopped: timed out
2025/05/26 09:11:34 INF [path front-doorbell-2] runOnUnDemand command launched
2025/05/26 09:11:34 INF [RTSP] [conn 127.0.0.1:53244] closed: source of path 'front-doorbell-2' has timed out
[WyzeBridge] Received event: stop for front-doorbell-2
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - East Cam on 192.168.3.147
2025/05/26 09:11:34 INF [RTSP] [conn 127.0.0.1:60876] opened
2025/05/26 09:11:35 INF [path east-cam] runOnDemand command started
[WyzeBridge] Received event: start for east-cam
2025/05/26 09:11:35 INF [path back-yard-cam] runOnDemand command stopped: timed out
2025/05/26 09:11:35 INF [path back-yard-cam] runOnUnDemand command launched
2025/05/26 09:11:35 INF [RTSP] [conn 127.0.0.1:53258] closed: source of path 'back-yard-cam' has timed out
[WyzeBridge] Received event: stop for back-yard-cam
[WyzeBridge] [carolyn-cam] Snapshot timed out
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:36] "GET /snapshot/carolyn-cam.jpg?1748268680111 HTTP/1.1" 200 -
[WyzeBridge] [lake-boat-cam] Snapshot timed out
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Garage Cam on 192.168.3.30
2025/05/26 09:11:37 INF [RTSP] [conn 127.0.0.1:60880] opened
2025/05/26 09:11:37 INF [path garage-cam] runOnDemand command started
[WyzeBridge] Received event: start for garage-cam
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:37] "GET /snapshot/lake-boat-cam.jpg?1748268680111 HTTP/1.1" 200 -
[WyzeBridge] [front-cam-v3] Snapshot timed out
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard v3 on 192.168.3.88
2025/05/26 09:11:37 INF [RTSP] [conn 127.0.0.1:60890] opened
2025/05/26 09:11:37 INF [path back-yard-v3] runOnDemand command started
[WyzeBridge] Received event: start for back-yard-v3
[WyzeBridge] [makerspace-cam] Snapshot timed out
2025/05/26 09:11:37 INF [RTSP] [session de843e39] runOnRead command stopped
2025/05/26 09:11:37 INF [RTSP] [session de843e39] runOnUnread command launched
2025/05/26 09:11:37 INF [RTSP] [conn 127.0.0.1:48658] closed: EOF
2025/05/26 09:11:37 INF [RTSP] [session de843e39] destroyed: not in use
[WyzeBridge] Received event: Unread for makerspace-cam
[WyzeBridge] 📕 Client stopped reading from makerspace-cam
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:37] "GET /snapshot/makerspace-cam.jpg?1748268680113 HTTP/1.1" 307 -
[WyzeBridge] 192.168.2.233 - - [26/May/2025 09:11:37] "GET /snapshot/front-cam-v3.jpg?1748268680113 HTTP/1.1" 200 -
[WyzeBridge] 🎉 Connecting to WyzeCam Doorbell - Front Doorbell 2 on 192.168.3.162
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Yard Cam on 192.168.3.111
2025/05/26 09:11:37 INF [RTSP] [conn 127.0.0.1:60896] opened
2025/05/26 09:11:37 INF [path front-doorbell-2] runOnDemand command started
[WyzeBridge] Received event: start for front-doorbell-2
2025/05/26 09:11:37 INF [RTSP] [conn 127.0.0.1:60902] opened
2025/05/26 09:11:37 INF [path back-yard-cam] runOnDemand command started
[WyzeBridge] Received event: start for back-yard-cam
[basement-v2] [-13] IOTC_ER_TIMEOUT

[IDisposable]

"This issue" being what specifically? All my cameras (v3) work fine, the v4 has never (yet) worked and I don't have one to test against, and I am working on getting the Doorbell Pro working right now.

I still can't get MediaMTX to emit recorded files yet, I am going to have to resolve that later if we need other things more urgently.

This fork was made public because the original stopped merging PRs (life gets busy), so I merged as many as I can get working, one by one.

[Jeppedy]

Oh, sorry... The IoT timeout error is still happening in this fork. I'm using, as mentioned below, V1 and V3 cams. See log. If you have any ideas, i'd appreciate it. *"What good is it for a man to gain the whole world, yet forfeit his soul?"* - *Mark 8:36 <http://christianbookshelf.org/spurgeon/spurgeons_sermons_volume_2_1856/profit_and_loss.htm>*

…

On Mon, May 26, 2025, 13:48 Marc Brooks ***@***.***> wrote: *IDisposable* left a comment (IDisposable/docker-wyze-bridge#20) <#20 (comment)> "This issue" being what specifically? All my cameras (v3) work fine, the v4 has never (yet) worked and I don't have one to test against, and I am working on getting the Doorbell Pro working right now. I still can't get MediaMTX to emit recorded files yet, I am going to have to resolve that later if we need other things more urgently. This fork was made public because the original stopped merging PRs (life gets busy), so I merged as many as I can get working, one by one. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB32XY73MLK2O7UT2V3FW6L3ANOWFAVCNFSM6AAAAAB4SQV7P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJQGQ2DMMZRGI> . You are receiving this because you commented.Message ID: ***@***.***>

[ShadowBlade72]

"This issue" being what specifically? All my cameras (v3) work fine, the v4 has never (yet) worked and I don't have one to test against, and I am working on getting the Doorbell Pro working right now.

I still can't get MediaMTX to emit recorded files yet, I am going to have to resolve that later if we need other things more urgently.

This fork was made public because the original stopped merging PRs (life gets busy), so I merged as many as I can get working, one by one.

The difference in users having issues is likely down to the config file they're using due to the platform they're hosting on. Docker based installations no longer work (at least from user reporting and my experience) without setting network_mode: host. The configuration files should be updated to reflect that.

From my understanding Wyze made a change to restrict viewing cameras to devices on the same network. Due to docker wizardry that I didn't feel like reading into, this necessitated setting network_mode: host for those deployments.

I see that the HAOS config example already has this set, thus it should work.

I submitted a pull request that should resolve the config for installs in the future.

[Jeppedy]

Should work... And yet, it does not. So frustrating. I'm a tech geek, but I need a little something to point me in the right direction here. I appreciate any info you all can share. I keep hearing from people "it works for me", but it quite clearly flat-out does not work for me. :-(

…

On Mon, May 26, 2025, 16:48 ShadowBlade72 ***@***.***> wrote: *ShadowBlade72* left a comment (IDisposable/docker-wyze-bridge#20) <#20 (comment)> "This issue" being what specifically? All my cameras (v3) work fine, the v4 has never (yet) worked and I don't have one to test against, and I am working on getting the Doorbell Pro working right now. I still can't get MediaMTX to emit recorded files yet, I am going to have to resolve that later if we need other things more urgently. This fork was made public because the original stopped merging PRs (life gets busy), so I merged as many as I can get working, one by one. The difference in users having issues is likely down to the config file they're using due to the platform they're hosting on. Docker based installations no longer work (at least from user reporting and my experience) without setting network_mode: host. The configuration files should be updated to reflect that. From my understanding Wyze made a change to restrict viewing cameras to devices on the same network. Due to docker wizardry that I didn't feel like reading into, this necessitated setting network_mode: host for those deployments. I see that the HAOS config example already has this set, thus it should work. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB32XY3EVKDSJGDEDJBRFXT3AOD3ZAVCNFSM6AAAAAB4SQV7P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJQGY3TENJVGI> . You are receiving this because you commented.Message ID: ***@***.***>

[SireSalty]

My v3 and V4 cameras with a fresh docker install do not seem to be working. my V3's show an old image (2-12 hours old) only and it doesn't change.

[SireSalty]

[front-porch-cam is v3
[front-porch-camclear] is v4

error examples:
[front-porch-cam] [-13] IOTC_ER_TIMEOUT
[front-porch-camclear] [-13] IOTC_ER_TIMEOUT

[WyzeBridge] ? Connecting to WyzeCam V3 - Garage on 192.168.0.180
2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55504] opened
2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55512] opened
2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55520] opened
2025/05/29 13:40:04 INF [path front-porch-cam] runOnDemand command stopped: timed out
Error opening input files: Server returned 400 Bad Request
2025/05/29 13:40:04 INF [path front-porch-cam] runOnUnDemand command launched
2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:52874] closed: source of path 'front-porch-cam' has timed out

[WyzeBridge] [API] ERROR pulling thumbnail?[HTTPError] 401 Client Error: for url: https://prod-sight-safe-auth.wyze.com/

[Jeppedy]

Are you sure 1) they are on the same subnet, and 2) that you have the network mode set to host in Docker? *"What good is it for a man to gain the whole world, yet forfeit his soul?"* - *Mark 8:36 <http://christianbookshelf.org/spurgeon/spurgeons_sermons_volume_2_1856/profit_and_loss.htm>*

…

On Thu, May 29, 2025, 08:42 SireSalty ***@***.***> wrote: *SireSalty* left a comment (IDisposable/docker-wyze-bridge#20) <#20 (comment)> [front-porch-cam is v3 [front-porch-camclear] is v4 error examples: [front-porch-cam] [-13] IOTC_ER_TIMEOUT [front-porch-camclear] [-13] IOTC_ER_TIMEOUT [WyzeBridge] ? Connecting to WyzeCam V3 - Garage on 192.168.0.180 2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55504] opened 2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55512] opened 2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:55520] opened 2025/05/29 13:40:04 INF [path front-porch-cam] runOnDemand command stopped: timed out Error opening input files: Server returned 400 Bad Request 2025/05/29 13:40:04 INF [path front-porch-cam] runOnUnDemand command launched 2025/05/29 13:40:04 INF [RTSP] [conn 127.0.0.1:52874] closed: source of path 'front-porch-cam' has timed out [WyzeBridge] [API] ERROR pulling thumbnail?[HTTPError] 401 Client Error: for url: https://prod-sight-safe-auth.wyze.com/ — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB32XY4T7QMYTHJLJ3BDZ4L3A4FC7AVCNFSM6AAAAAB4SQV7P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJZGQ2DGMRWGA> . You are receiving this because you commented.Message ID: ***@***.***>

[SireSalty]

1. Yes, for testing I put them on the same subnet.
2. Unsure, its a fresh install without much changes