Reolink Video Doorbell discussion

[luisiam]

The latest FW 1859 enables 2-way audio via ONVIF profile T. I checked with Happytimesoft ONVIF client and 2-way audio works. Is there any chance to get it working in go2rtc?

Output from info page

{
  "producers": [
    {
      "type": "RTSP active producer",
      "url": "rtsp://192.168.10.21//",
      "remote_addr": "192.168.10.21:554",
      "user_agent": "go2rtc/1.3.1",
      "medias": [
        "video, recvonly, H.264 High 5.1",
        "audio, recvonly, MPEG4-GENERIC/16000"
      ],
      "receivers": [
        "96 H264, bytes=129455539, senders=1",
        "97 MPEG4-GENERIC/16000, bytes=1984536, senders=1"
      ],
      "recv": 132603331
    },
    {
      "type": "RTSP passive producer",
      "url": "rtsp://localhost:8554/fb75e35d718d1e0379580b00d5fcc0e7",
      "remote_addr": "127.0.0.1:43364",
      "user_agent": "ffmpeg/go2rtc",
      "medias": [
        "audio, recvonly, OPUS/48000/2"
      ],
      "receivers": [
        "96 OPUS/48000/2, bytes=2800207, senders=1"
      ],
      "recv": 2949215
    }
  ],
  "consumers": [
    {
      "type": "RTSP passive consumer",
      "url": "rtsp://localhost:8554/doorbell_test?audio",
      "remote_addr": "127.0.0.1:43354",
      "user_agent": "go2rtc/ffmpeg",
      "medias": [
        "audio, sendonly, ANY"
      ],
      "senders": [
        "96 MPEG4-GENERIC/16000, bytes=1984536, receivers=1"
      ],
      "send": 2046072
    },
    {
      "type": "WebRTC/WebSocket async passive consumer",
      "remote_addr": "tcp4 prflx 192.168.10.183:65337 related :0",
      "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36 Edg/111.0.1661.62",
      "medias": [
        "video, sendonly, VP8, RTX, VP9, H264, AV1, RED, ULPFEC, FLEXFEC-03",
        "audio, recvonly, OPUS/48000/2, RED/48000/2, G722/8000, PCMU/8000, PCMA/8000, CN/8000, TELEPHONE-EVENT/48000, TELEPHONE-EVENT/8000",
        "audio, sendonly, OPUS/48000/2, RED/48000/2, G722/8000, PCMU/8000, PCMA/8000, CN/8000, TELEPHONE-EVENT/48000, TELEPHONE-EVENT/8000"
      ],
      "receivers": [
        "111 OPUS/48000/2, bytes=812126, senders=0"
      ],
      "senders": [
        "96 H264, bytes=124447151, receivers=1",
        "96 OPUS/48000/2, bytes=2679873, receivers=1"
      ],
      "recv": 1054116,
      "send": 128596160
    }
  ]
}

[luisiam]

Yes I did. When I run the script directly from CLI it seems working without throwing any error.

If you do the following inside the frigate docker container to play a test MP3, does it work?

cd /config/neolink

./neolink talk Doorbell --config config.toml -m -i "souphttpsrc location=https://rhasspy.github.io/piper-samples/samples/en/en_US/lessac/high/speaker_0.mp3"

Yup that works

[bezmi]

How about changing neolink_talk.sh to:

#!/usr/bin/env bash
ffmpeg -i https://rhasspy.github.io/piper-samples/samples/en/en_US/lessac/high/speaker_0.mp3 -f  alaw -ar 8000 -f wav - | neolink ./neolink talk Doorbell -c config.toml --volume=1.0 -m -i "fdsrc fd=0"

and then calling it from the docker container shell, /config/neolink/neolink_talk.sh. It should play the test mp3 similar to before, but now we're just making sure the script works.

Only other thing I can think of is to try go2rtc v1.9.2 instead of v1.9.3 as that's what I was using originally. I haven't tested too much with the latest version. Frigate version 0.13.2. Sometimes if things crash in a weird way, I need to issue a ./neolink reboot Doorbell --config config.toml and then restart frigate, but when that happens, issuing a test command like above doesn't work either, it is a rare occurrence.

[luisiam]

How about changing neolink_talk.sh to:

#!/usr/bin/env bash
ffmpeg -i https://rhasspy.github.io/piper-samples/samples/en/en_US/lessac/high/speaker_0.mp3 -f  alaw -ar 8000 -f wav - | neolink ./neolink talk Doorbell -c config.toml --volume=1.0 -m -i "fdsrc fd=0"

and then calling it from the docker container shell, /config/neolink/neolink_talk.sh. It should play the test mp3 similar to before, but now we're just making sure the script works.

Only other thing I can think of is to try go2rtc v1.9.2 instead of v1.9.3 as that's what I was using originally. I haven't tested too much with the latest version. Frigate version 0.13.2. Sometimes if things crash in a weird way, I need to issue a ./neolink reboot Doorbell --config config.toml and then restart frigate, but when that happens, issuing a test command like above doesn't work either, it is a rare occurrence.

I am using the exact same go2rtc as well as frigate as you. Not sure why it's not working on my end. May be I will just wait for it to be integrated into go2rtc itself lol

[ReX1983]

Does anybody know if the latest firmware (v3.0.0.3215_2401262240) also breaks 2-way audio?

I have confirmed that the 2-way audio broke between version v3.0.0.2033_23041302 and v3.0.0.3215_2401262240. When I reverted to v3.0.0.2033_23041302 using this firmware archive repository, I managed to get it working.

[Iceman248]

Does anybody know if the latest firmware (v3.0.0.3215_2401262240) also breaks 2-way audio?

I have confirmed that the 2-way audio broke between version v3.0.0.2033_23041302 and v3.0.0.3215_2401262240. When I reverted to v3.0.0.2033_23041302 using this firmware archive repository, I managed to get it working.

That's what is being said in the post you quoted. Yes, my findings were the same.

[n3xus1]

I found a newer firmware version online for the Wifi reolink doorbell v3.0.0.3308_2405271823 that has support for the 2 way audio and works with the V2 chime at 900Mhz. I do notice the chime on mine is a little buggy, sometimes it needs a long press for it to work. Not sure if it's a issue with the firmware or frigate

here is a link to the file https://drive.google.com/file/d/19LxC2tIbTUEBUNiwoFtAMPsC5MbF9YF5/view?usp=drive_link

[Cytomax55]

@n3xus1 Do you know if the new updated firmware helps with anything or fixes any problems??

[n3xus1]

@n3xus1 Do you know if the new updated firmware helps with anything or fixes any problems??

All I know is that it allows 2 way audio and the V2 chime to work. I did experiment a bit with neolink, and it seemed to work but was buggy. The RC version was very delayed and I couldn't use 2 way audio when not on local network with neolink. I may need to install libssl in my docker container. I have not had a chance to go back and test more with neolink

[Za-Sing]

I bricked and returned TWO doorbells. I tried downgrading to 2676 and 2033, both times the doorbell would no longer connect and got itself stuck constantly rebooting every 20 seconds or so. I can't think of anything I could have possibly done wrong (unless updating firmware over WiFi instead of Ethernet is what killed them?). Is it worth it to try a third time with this other firmware? Anyone have similar experiences?

[bedrockuser]

I bricked and returned TWO doorbells. I tried downgrading to 2676 and 2033, both times the doorbell would no longer connect and got itself stuck constantly rebooting every 20 seconds or so. I can't think of anything I could have possibly done wrong (unless updating firmware over WiFi instead of Ethernet is what killed them?). Is it worth it to try a third time with this other firmware? Anyone have similar experiences?

Yes, it happened to me 1 week ago. I sent it back too. I don't touch the firmware anymore for fear of doing the same thing again, so I'm going to try the neolink technique.

[Za-Sing]

@bedrockuser Please let me know how neolink works on a new doorbell! I'd greatly appreciate that, since I'm having trouble finding a good alternative to Reolink. If it works well I may get another doorbell and give it a shot.

[qonfusion90]

I bricked and returned TWO doorbells. I tried downgrading to 2676 and 2033, both times the doorbell would no longer connect and got itself stuck constantly rebooting every 20 seconds or so. I can't think of anything I could have possibly done wrong (unless updating firmware over WiFi instead of Ethernet is what killed them?). Is it worth it to try a third time with this other firmware? Anyone have similar experiences?

I received two new PoE Reolink doorbells (Black and White) yesterday with latest firmware. At first they where not working. After upgrading to a newer version provided by Reolink support it started working again. Please review my HA Community post

Hope this helps.

[bagobones]

I received two new PoE Reolink doorbells (Black and White) yesterday with latest firmware. At first they where not working. After upgrading to a newer version provided by Reolink support it started working again. Please review my HA Community post

If you get special firmware from reolink support please try and submit them to the https://github.com/gtalusan/reolink-fw-archive project so others can benefit from them.

[Za-Sing]

I found a newer firmware version online for the Wifi reolink doorbell v3.0.0.3308_2405271823 that has support for the 2 way audio and works with the V2 chime at 900Mhz. I do notice the chime on mine is a little buggy, sometimes it needs a long press for it to work. Not sure if it's a issue with the firmware or frigate

here is a link to the file https://drive.google.com/file/d/19LxC2tIbTUEBUNiwoFtAMPsC5MbF9YF5/view?usp=drive_link

Has anyone else gotten a WiFi version of this v3.0.0.3308 firmware from Reolink support? I know I am being a stickler but I would prefer an official download link before I take my chances on buying a 3rd doorbell...

[n3xus1]

I found a newer firmware version online for the Wifi reolink doorbell v3.0.0.3308_2405271823 that has support for the 2 way audio and works with the V2 chime at 900Mhz. I do notice the chime on mine is a little buggy, sometimes it needs a long press for it to work. Not sure if it's a issue with the firmware or frigate

here is a link to the file https://drive.google.com/file/d/19LxC2tIbTUEBUNiwoFtAMPsC5MbF9YF5/view?usp=drive_link

Has anyone else gotten a WiFi version of this v3.0.0.3308 firmware from Reolink support? I know I am being a stickler but I would prefer an official download link before I take my chances on buying a 3rd doorbell...

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

[Za-Sing]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

[Cytomax55]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

What version are you running?

[n3xus1]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

What version are you running?

v3.0.0.3308_2405271823

[mx-vatte]

Nice to read that 2-way audio is working again. Do you know if this firmware works for the POE version of Reolink doorbell as well?

[luisiam]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

Are you using pure go2rtc or go2rtc with neolink?

[DMedina559]

I got support to send me v3.0.0.3308_2405271823 also and it's working with go2rtc without neolink

[n3xus1]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

Are you using pure go2rtc or go2rtc with neolink?

I'm just using go2rtc in home assistant. I tried neolink but it was a bit buggie for me.

[Za-Sing]

I downloaded it from this link and it worked for me. I'm on vacation so I'm not able to send you the exact copy I used. You could try support yourself and see if you can get it or maybe there is a newer version out you could share with all of us.

For some reason the support person I emailed seemed unaware of the new version (or unwilling to share it) however I can confirm the firmware on the Drive link worked for me as well, I got a brand-new doorbell today and updated it. 2-way audio is working fine through go2rtc + Frigate lovelace card

Are you using pure go2rtc or go2rtc with neolink?

I am also using go2rtc with the Frigate lovelace card in home assistant. I have not tried neolink

[keithnet]

POE version of 3308 is here: https://community.home-assistant.io/t/2-way-audio-w-reolink-poe-doorbell/649469/64

2 way audio works for me now again in Home Assistant.

I does have bug tho: "Unfortunately it breaks the ability to send pre configured auto reply messages over REST commands. :("

[DMedina559]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model

https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

[bagobones]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model

https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install..

Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

[Blueion76]

Anyone have the firmware for the White WiFi doorbell?

[Blueion76]

Anyone have the firmware for the White WiFi doorbell?

Got an update for anyone with the white WiFi doorbell like me.

[vexersa]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install..

Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works.

Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

[bagobones]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install.. Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works.

Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

I also have a long delay

go2rtc in frigate

go2rtc:
  streams:
    doorbell: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus   # transcodes audio to opus for webrtc compatibility
    doorbell_sub: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus   # transcodes audio to opus for webrtc compatibility

Frigate card in HA

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: doorbell_sub
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

[DMedina559]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install.. Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works. Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

I also have a long delay

go2rtc in frigate

go2rtc:
  streams:
    doorbell: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus   # transcodes audio to opus for webrtc compatibility
    doorbell_sub: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus   # transcodes audio to opus for webrtc compatibility

Frigate card in HA

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: doorbell_sub
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

I read somewhere that if you're using the rtsp stream for both you should disable the back channel on the mainstream so the mic connects to the substram.

This is my go2rtc yaml that works for me

go2rtc: 
  streams:
    front_door_camera:
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_main#backchannel=0
      - ffmpeg:front_door_camera#audio=opus#hardware
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_sub
    front_door_camera_sub:
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_sub
      - ffmpeg:front_door_camera_sub#audio=opus#hardware

[bagobones]

I read somewhere that if you're using the rtsp stream for both you should disable the back channel on the mainstream so the mic connects to the substram.

Maybe, I thought that was only to fix a bug with Amcrest doorbells that would not ring if their where streaming.

I very rarely attempt to use the talk feature other than some testing. Very few people come and stay at the door when I am not home.

[luisiam]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install.. Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works. Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

I also have a long delay

go2rtc in frigate

go2rtc:
  streams:
    doorbell: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus   # transcodes audio to opus for webrtc compatibility
    doorbell_sub: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus   # transcodes audio to opus for webrtc compatibility

Frigate card in HA

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: doorbell_sub
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

You can reference Frigate documentation on Reolink doorbell setup recommendation. https://docs.frigate.video/configuration/camera_specific#reolink-cameras

Rule of thumb for reolink camera is to use HTTP-FLV stream as much as you can.

[DMedina559]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install.. Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works. Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

I also have a long delay go2rtc in frigate

go2rtc:
  streams:
    doorbell: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus   # transcodes audio to opus for webrtc compatibility
    doorbell_sub: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus   # transcodes audio to opus for webrtc compatibility

Frigate card in HA

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: doorbell_sub
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

You can reference Frigate documentation on Reolink doorbell setup recommendation. https://docs.frigate.video/configuration/camera_specific#reolink-cameras

Rule of thumb for reolink camera is to use HTTP-FLV stream as much as you can.

I haven't had any issue with the rtsp streams on either of my Reolink cameras (Wifi Doorbell, RLC-540A)

[luisiam]

If anyone wants the new firmware for the black wifi doorbell that worked on my v2 model https://support-d.reolink.com/attachments/token/BWuMT3WnhbCUWlwmbGyBLC7cw/?name=Reolink-Video-Doorbell-WiFi.3308_2405271823.DB_566128M5MP_W.paks

I can confirm RTSP and two way audio works via the frigate card / frigate 0.14 / go2rtc 1.9.2 at least testing right after install.. Will have to wait and see if it is stable or has leaks / fails after a few days like some earlier firmware.

I've attempted to configure the Frigate card with go2rtc. When pushing the button on the doorbell unit, the microphone icon pops up on the frigate card, but I don't hear any audio making it back through to the doorbell unit from my phone (which is what i was using to test whilst standing at the doorbell). Audio from the doorbell to HA works, but has an epic delay. I guess I can live with a delay, so long as 2 way audio works. Would you be prepared to put together a short guide on how you've set yours up? 🙏x ♾️

I also have a long delay go2rtc in frigate

go2rtc:
  streams:
    doorbell: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus   # transcodes audio to opus for webrtc compatibility
    doorbell_sub: #Reolink Doorbell
      - rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.6:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus   # transcodes audio to opus for webrtc compatibility

Frigate card in HA

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: doorbell_sub
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

You can reference Frigate documentation on Reolink doorbell setup recommendation. https://docs.frigate.video/configuration/camera_specific#reolink-cameras Rule of thumb for reolink camera is to use HTTP-FLV stream as much as you can.

I haven't had any issue with the rtsp streams on either of my Reolink cameras (Wifi Doorbell, RLC-540A)

I believe earlier reolink models have pretty bad RTSP implementation. The RTSP stream on my RLC-510WA was extremely choppy and I have always used HTTP-FLV stream as much as possible. It also avoid the potential "backchannel" issue that other people were mentioning in the previous comment.

[EthanBezz]

Reolink has just released a new firmware on their website which “Add support for ONVIF audio-related commands.”

https://reolink.com/download-center/

Firmware version is v3.0.0.3308_2407315183

[vexersa]

Reolink has just released a new firmware on their website which “Add support for ONVIF audio-related commands.”

https://reolink.com/download-center/

Firmware version is v3.0.0.3308_2407315183

Thanks for the headsup. Would you know how configs would need to change for this to work in HA/Frigate?

[Cytomax55]

I don't fully understand the difference between onvif and rtsp and HTTP flv, but it seems we were using an rtsp stream before and this firmware is for onvif. Does this help us with two-way audio since we're using rtsp? Should we now change to onvif?

[alexdelprete]

Reolink has just released a new firmware on their website which “Add support for ONVIF audio-related commands.”

https://reolink.com/download-center/

Firmware version is v3.0.0.3308_2407315183

Downloaded this from reolink for my wifi doorbell and when manually updating, I always have this error (tried several times, redownloading too):

Anybody tried this?

[DMedina559]

Reolink has just released a new firmware on their website which “Add support for ONVIF audio-related commands.” https://reolink.com/download-center/ Firmware version is v3.0.0.3308_2407315183

Downloaded this from reolink for my wifi doorbell and when manually updating, I always have this error (tried several times, redownloading too):

Anybody tried this?

Did you unzip it? My wifi doorbell updates just fine

[AlexxIT]

ONVIF is just a "meta" protocol. Stream in 99% of the time transferred via RTSP.

[alexdelprete]

Did you unzip it? My wifi doorbell updates just fine

Sure. When you manually update, the Update web page will accept only *.pak files, you can't make those mistakes. :)

Must be something with communication with the doorbell, I don't know...

UPDATE: found the issue, I downloaded the fw for the white model. I didn't know the fw was different between white/black models.

[keithnet]

POE version of 3308 is here: https://community.home-assistant.io/t/2-way-audio-w-reolink-poe-doorbell/649469/64

2 way audio works for me now again in Home Assistant.

I does have bug tho: "Unfortunately it breaks the ability to send pre configured auto reply messages over REST commands. :("

v3.0.0.3308_2407315183 fixed auto reply messages over REST commands for me. 2 way audio is still working too.

[a-d-r-i-a-n-d]

The 2 way audio (WIFI version) seems to work again after this latest firmware update.

[vexersa]

The 2 way audio (WIFI version) seems to work again after this latest firmware update.

Would you be willing to detail your configuration?

[a-d-r-i-a-n-d]

I am fairly new to frigate so feel free to point out any mistakes. I've read that http stream is more reliable with Reolink cameras so here is my relevant config:

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

cameras:
  front_doorbell:
    webui_url: http://192.168.1.12
    detect:
      fps: 5
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/front_doorbell
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/front_doorbell_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
            # - audio

[Cytomax55]

@a-d-r-i-a-n-d do you have 2 way talk working?

[a-d-r-i-a-n-d]

@Cytomax55 yes it’s working with the configuration above and the latest firmware from Reolink.

[vexersa]

Thanks @a-d-r-i-a-n-d ,

Is your config similar to this (assuming you are using the Frigate card?):

Config:

type: custom:frigate-card
cameras:
  - camera_entity: camera.outside_gate_doorbell_v1_1
    live_provider: go2rtc
    icon: mdi:gate
live:
  draggable: false
  zoomable: false
  controls:
    builtin: true
    next_previous:
      style: none
    thumbnails:
      mode: none
  layout:
    fit: contain
  auto_unmute: selected
  preload: false
  lazy_load: false
  transition_effect: none
  show_image_during_load: false
  microphone:
    always_connected: true
performance:
  features:
    animated_progress_indicator: false
  style:
    border_radius: false
    box_shadow: false
timeline:
  show_recordings: false
menu:
  style: overlay
  buttons:
    frigate:
      enabled: false
    cameras:
      enabled: false
    live:
      enabled: false
    snapshots:
      enabled: false
    clips:
      enabled: false
    media_player:
      enabled: false
    microphone:
      enabled: true
      priority: 60
      type: toggle
    mute:
      enabled: true
      priority: 55
    screenshot:
      enabled: false
    timeline:
      enabled: false
    fullscreen:
      icon: mdi:overscan
  alignment: right
  position: top
  button_size: 70

My mic button does nothing, should it toggle on and off? I'd have thought so.

[a-d-r-i-a-n-d]

Mine is very basic, I've only been playing with frigate for a couple of weeks and focusing on reliability testing at the moment.

type: custom:frigate-card
cameras:
  - camera_entity: camera.front_doorbell
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
menu:
  buttons:
    microphone:
      enabled: true
      type: toggle
      alignment: opposing

Looks like you're missing the webrtc so you should change it to:

type: custom:frigate-card
cameras:
  - camera_entity: camera.outside_gate_doorbell_v1_1
    live_provider: go2rtc
    icon: mdi:gate
    go2rtc:
      modes:
        - webrtc
...

Also make sure that you have WebRTC enabled for your camera streams in the Frigate integration.