Streams never start with 2.9.8

[vipergts450]

Hello @mrlt8 ,

Just pulled the latest 2.9.8 an hour ago. The container comes up and seems to be operating fine, but the streams to each camera never start. I did not change my configuration at all since 2.9.7 or prior.

Log:

2024-06-20T19:52:44.986400388Z 🚀 DOCKER-WYZE-BRIDGE v2.9.8 X86_64
2024-06-20T19:52:44.986517501Z 
2024-06-20T19:52:45.011528899Z [WyzeBridge] 📚 Using 'auth' from local cache...
2024-06-20T19:52:45.016523780Z  * Serving Flask app 'frontend'
2024-06-20T19:52:45.016685676Z  * Debug mode: off
2024-06-20T19:52:45.017168690Z [WyzeBridge] 📚 Using 'user' from local cache...
2024-06-20T19:52:45.019034176Z [WyzeBridge] 📚 Using 'cameras' from local cache...
2024-06-20T19:52:45.019246796Z [WyzeBridge] 🪄 FILTER ALLOWING: 2 of 3 cams
2024-06-20T19:52:45.019329117Z [WyzeBridge] [+] Adding cam1 [WYZE_CAKP2JFUS]
2024-06-20T19:52:45.022431884Z [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
2024-06-20T19:52:45.023128059Z  * Running on all addresses (0.0.0.0)
2024-06-20T19:52:45.023191207Z  * Running on http://127.0.0.1:5000
2024-06-20T19:52:45.023237519Z  * Running on http://172.30.0.2:5000
2024-06-20T19:52:45.023285008Z [WyzeBridge] Press CTRL+C to quit
2024-06-20T19:52:45.031918991Z [WyzeBridge] [+] Adding cam2 [WYZECP1_JEF]
2024-06-20T19:52:45.032577576Z [WyzeBridge] starting MediaMTX 1.1.1
2024-06-20T19:52:45.033373199Z [WyzeBridge] 🎬 2 streams enabled

The process stops at this point and never starts the streams.

[vipergts450]

Weird, I wonder if Wyze itself is down right now, because I'm having trouble on the official Wyze app also

[vipergts450]

Restarting the container a few times still stalls at the same point as above.

[brokendash]

I'm also having issues, was running 2.9.7 no changes in cfg. after update to 2.9.8 no connections to cams would initiate automaticly like before. sometimes they can be started by hand via the web interface but they flake out.....

[vipergts450]

It feels like the new resuming code might have forgotten to start the stream when the container starts up automatically and is waiting for the WebUI to send a "play" command to get everything going. Maybe worth adding a - AUTOSTART=True flag into the configuration options if the default is expected to be "False" now?

[mrlt8]

My bad, this should be fixed in v2.9.9.

[vipergts450]

We appreciate all your work on this!

[hitnrun30]

Yeah and now especially since I added gpt4vision it makes all much easier

[nomi25home]

I had the same issue. I use Dockge to host WB container. I had to add the latest tag to the image and recreate the container for it to work

image: mrlt8/wyze-bridge:latest

This is what my docker-compose looks like now

`version: "3.3" services: wyze-bridge: environment:

• WB_IP=192.168.
• WYZE_EMAIL=
• WYZE_PASSWORD=
• API_ID=
• API_KEY= ports:
• 8554:8554
• 8888:8888
• 5000:5000 image: mrlt8/wyze-bridge:latest volumes: [] networks: [] depends_on: [] restart: always logging: driver: gelf options: gelf-address: udp://192.168. networks: {} `

[hitnrun30]

2.99 Fixed my problems.

[vipergts450]

2.9.9 attempts to connect but cannot, only getting [-13] IOTC_ER_TIMEOUT on both cameras now

[vipergts450]

cam1 stream started on its own after 3 hours. cam2 is actually in need of a hard reboot in person, so no data on that one.

[vipergts450]

cam1 and cam2 have been very stable once the stream went up! Almost 24 hours so far and no issues. I will let you know if they run into any timeouts. Once again, thanks for helping our community @mrlt8

[vipergts450]

No drops since my last comment above on either cam. 🤞🏻