bobloadmire

RTSP works fine. low/high res streams. TAPO has the same behavior on low or high res streams. trying to direct view the TAPO stream from the stream links in go2rtc...

Ok so for fun I had Gemini compare the RTSP chrome media output to the TAPO media output while viewing in Frigate (Since Frigate or go2rtc aren't reporting issues): Okay,...

> This looks like the usual GPT nonsense. Do you have any better ideas than the usual gpt nonsense? I let it run all night and got some errors on...

> I haven't heard such complaints about the Tapo protocol, you are the first. I would start by checking out the standalone go2rtc. I gave you the go2rtc log in...

just got a brand new error randomly: 9:25:32.978 AM | error | undefined error=listen udp [fe80::be24:11ff:fe4b:f08c%eth0]:8555: bind: cannot assign requested address caller=github.com/AlexxIT/go2rtc/internal/webrtc/webrtc.go:48 looks like some sort of ipv6 error.

ok thanks. we'll I spun up a standalone webrtc instance outside of frigate, gave it just that single cams config, and got the same exact behavior. I'm not really sure...

> Do you using Firefox? Because webrtc error shouldn't be a problem for any other browser. > > Your issue about MSE. It's not related to microphone access. Using chrome,...

> You can set fixed listen IP for webrtc module. Or remove this line from config. Remove what line from config? For the fixed ip, that would just be the...

I tried this config with a new go2rtc instance and webrtc works, but MSE. doesn't. Passing through to Frigate still has the same old behavior. ``` streams: hot_tub: - tapo://admin:[email protected]#video=copy#audio=aac#audio=opus