BUG: RTSP stream not working

[jreagor]

Describe the bug

First, Thank you very much for this add-on!

HA Version 14.2 Supervised on HA Green.
WB Version 2.10.3
WebAUTH False
Using local URL
3 WCv3 with RSTP firmware (4.28.4.41)
1 PanCam with RSTP firmware (4.29.4.41)
3 WC Floodlights with v3 cams (two cams each, one built in one add on v3) firmware (4.36.13.0416)
1 WCv3 without RSTP firmware (4.36.10.4054)

The four cams with RSTP firmware, I can see and stream in the WB webUI and add as generic cams with RTSP url or entity from WB.

The WCv3 without RSTP firmware stream in the WB webUI but don't see it as an entity when trying to add to generic cam.

The three floodlights with v3 cams only show snapshots in the WB webUI, cant stream in the webUI, show up as entities for streaming in generic cam and the RTSP url times out when adding to generic cam.

Any thoughts?

Thank you!

Affected Bridge Version

2.10.3

Bridge type

Home Assistant

Affected Camera(s)

See above

Affected Camera Firmware

See above

docker-compose or config (if applicable)

[Jeppedy]

I had it working, but when I saw odd behaviors, I uninstalled and reinstalled. I'm not sure if it's an odd defect or something I changes when I reinstalled, but only v2 cams are working properly. I have none where I flashed RTSP firmware on the cams, so these are all "stock" cams.

[bpapa9013]

Most likely related to known recent issue that's been traced back to the changes in the P2P lib that Wyze uses which has apparently been changed to require that the wyze-bridge container/HAOS add-on is on the same subnet as the cams and must have host netwoking (not a viable permanent "fix" but the best temporary work-around).

For HAOS/wize-bridge add-on users check the temp solution here:
#1432 (comment)

You will need to install a forked non-official version of wyze-bridge that I think gives the add-on host networking on the HAOS host. I am not an expert on this solution as I use HA/wyze-bridge/frigate all in standard containers. If you also use Unifi networking hardware please also check the recent posts on the Unifi Wifi/network settings thread here:
#891
Where it was determined that some Unifi Wifi/network settings can fix the multicast filtering that is also affecting the bridge's ability to connect to cameras (even on the same subnet).

[jreagor]

Thank you for the replies. I originally considered the subnet issue, however while some cams are on an AP they are all on the same subnet. I did try the forked versions with same results. As of now, all standalone cams (FW 4.36.13.0416, 4.29.4.41, 4.61.0.3 and 4.28.4.41) regardless of firmware or AP connection are streaming via WB entities as they should. One v3 (FW 4.36.13.0416) which is connected to a garage controller is not streaming. I have one v3 standalone cam (FW 4.61.0.3) on the same AP as other v3 cams connected via floodlights (FW 4.36.13.0416) and that one standalone cam streams via WB entity. Not sure why I couldn't see it before, probably user error. The ones that now seem to be the issue are the floodlight connected cams and the v3 cam with the garage door controller. Only seeing snapshots and snapshot entities for those no streams or stream entities. Oddly enough, the only common physical connection is the non-streaming seem to not be stand alone cams.