#Reolink PoE Doorbell + Frigate + HA with Two-Way-Audio working.

1 messages · Page 1 of 1 (latest)

vale kraken
#

I know this has been discussed ad nauseum for 5 years now and there are a ton of posts about it. None of those posts, however, seem to address my issues.

What I have:

  • Reolink PoE doorbell w/static IP. (http, https, rtsp enabled)
  • Frigate working with recommended frigate config for reolink
  • Two way audio working in frigate.
  • WebRTC specified in frigate config.

What I've tried:

  • I've tried installing the WebRTC-Camera HACS integration (and configuring it as an integration)
  • I've used the advanced camera card and set up the go2rtc options as recommended. (go2rtc as provider, webrtc as live view provider).

It seems that no matter the combinations of things I've tried, suggestions from months/years past, etc... nothing seems to get me a microphone button in the advanced camera card within HA. And, not only do I not get two-way-audio, but the framerate drops to about 1fps and the video looks worse than the substream. Something maybe borked in the go2rtc implementation? It's a current build of frigate, so go2rtc should be 1.9+ at least. It should be noted that if I use the HA built in stream option, it's crystal clear, smooth and I at least have one way audio.

Legend:
10.50.0.50 - frigate server
10.50.1.30 - Doorbell camera
8555 tcp and udp are exposed from docker

Configs are attached as txt file.

Let me know what I'm missing. Thanks.

📎 Frigate-Doorbell-Broken-Configs.txt
jaunty storm
#

Just as a double check since I didn't see you mention it... are you accessing HA over HTTPS?

vale kraken
#

Yes..

#

Sorry, missed that.

#

Both frigate and HA are https.

#

Wait.... I take it back... It appears I've fallen back to http on HA. frigate is HTTPS

#

Dammit.. that's probably it, eh?

jaunty storm
#

Definitely a possibility

vale kraken
#

Actually, now that I'm thinking about it.. I'm not sure I ever set that up..... derp. Know of a good guide on how to do that - specficially within HA and not an external ssl termination.

jaunty storm
#

That will break anything that connects over http to HA though, since HA will serve either via HTTP or HTTPS

#

If you wanted both, you'd need to go a reverse proxy route

vale kraken
#

Alright, so do you know of an easy peasy self-hosted docker style reverse proxy manager? I'm capable of doing it the manual way, but I do this crap full time for my job and already have too much self-hosted stuff. I'd like to minimize my home complexity. 🙂

jaunty storm
#

I use Nginx Proxy Manager, super simple to set up new proxy hosts. You can get one wildcard cert for a domain and use it across everything easily.

#

A tip to save potential frustration is to remember to enable Websockets support (toggle when creating a new host)

vale kraken
#

Awesome. Thanks.

vale kraken
#

FYI, this worked... Got NPM working and everything is solid now.

stone tulip
#

@vale kraken still struggling getting two-way audio to work, also in frigate. Since you have the same doorbell, would you be so kind to provide (maybe private) your frigate config to me?

vale kraken
stone tulip
stone tulip
#

@vale kraken this conversation

novel matrix
# vale kraken FYI, this worked... Got NPM working and everything is solid now.

Thanks bud, This thread helped out quite a bit since I've been struggling with this for weeks.
I actually ended activating my 1 month free trial of Nabu just to get HA on HTTPS some way and was able to get 2-way audio to work for a split second in HA. I had also set my Frigate on HTTPS with NPM since it was using a self-signed cert and HA would not trust it. Now I just have to find a way to keep it working, not sure if now I just am having issues with the Advance Camera config file.