search

felipecrs / hass-expose-camera-stream-source

Allows to import Home Assistant cameras into go2rtc and Frigate
MIT License
100 stars 4 forks source link

Nest doorbell stream has no audio #33

Closed backslashV closed 9 months ago

backslashV commented 9 months ago

Hi, How can I add audio to the stream? I have the following config in Frigate still with no audio.

go2rtc:
  streams:
    doorbell:
      - echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.doorbell
      - "ffmpeg:back#audio=aac"
felipecrs commented 9 months ago

Shouldn't it be "ffmpeg:doorbell#audio=aac"?

backslashV commented 9 months ago

Oh right. Didn't realize that's the camera name, but still I don't have audio after changing it to the correct name. I see this in the Frigate logs:

2024-02-11 04:10:29.601473759 20:10:29.601 WRN [rtsp] error="streams: codecs not matched: AAC => ANY" stream=doorbell

Please let me know if I should post this question in the go2rtc repo.

felipecrs commented 9 months ago

Right. Yeah, you should place the question there. This integration only forwards the RTSP link from Home Assistant to go2rtc/outside. There's nothing that can be done at this integration to fix your issue.

felipecrs commented 9 months ago

Oh. What you can do by the way is to run this script in some terminal add-on and try to reproduce the RTSP it outputs in VLC. If there is no audio in VLC, there is little go2rtc could do as well.

felipecrs commented 9 months ago

Also, does audio work within Home Assistant?

backslashV commented 9 months ago

Thanks. Running the script in the terminal addon outputs an RTSPS link which VLC can't play. The original camera from the Nest integration does have audio.

felipecrs commented 9 months ago

If you have audio when browsing the camera entity within Home Assistant, then there is a chance go2rtc can pick up the audio as well. Make sure to open an issue there. Try checking the stream directly by the go2rtc port btw, removing Frigate from the loop.