2-way Audio w/ Reolink PoE Doorbell

Community Guides
21

Possibly stupid question but just want to confirm. I do not have nginx proxy manager running at this stage. Could that be causing the issue? Im thinking no b/c LE on Home Assistant is managing the certificate but I’ve clearly been wrong about a lot of things so far.

I’ll re-factor the LE config to explicitly add ha.domain.casa. My base URL in Home Assistant is set to: https://ha.domain.casa. Looks like there’s an error.

Screenshot 2023-12-15 at 9.44.34 AM
Screenshot 2023-12-15 at 9.44.34 AM1218×796 60.4 KB

configuration.yaml

http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

22

Turn off the automatic switch - and it will let you put the https URL in as your local URL. No you do not Nginx Proxy Manager at this point.

23

Still hitting me with that error: Unable to fetch auth providers. https://ha.domain.casa:8123/?auth_callback=1. I restarted the server and now I cannot login with http, https, IP:port or server_name:port.

I clicked the certificate lock in Safari and it says something is misconfigured

Screenshot 2023-12-15 at 10.09.38 AM
Screenshot 2023-12-15 at 10.09.38 AM1218×570 101 KB

I owe you a coffee or beer for all this help :slight_smile:

24

OK I think we need to take this to private messaging at this point - so as not to completely derail this original topic.

1 Like
25

Major kudos and thanks to @mobile.andrew.jones for all of your help! And apologies to OP @peveleigh for threadjacking.

Here’s what fixed the issue:

  • Added ha.domain.tld to my Let’s Encrypt configuration yaml and regenerated certificate
  • Apparently the wild card *.domain.tld wasn’t specific enough so I made it explicit
  • Passed https://ha.domain.tld:8123 to Settings > Network > Home Assistant URL
  • Added ha.domain.tld to pfSense > Services > DNS Resolver > Host Override

Now the kicker is that after doing all of this and navigating to the site everything looked like it was going to work and then poof the browser started throwing errors like the server was unresponsive. The fix turned out to be disconnecting from my VPN, which makes no sense to me. But, now it’s working.

1 Like
26

I just got my setup working with the help of HomeAssistant and Reolink Doorbell POE - Third party integrations - Home Assistant Community (home-assistant.io).

Really nice!

27

I have no idea why the Frigate card won’t work for me but webrtc card will. Here’s my Frigate card config:

type: custom:frigate-card
cameras:
  - camera_entity: camera.front_door_frigate
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
      stream: camera.front_door
menu:
  buttons:
    microphone:
      enabled: true
      type: toggle
live:
  microphone:
    always_connected: false

For whatever reason the microphone button doesn’t show up under the menu once enabled.

28

this seems wrong, that should be what it is named in frigate

29

That’s the go2rtc stream camera. I tried swapping it with the frigate camera and it didn’t make a difference.

For what it’s worth, I don’t run go2rtc alongside Frigate. It’s running its own LXC with Frigate in a different LXC.

30

Well there’s your problem

31

Hi @peveleigh you mention to add ‘go2rtc’ and ‘webrtc’ from HACs. But HACs only has WebRTC Camera and Integrations only has ‘RTSPtoWebRTC’. Are these what you mean that must be installed? Please advise.

32

That’s the one you’re looking for.

33

@crzynik Can you define what the problem is? I’m trying to get 2-way audio working on my Reolink POE Doorbell cam as well and the hass-frigate-card isn’t working as expected. I have HA running over HTTPS now via Lets Encrypt add on. Frigate is running on unRAID presently and passing games via MQTT to HA. Soon they will both be on the same dedicated hardware to eliminate some of the go-between.

34

Thanks partner!

35

The integrated go2rtc must be used with the frigate card. I also see no reason to run an external go2rtc gicven that all features are supported in the internal go2rtc and it is possible to use any version of go2rtc inside frigate

1 Like
36

Other than the external implementation as suggested by OP, do the rest of the steps make sense to implement in hass-frigate-card?

37

The reason is because the inbuilt go2rtc has a habit of crashing far more frequently than running go2rtc outside of the frigate container.

38

Probably because it’s the default version go2rtc 1.2 in frigate 0.12 but it can of course can be updated and that fixes issues for the vast majority of users. Frigate 0.13 runs go2rtc 1.8.4.

The difference is not because it’s running in frigate vs a separate container.

39

I was able to easily update my Frigate go2rtc to 1.8.4 by following these instructions @ https://www.youtube.com/watch?v=upXyBVMR4RM (about mid way through).

1 Like
41

@peveleigh Where is the go2rtc.yaml file to be saved? I did not see it in config or custom_components. Do I have to create it myself and if so, where?