Frigate WebRTC Cameras Google Home

[fallow swan]

Hi All. I have 2 Reolink Cameras in Frigate that I want to be able to expose to the Google Assistant SDK and display the video feeds on the Google Home App and Google Nest Hubs default interface. I have Nabu Casa remote paid for and configured, all other devices work fine when exposing to Google Assistant and managing from Google Home/Google Assistant. Video feeds I'm able to expose and see in Google Home however when I try and load the stream in the app it just loads forever.

• I have go2RTC configured in Frigate

 streams:
   doorbell:
     - rtsp://user:pass@<localip>:554/h264Preview_01_sub
   playroom:
     - rtsp://user:pass@<localip>:554/h264Preview_01_main
 webrtc:
   candidates:
     - <localip>:8555
     - stun:8555```
      *I attempted the stun configuration with a forwarded port just as a test but I don't think it should be needed and I've removed the port forward for now. *
- I have Web2RTC enabled in Home Assistant Cloud settings

I've also attempted this without frigate and using the direct streams with go2rtc configured in HomeAssistant with the same results. 

Has anyone managed to get this to work at all?

I also should note that it seems like any text to speech casts to my devices also fail. Whether that's entirely relevant to this I'm unsure

[versed osprey]

I would stick with the WebRTC from HA and do not configure go2rtc in frigate

[fallow swan]

Yeah I had a feeling I was doubling up there. That being said, in previous tests that also has had the same result.

[fallow swan]

Should also be noted that when I remove go2rtc configurations from frigate, they show as unsupported when exposing them to Google Assistant. That said. My nas is pretty resource poor so I'm going to leave frigate alone to record only, any streaming I'll do using the direct reolink rtsp streams and configure any specifics with go2rtc.yaml in home assistant or configure ffmpeg. I'm yet to actually determine if this is a connection issue, or a codec issue.