Reolink Video Doorbell - stream won't close after 2 way audio

[cooltings]

Hi, I am using the frigate hass card with 2 way audio which works great with the doorbell. The only issue is that after finishing 2 way talk the stream doesn't seem to close and the blue status ring on the doorbell stays blue indicating it still receiving audio. Here is my config in case it has something to do with that:

api:
  ffmpeg:
    bin: /usr/local/bin/ffmpeg
  origin: '*'
ffmpeg:
  rtsp: -fflags nobuffer -flags low_delay -stimeout 5000000 -user_agent go2rtc/ffmpeg
    -rtsp_transport tcp -i {input}
hass:
  config: /config
log:
  format: text
rtsp:
  default_query: mp4
streams:
  reolink:
  - ffmpeg:http://192.168.0.33/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=smartcam#video=copy#audio=opus
  - rtsp://[email protected]:554/h264Preview_01_main
  reolink_rec:
  - rtsp://[email protected]:554/h264Preview_01_main#backchannel=0
  - ffmpeg:reolink_rec#audio=pcma
webrtc:
  candidates:
  - 192.168.0.219:8555
  - stun:8555
  listen: :8555

[danluckner]

Just to add more information, in my setup, with go2rtc version 1.7.1 it seems to be working fine, but with version 1.9 and up it does not.

[esand]

Can you confirm that after 2-way audio is closed, that client isn't still an active consumer? If you list out the stream consumers, you should be able to see if there's anything still connected to your backchannel stream. If nothing is connected but the streams remain, that would indicate an issue. I am assuming though, that something is still connected as a consumer even though you believe it's closed.

[dagleaves]

@danluckner Since you're using Reolink with an audio stream, see #1254 for the fix I used for a similar problem.