-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reolink integration does not trigger binary_sensor.visitor in case video doorbell button pressed #91041
Comments
Hey there @starkillerOG, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) reolink documentation |
@fr33pr0d do you see any repair issues about the reolink integration? Partly this will be fixed by #91070, but I am doubting if ONVIF pushes are comming through correctly in your system. |
Local URL: http://192.x.x.x:8123 |
If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library. |
@starkillerOG thanks, I'll wait for the update 👍🏻 |
Hmm, still seems to be very slow here when it works(takes about 10seconds before HA detects the doorbell push Ps: just added myself as a sponsor, because you're doing a great job keeping this code up to date ! |
@palmerch1 thank you very much for sponsering! Please hold on for a few more days untill HA 2023.4.5 is available, and please let me know if it is working once you upgraded. |
HomeAssistant 2023.4.5 is now available and includes the ONVIF push fix. |
@home-assistant close |
The problem
Reolink integration does not trigger binary_sensor.visitor in case video doorbell button pressed.
What version of Home Assistant Core has the issue?
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Reolink IP NVR/camera
Link to integration documentation on our website
https://www.home-assistant.io/integrations/reolink
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Unfortunately this issue persists and it looks like it made it worse than before. Now it detects about 20% of doorbell presses and even when it works, it "detects" it a good few minutes after the button press. Everything else works absolutely fine. I still have HTTP set, I also tried with it off and it doesn't work at all. Enabled it back and it works 2 times out of 10-ish.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: