go2rtc icon indicating copy to clipboard operation
go2rtc copied to clipboard

Unable to connect output stream to Nest.Google doorbell (two way audio)

Open NikoMiko68 opened this issue 1 month ago • 2 comments

I use go2rtc 1.9.12 with Frigate 0.16.2 inside a docker I have 6 cameras from Google/Nest, Aqara or Reolink Google/Nest cam are not the best to use outside Google's ecosystem but I have them since a while and I would try to give it a go. I have no issues with Aqara or Reolink, I can even connect the radio stream to my Reolink camera. But concerning the Google/Nest doorbell wired 1st Gen, I am not able to connect the output stream to the doorbell to talk with the person ringing at the door, I get always the same error: [streams] can't add track error=webrtc: can't get track. the net diagram confirm the missing connection (it shows the additional branch when I activate the output stream (from PC to camera):

Image

My go2rtc config:

go2rtc:
  webrtc:
    candidates:
      - 192.168.1.0/24:8555
      - 127.0.0.0/24:8555
      - 172.30.33.0/24:8555
      - 172.16.3.0/24:8555
      - 172.16.4.0/24:8555
      - XXX.XXX.XXX.XXX:8555
      - stun:8555
  api.origin: '*'
  streams:
    terrasse:
      - rtsp://XXX:[email protected]:8554/ch1
      - ffmpeg:terrasse#video=h264#width=2688#height=1520#audio=aac#hardware=cuda
    terrasse_sub_raw:
      - rtsp://XXX:[email protected]:8554/ch3
      - ffmpeg:terrasse_sub_raw#video=h264#width=1280#height=720#audio=aac#hardware=cuda   
    sonnette:
      - nest:?client_id=XXX&client_secret=XXX&device_id=XXX&project_id=XXX&protocols=WEB_RTC&refresh_token=XXX
    salleManger:
      - nest:?client_id=XXX&client_secret=XXX&device_id=XXX&project_id=XXX&protocols=WEB_RTC&refresh_token=XXX
    garage:
      - nest:?client_id=XXX&client_secret=XXX&device_id=XXX&project_id=XXX&protocols=WEB_RTC&refresh_token=XXX
    jardin:
      - nest:?client_id=XXX&client_secret=XXX&device_id=XXX&project_id=XXX&protocols=WEB_RTC&refresh_token=XXX
    oiseaux:
      - rtsp://XXX:[email protected]:8554/Preview_01_main
      - ffmpeg:oiseaux#video=h264#width=2560#height=1920#audio=aac#hardware=cuda
    oiseaux_sub_raw:
      - rtsp://XXX:[email protected]:8554/Preview_01_sub
      - ffmpeg:oiseaux_sub_raw#video=h264#width=640#height=480#audio=aac#hardware=cuda

I have spent days and nights on that topic w/o finding a way to solve that issue, I wonder if the design of the go2rtc Nest plugin allows this feature.

NikoMiko68 avatar Dec 02 '25 13:12 NikoMiko68

I did more test and build a new machine running exclusively on HA OS, I used the integrated Frigate addon and all runs under https to get the two way audio

The result is exactly the same, the output audio stream didn't connect to the NEST stream, I think something is missing here.

Image Image

@AlexxIT Could you confirm if the NEST stream can work in a two way audio mode?

NikoMiko68 avatar Dec 04 '25 17:12 NikoMiko68

As far as I know, source nest does not support two-way audio. This was not stated anywhere in the documentation. And I don't have such cameras for testing.

AlexxIT avatar Dec 18 '25 12:12 AlexxIT