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,

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
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of homekit can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleChange the title of the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign homekitRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
homekit documentation homekit source (message by IssueLinks)
ah, bot picked Homekit instead of Reolink... ping @starkillerOG
@Kepro the "Visitor" binary sensor are the doorbell presses, so you can use that entity_id to configure it in YAML.
@bdraco I know nothing about HomeKit, is it possible to set the linked_doorbell_sensor automatically?
Do I have to set some sort of device class or something in the reolink integration code to let HomeKit recognize the correct binary sensor?
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
I can confirm that the visitor entity is not reliable. When someone pushes the doorbell button, the visitor entity sometimes turns to "on", but most of the time it does not respond. Also, the visitor-detected trigger does not work because of this. This worked fine in the HACS integration that I used before.
I had the HACS integration and the official integration installed simultaneously and removed the HACS integration because entities were shown double. Not sure if that has something to do with this behavior.
@smarthomejunkie can you tell me more about your configuration: Wifi or PoE doorbell? Which firmware version? direct connection or connected to NVR? If NVR, connected to which channel and what is the NVR firmware?
The custom reolink integration or ONVIF integration can interfer with the pushes, please only use the official reolink integration when testing and reboot HomeAssistant if you removed a custom integration.
@smarthomejunkie can you tell me more about your configuration: Wifi or PoE doorbell? Which firmware version? direct connection or connected to NVR? If NVR, connected to which channel and what is the NVR firmware?
The custom reolink integration or ONVIF integration can interfer with the pushes, please only use the official reolink integration when testing and reboot HomeAssistant if you removed a custom integration.
I use the WiFi version with the latest firmware v3.0.0.1459_22102806 I connected it directly to HA. The custom integration is removed a couple of days ago and I rebooted HA multiple times after that. I will try to remove the integration, reboot HA and reinstall the integration.
Okay, I removed the official integration, rebooted HA and installed the official integration again and I can confirm that that solved the issue.
@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.
@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 ;)
Thank you so much!, you are my first monthly sponsor :)
Thank you so much!, you are my first monthly sponsor :)
I know how important that is. I am dependent on sponsorships myself.
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.
@Kepro the "Visitor" binary sensor are the doorbell presses, so you can use that entity_id to configure it in YAML.
@bdraco I know nothing about HomeKit, is it possible to set the
linked_doorbell_sensorautomatically?Do I have to set some sort of device class or something in the reolink integration code to let HomeKit recognize the correct binary sensor?
If the binary sensor has device class occupancy and it's on the same device as the camera it will automatically get picked up
@Kepro the "Visitor" binary sensor are the doorbell presses, so you can use that entity_id to configure it in YAML. @bdraco I know nothing about HomeKit, is it possible to set the
linked_doorbell_sensorautomatically? Do I have to set some sort of device class or something in the reolink integration code to let HomeKit recognize the correct binary sensor?If the binary sensor has device class occupancy and it's on the same device as the camera it will automatically get picked up
Do you have an example how i can configured this?
@avdgaag1984 you can do it as I done it
- 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
rest is for @starkillerOG to implement it to reolink integration, thanks @bdraco for info!
@avdgaag1984 you can do it as I done it
- 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_visitorrest is for @starkillerOG to implement it to reolink integration, thanks @bdraco for info!
Okay Thanks, should just stand? And that port number where do I get it from
@avdgaag1984 please follow official documentation https://www.home-assistant.io/integrations/homekit/ or wait for fix/implementation :-)
@avdgaag1984 please follow official documentation https://www.home-assistant.io/integrations/homekit/ or wait for fix/implementation :-)
I think I misread, I don't have homekit running on my home assistant. But I do have problems with my visitor sensor :(
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.
The HACS integrations are still there. You might have to add the repository to HACS first in your case. It's this one: https://github.com/JimStar/reolink_cctv
But, the official integration does work on my side now. Not sure why it's not working on yours.
Home Assistant 2023.2.2 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230202.0 - latest
Reolink Wi-FI Doorbell Firmware v3.0.0.1459_22102806 Running through the NVR or Standalone the visitor doesn't report on state. I have tried removing the addon rebooting and readding it but I still don't get Visitor update on state. I will try the hacs version and report if that works to report Visitor state. Thanks for working on the Reolink Integration.
It also fails to report for me using https://github.com/JimStar/reolink_cctv Hacs integrations it simply shows as off or unavailable
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...
@starkillerOG well answer it again :D on / off for the visitor is still "somebody is on your front door and pressed the bell" so it's more likely occupancy rather than on/off state no?
@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
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
occupiedandnot occupiedinstead ofonandoffright?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.
@avdgaag1984 could you provide some extra info about your setup:
Doorbell Wifi or POE?
Direct connection or through NVR?
Firmware version of doorbell (and if applicaple NVR)?
Do you use HTTP or HTTPS for the local connection to HomeAssistant?
What URL do you have configured under settings->system->network->Home Assistant URL->local network?
@yaggermr alright you do seem to have the latest firmware version of the wifi doorbell. The visitor sensor of the doorbell will not work when connected to a NVR on the latest released NVR firmware. Beta NVR firmware v3.0.0.211_23011204 fixes this issue, you can request beta firmware from reolink support, release firmware is expected in a few weeks. (stated in the reolink homeassistant docs).
When connecting the Wifi doorbell directly to HomeAssistant on the latest firmware it can work.
Probably the webhook pushes are not comming through correctly:
What URL do you have configured under settings->system->network->Home Assistant URL->local network?
@avdgaag1984 could you provide some extra info about your setup: Doorbell Wifi or POE? Direct connection or through NVR? Firmware version of doorbell (and if applicaple NVR)? Do you use HTTP or HTTPS for the local connection to HomeAssistant? What URL do you have configured under
settings->system->network->Home Assistant URL->local network?
-
Doorbell POE
-
Direct connection
-
Last Firmware

-
Https for the local connection

can is change a setting when i want both (http and https) ?
I would say just use automatic, using https in local (home) network is not necessary