[Support]: Reolink - Doorbell - 2waytalk - works in mobile but not computer

[SnokplaTT]

Describe the problem you are having

Hello everyone,
I'm pulling my hair out with FRIGATE and REOLINK.

I have two cameras:

Reolink video doorbell PoE - v3.0.0.4662_25031222271
Reolink Duo 3 PoE - v3.0.0.4867_2505072124

When adding these cameras to Frigate, my logs were filled with errors and recordings were corrupted.
So I worked with ChatGPT and got some research leads, modifying the configuration to get a result without errors, although I don't master all my modifications (it was link to inputs arg and increase shm). I will document myself to better understand my modification.

However, I still have one difficulty on the doorbell is 2-way talk.
In Frigate from a computer with Chrome/Firefox/Edge, I do have the microphone icon on Frigate but when I click on it, the camera fails to load.
The browser debug mode reports (Firefox: "the media resource blob:https://frigate/..... could not be decoded. WebRTC: ICE failed" / in Google: "Websocket connection to 'wss://frigate/.... failed received a broken, close frame..."
In HA integration, i don't have any microphone in advanced camera card (in mobile or computer) with microphone option active...
Futhermore, with a mobile phone, in Frigate, it works fine with my phone though local network VPN.

I added port 1984 to my docker compose to view directly on go2rtc lié a frigate, and it's on http. Is this a lead? Knowing that I access my Frigate in https with a redirection frigate.domain.fr

To finish my test, i have tried with the go2rtc and webrtc add-on directly in HA (because the goal is to make a video intercom with advanced camera card) and I manage to activate a media stream with the microphone in webrtc so my "stream" are correct.

Do you have any idea please?

Version

version: 0.15-1

What browser(s) are you using?

No response

Frigate config file

mqtt:
  enabled: true
  host: 192.168.1.X
  user: mqtt
  password: pass
  port: 1883

birdseye:
  enabled: true
  mode: continuous
  quality: 5

detectors:
  coral:
    type: edgetpu
    device: usb

record:
  enabled: true
  retain:
    days: 2
  alerts:
    retain:
      days: 2
  detections:
    retain:
      days: 2

snapshots:
  enabled: true
  timestamp: true
  bounding_box: true
  crop: false
  quality: 70
  retain:
    default: 15

timestamp_style:
  position: bl
  effect: solid

review:
  alerts:
    labels:
      - person

semantic_search:
  enabled: true
  reindex: false
  model_size: large

go2rtc:
  ice_servers:
  - urls:
      - stun:stun.l.google.com:19302
  streams:
    rtsp_couloir:
      - rtsp://admin:password@192.168.1.27/streaming/channels/101
      - rtsp_couloir#audio=opus
    rtsp_couloir_sub:
      - rtsp://admin:password@192.168.1.27/streaming/channels/102
      - rtsp_couloir_sub#audio=opus
    rtsp_ext1:
      - rtsp://admin:password@192.168.1.28/h264Preview_01_main
    rtsp_doorbell:
      - rtsp://admin:password@192.168.1.29/h265Preview_01_main
      - ffmpeg:rtsp_doorbell#audio=opus#audio=copy
      - onvif://192.168.1.29
    rtsp_doorbell_sub:
      - rtsp://admin:password@192.168.1.29:554/h264Preview_01_sub

cameras:
  Couloir:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/rtsp_couloir
          input_args:
            - -rtsp_transport
            - tcp
            - -timeout
            - '5000000'
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/rtsp_couloir_sub
          input_args:
            - -rtsp_transport
            - tcp
            - -timeout
            - '5000000'
          roles:
            - detect
            - audio
    detect:
      enabled: true
    live:
      stream_name: rtsp_couloir
    birdseye:
      enabled: true
    objects:
      track:
        - person
        - vehicle
        - animal

  Exterieur:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/rtsp_ext1
          input_args:
            - -rtsp_transport
            - tcp
            - -rtsp_flags
            - +prefer_tcp
            - -timeout
            - '5000000'
          roles:
            - record
            - detect
    detect:
      enabled: true
    live:
      stream_name: rtsp_ext1
    birdseye:
      enabled: true
    objects:
      track:
        - person
        - dog

  Doorbell:
    enabled: true
    ffmpeg:
      hwaccel_args: []
      inputs:
        - path: rtsp://127.0.0.1:8554/rtsp_doorbell
          input_args:
            - -rtsp_transport
            - tcp
            - -timeout
            - '5000000'
          roles:
            - record
            - audio
            - detect
        - path: rtsp://127.0.0.1:8554/rtsp_doorbell_sub
          input_args:
            - -rtsp_transport
            - tcp
            - -timeout
            - '5000000'
          roles:
            - detect
    detect:
      enabled: true
    live:
      stream_name: rtsp_doorbell
    birdseye:
      enabled: true
    objects:
      track:
        - person
        - dog
      
camera_groups:
  Safety:
    order: 1
    icon: LuBanana
    cameras:
      - Couloir
      - Exterieur
      - Doorbell
  Birdseye:
    order: 3
    icon: LuBird
    cameras: birdseye

version: 0.15-1

Relevant Frigate log output

N/A clear

Relevant go2rtc log output

N/A clear

FFprobe output from your camera

N/A

Frigate stats

No response

Install method

Docker Compose

docker-compose file or Docker CLI command

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "1024mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions

      - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /path/to/your/config.yml:/config/config.yml
      - /path/to/your/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "1994:1994"  # Frigate API/debug
      - "1984:1984"  # Interface go2rtc (Talk/Config)
      
    environment:
      FRIGATE_RTSP_PASSWORD: "Passwordmodified!"

Object Detector

Coral

Network connection

Wired

Camera make and model

REOLINK

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Your configuration for 2-way talk with the Reolink Doorbell in Frigate is close, but there are a few areas to check based on the documentation:

1. WebRTC and go2rtc Configuration:
   For 2-way talk to work reliably (especially from computers), you must ensure that go2rtc is set up for WebRTC, and that Frigate is accessible via HTTPS. WebRTC requires port 8555 (TCP and UDP) to be open and forwarded to your Frigate host if you access it externally. For internal access, you may need to set WebRTC candidates in your go2rtc config:

   go2rtc:
     streams:
       ...
     webrtc:
       candidates:
         - 192.168.1.x:8555
         - stun:8555

   If using a VPN or a reverse proxy for HTTPS, make sure the candidate IP matches the actual interface/IP clients use to reach Frigate(1).

2. Codec Compatibility:
   The browser must be able to decode the camera stream. Use H.264 video and AAC (or PCMA/PCMU/Opus) audio for maximum compatibility. Avoid H.265 for WebRTC/MSE in browsers. If your Reolink is sending H.265, transcode it to H.264:

   go2rtc:
     streams:
       rtsp_doorbell:
         - "ffmpeg:rtsp://admin:password@192.168.1.29/h265Preview_01_main#video=h264#audio=opus"

   Adjust your Frigate camera input to use this stream(1)(2).

3. HTTPS Requirement:
   Accessing Frigate over HTTPS is required for microphone access in browsers. If you use a reverse proxy, ensure websockets and all required ports are forwarded and not blocked(1).

4. Substream for Live View:
   If you want to use a substream for live view (to reduce bandwidth), configure the live.stream_name for your doorbell camera:

   cameras:
     Doorbell:
       ...
       live:
         stream_name: rtsp_doorbell_sub

   Ensure the stream referenced is configured in your go2rtc section(1).

5. Firewall/NAT/Network Issues:
   WebRTC ICE errors often indicate a networking problem. Double-check that port 8555 is open, forwarded, and not blocked by a firewall. If you're using Docker in bridge mode, ensure the ports are mapped:

   ports:
     - "8555:8555/tcp"
     - "8555:8555/udp"

   If you use network: host, port forwarding is not necessary, but avoid port conflicts(1).

6. Audio Streams:
   For two-way talk, ensure your stream's audio is in a compatible format (AAC/Opus). If not, transcode as shown above. Reolink doorbells are recommended to use the HTTP-FLV stream for stability, but for 2-way audio, a secondary RTSP stream may be required(3).

7. Browser Permissions:
   Make sure your browser is allowed to use the microphone and that no browser extensions are interfering.

8. Frigate UI vs. Home Assistant Card:
   Two-way talk is only supported in the Frigate Web UI when go2rtc and WebRTC are set up as described(1). If using the Home Assistant Frigate card, follow its specific documentation for 2-way audio.

Summary of steps to try:

• Ensure go2rtc streams use H.264 video and Opus/AAC audio.
• Set WebRTC candidates to the LAN IP of your server.
• Confirm HTTPS is working and all required ports are open.
• Use the HTTP-FLV or RTSP stream as recommended for your device.
• Use the Frigate Web UI for 2-way talk testing, not just the Home Assistant card.

References and further reading:

• Live View
• Configuring go2rtc
• Camera Specific Configurations

📚 Sources:

1. Live View
2. Configuring go2rtc
3. Camera Specific Configurations

[SnokplaTT]

Hello, to answer IA :

1° When i have tried to look to add webrtc to my config i have read that it wasn't maintain.
2° Copy past error, the camear is h264
3° Yes, thought NPM & certificat & frigate.domaine.fr
4° Copy past error, in my original the sub is in comment.
5° Yes as visible in my docker compose
6° Check with VLC the audio is in AAC, but maybe i haven't understand this.

[SnokplaTT]

Thank you NickM

I just made the change, and I see little to no difference. Unfortunately, I can't check on the PC (it's not available until tomorrow), but on HA, the microphone button hasn't appeared. Also, and I apologize for only noticing this now, on HA with the advanced camera card, I don't have any sound either.

Just to be sure, it is frigate ip adress?
webrtc:
candidates:
- 192.168.1.x:8555
- stun:8555

[NickM-27]

For home assistant you have to configure the microphone to appear, there is no automatic behavior like there is in frigate

[hawkeye217]

Make sure you're using the go2rtc source with the correct stream name for the Advanced Camera Card, for example:

cameras:
  - camera_entity: camera.rtsp_doorbell
    go2rtc:
      modes:
        - webrtc
      stream: rtsp_doorbell
    live_provider: go2rtc

[SnokplaTT]

@NickM-27 :
Yes for sure, i know and it is done but it doesn't works...

@hawkeye217 : Yes agree.

My card configuration :
type: custom:advanced-camera-card
cameras:

• frigate:
  url: http://192.168.1.4:5000/#Doorbell
  webrtc_card:
  entity: camera.doorbell
  menu:
  buttons:
  microphone:
  enabled: true
  permanent: true
  alignment: matching
  icon: mdi:account
  type: momentary
  mute:
  permanent: true
  enabled: true
  alignment: opposing
  icon: mdi:air-conditioner

• I have so much trouble with LXC and i think that i have tested everything ...... So i am thinking more and more to create a new frigate out of LXC but with VM / docker / container as recommended..

[hawkeye217]

So to be clear, I suggested using the go2rtc provider, not webrtc_card. I'm not totally familiar with all of the inner workings of the Advanced Camera Card, but I know users have had success using the go2rtc provider.