Tapo 2 way audio stops working

[leaskovski]

Hi there... so I am running frigate with go2rtc 1.9.2 (the version they back into their container). The system works fine, and no real issues apart from a 2 way audio issue that I have noticed with my tapo c200 camera (v2 hardware).

Here is my config...

api:
  origin: '*'
candidates:
- 192.168.0.196:8555
- stun:8555
hass:
  config: /config
log:
  format: text
  level: debug
rtsp:
  default_query: mp4
streams:
  dog_cam: tapo://xxx:[email protected]
  dog_cam_sub: rtsp://xxx:[email protected]/stream2
  doorbell_cam:
  - ffmpeg:https://192.168.0.111/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=xxx&password=xxx#video=copy#audio=copy#audio=opus
  - rtsp://xxx:[email protected]:554/h264Preview_01_sub
  doorbell_cam_sub:
  - ffmpeg:https://192.168.0.111/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx
  drive_cam: rtsp://xxx:[email protected]/Streaming/Channels/101/
  drive_cam_sub: rtsp://xxx:[email protected]/Streaming/Channels/102/
  garden_cam: rtsp://xxx:[email protected]/Streaming/Channels/101/
  garden_cam_sub: rtsp://xxx:[email protected]/Streaming/Channels/102/
webrtc:
  candidates:
  - stun:8555

What happens is that 2 way audio will work fine after a restart of the go2rtc service, so if I open the internal webrtc.html link with vid+audio+mic for the camera, it works fine. If I then close that browser session, and reopen up the browser and go back to that page after a few minutes, the 2 way audio doesn't work.

What log levels do I need to enable to get sufficient logging for the problem? This could be a repeat of this issue (https://github.com/AlexxIT/go2rtc/issues/547), as it seems very similar.

[leaskovski]

@AlexxIT , do you need me to reproduce this with any specific logging enabled for you?

[AlexxIT]

I can check this with my camera

[leaskovski]

@AlexxIT did you manage to recreate this issue in the end?

[AlexxIT]

Haven't tested this yet.

[felipecrs]

@leaskovski, I suggest you try with a newer go2rtc:

https://docs.frigate.video/configuration/advanced/#custom-go2rtc-version

[elementc]

Hi, found my way here from https://github.com/blakeblackshear/frigate/discussions/14066

@leaskovski, I suggest you try with a newer go2rtc:

https://docs.frigate.video/configuration/advanced/#custom-go2rtc-version

I was experiencing similar issues to @leaskovski but against multiple reolink devices instead of of the Tapo device they mentioned, and updating from frigate's included go2rtc (1.9.2 at time of writing) to 1.9.9 from the releases page resolved this issue (modulo other fiddliness that these devices exhibit).

This may not reflect actual resolution for Tapo devices, of course, but confirming that the general advice is promising. Perhaps Frigate should upgrade the version they are shipping with, globally?

[leaskovski]

I didn't realise its that easy to patch frigate to a newer version of go2rtc. Kudos to the devs for that! I have just patched, and am now running 1.9.9. My initial test seems to suggest things are still the same. Will do some more testing to see if this is still an issue.

[pladombrowski]

Hello! I'm having the same issue. Here I'm using a direct webrtc connection to tapo cameras with go2rtc that works perfectly for a random time, and out of nowhere the two-way audio starts to fail and the audio from the client's microphone stops going to the camera.

Using go2rtc 1.9.9