core: Reolink integration not showing doorbell notification for Reolink Doorbell

The problem

Reolink integration not showing the camera as a doorbell in the home kit integration,

image

The more likely question is, if this integration should provide automatically linked_doorbell_sensor (from https://www.home-assistant.io/integrations/homekit/#linked_doorbell_sensor) or if this integration can provide it automatically šŸ¤”

if nope, should we update documentation? (I can do that)

What version of Home Assistant Core has the issue?

2023.2.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Reolink

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

diagnostic log config_entry-homekit-0b91fabfe70646541ef30e334922d2b2.json.txt

you can see that linked_motion_sensor is there but not linked_doorbell_sensor

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 88 (26 by maintainers)

Most upvoted comments

I have the same problem, maybe it’s because I’m using HTTPS, but I don’t want to disable it. Instead I found a workaround for now: I have enabled the ā€œLast Notificationā€ sensor in the Home Assistant app on my (Android) phone. When someone rings my doorbell, I get a notification from the Reolink app on my phone with the text ā€œVisitor from NameOfDoorbellā€. This is also the sensor text in Home Assistant and it’s the trigger for my automation.

If there is a way to fix the visitor sensor with HTTPS, that would be great.

OK found the missing piece if you browse to the doorbell ip, go to settings, network, advanced and then port settings youl find HTTP port disabled by default switch that on , and done! working great so far!

I have installed the NGINX Home Assistant SSL proxy addon, i can now access my home assistant with http. But i can not access with https What i am doing wrong

I have it done again i see the addon is not starting. I have checked the logs, i can not see an error

image

image

I have fix it, NGINX is now running and the Reolink Doorbell is working.

Following this thread, my issue was the HTTPS portion too. I have both internally and externally configured my HA to respond to a FQDN with a valid certificate. I changed this, reinstalled the integration and it worked. Hopefully there are no downsides to changing the internal address. Thanks.

How do you do this in your certifcate? I am not a hero with certificates

I’m using a free certificate of Let’s Encrypt, my nginx proxy manager is doing the renewals and does the reverse proxy functionality. My internal DNS just points to the internal IP of the ngix and externally port 443 is redirected to the reverse proxy too. So basically HA isn’t doing anything with certificates, all is handled by my reverse proxy.

If the binary sensor has device class occupancy and it’s on the same device as the camera it will automatically get picked up

@bdraco but that would mean the states will show in the UI as occupied and not occupied instead of on and off right?

I personnaly think those states would be a bit weird for a doorbell press…

Yes. That’s is historically what has been used for doorbells in all the other integrations.

@Kepro sure, I will change it to occupancy, I don’t have strong fealings about it.

PR to implement the device class is here: https://github.com/home-assistant/core/issues/87134

I have this problem too. I use the official integration of Reolink. All sensors work except the visitor. It just doesn’t respond, removed the integration several times, but this doesn’t want to solve it. I have had the reolink at home for a week, at first I couldn’t get it to work via Hacs either. All Hacs integrations related to Reolink are no longer there. It is not the Reolink itself, since their app neatly gives the notifications.

@smarthomejunkie good to hear it is working for you now.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library.

Done šŸ˜‰

@smarthomejunkie good to hear it is working for you now.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library.

Okay, I removed the official integration, rebooted HA and installed the official integration again and I can confirm that that solved the issue.

Hey @starkillerOG thanks for reply, yeah I was digging into homekit/reolink integration, but as I was using ā€œUIā€ integration rather than YAML, but yeah after 2 hours I ended up with YAML 😃

but yeah I’m pointing this out because people will ā€œexpectā€ to work it out of the box, so any help from code or even from documentation will help… 😃 both of you great work btw!

- name: Doorbell
  port: 21066
  mode: accessory
  filter:
    include_entities:
      - camera.doorbell_sub
  entity_config:
    camera.doorbell_sub:
      support_audio: true
      linked_motion_sensor: binary_sensor.doorbell_motion
      linked_doorbell_sensor: binary_sensor.doorbell_visitor