[Config Support]: How to setup Microphone in HA for Reolink

[ViezeVisNL]

Describe the problem you are having

Hi all!

I'm having Home Assistant with the Frigate Home Assistant plugin using a Reolink POE doorbell camera. How do I get the microhpone working? On the local URL the microphone button is there but pushing it does not enable the microphone (also all permissions in browser are okay) http://homeassistant.local:8123/. When I use my public URL (ha.domain.com) the microphone option is not even there.

I'm using the Advanced Camera Card.
http://homeassistant.local:8123/hacs/repository/394082552

I have never got this working properly but I have no idea why...

Version

0.16.3-9034454

Frigate config file

mqtt:
  host: 192.168.2.64
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: mqtt-user
  password: ****
  stats_interval: 60

#AI detectors
detectors:
  coral:
    type: edgetpu
    device: usb

#go2rtc
go2rtc:
  streams:
    reolink:
      - ffmpeg:http://192.168.2.65/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=*****#video=copy#audio=copy#audio=opus
      - rtsp://admin:*****@192.168.2.65:554/h264Preview_01_sub
      - ffmpeg:reolink#audio=opus
    reolink_sub:
      - ffmpeg:http://192.168.2.65/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=*****

#Cameras
cameras:
  reolink:
    snapshots:
      enabled: true
      required_zones:
        - zone_voortuin
      retain:
        default: 14
        objects:
          person: 14
          cat: 14
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/reolink
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/reolink_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-copy
    mqtt:
      enabled: true
      timestamp: false
      bounding_box: true
      crop: false
    motion:
      mask: 0,0.211,1,0.209,1,0,0,0
    zones:
      zone_voortuin:
        coordinates: 
          0.611,0.66,0.764,0.642,1,0.767,1,1,0.645,1,0.082,1,0.116,0.966,0.302,0.76,0.374,0.678,0.396,0.653,0.484,0.66
        inertia: 3
        loitering_time: 0
    objects:
      filters:
        person:
          mask:
            # - 0.2,0.757,0.234,0.753,0.224,0.685,0.19,0.692
            # - 0.282,0.698,0.314,0.689,0.305,0.643,0.275,0.646
            # - 0.33,0.67,0.355,0.658,0.347,0.616,0.325,0.615
objects:
  track:
    - person
    - cat
  filters:
    person:
      threshold: 0.70
    cat:
      threshold: 0.40

#record
record:
  enabled: true
  retain:
    days: 14
    mode: motion
  alerts:
    retain:
      days: 14
  detections:
    retain:
      days: 14
review:
  alerts:
    required_zones:
      - zone_voortuin
version: 0.16-0
detect:
  enabled: true

Relevant Frigate log output

//

Relevant go2rtc log output

//

Frigate stats

No response

Operating system

Home Assistant OS

Install method

Home Assistant Add-on

docker-compose file or Docker CLI command

//

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

To enable two-way talk with your Reolink doorbell in Home Assistant, you need to configure WebRTC properly and use the correct provider in the Advanced Camera Card(1).

Required WebRTC Configuration

First, add WebRTC candidates to your go2rtc configuration. Since you're using the Home Assistant Add-on, you may need to define candidates manually if automatic generation fails(1):

go2rtc:
  webrtc:
    candidates:
      - 192.168.2.X:8555  # Replace X with your Home Assistant IP
      - stun:8555
  streams:
    reolink:
      - ffmpeg:http://192.168.2.65/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=*****#video=copy#audio=copy#audio=opus
      - rtsp://admin:*****@192.168.2.65:554/h264Preview_01_sub
    reolink_sub:
      - ffmpeg:http://192.168.2.65/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=*****

(1)

HTTPS Requirement

You must access Frigate via HTTPS for microphone access in browsers(1). This may require opening port 8971(1). The microphone not appearing on your public URL (ha.domain.com) suggests HTTPS may not be properly configured for that access method(1).

Advanced Camera Card Configuration

For the Advanced Camera Card, use the go2rtc provider (not webrtc_card) with the correct stream name(2):

type: custom:advanced-camera-card
cameras:
  - camera_entity: camera.reolink
    go2rtc:
      modes:
        - webrtc
      stream: reolink
    live_provider: go2rtc
menu:
  buttons:
    microphone:
      enabled: true

(2)

Audio Codec Compatibility

Your configuration already includes opus audio transcoding, which is correct for WebRTC support(1). MSE requires PCMA/PCMU or AAC audio, while WebRTC requires PCMA/PCMU or opus audio(1).

Port Requirements

Ensure port 8555 (TCP and UDP) is accessible. For the Home Assistant Add-on, this should be handled automatically, but verify no firewall is blocking it(1).

Troubleshooting Steps

1. Verify HTTPS access is working for both local and public URLs(1)
2. Check that WebRTC candidates are set to your Home Assistant IP address(1)
3. Use the go2rtc provider in the Advanced Camera Card, not webrtc_card(2)
4. Ensure browser permissions allow microphone access(1)
5. Test in the Frigate Web UI first before troubleshooting the Home Assistant card(1)

📚 Sources:

1. Live View
2. [Support]: Reolink - Doorbell - 2waytalk - works in mobile but not computer

---

Have another question? Just tag @inkeep.