-
-
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 Wifi doorbell sensors stop working after becoming unavailable #130237
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 |
First off, I see you are not running the latest firmware of the doorbell, I would advice updating to v3.0.0.4110_2410111119 (although probably unrelated). Secondly there is a update in the latest HA 2024.11.0 which might help you: you are currently using ONVIF long polling which is very CPU intensive for the doorbell. HA 2024.11.0 implements a new push mechanism using the Baichuan protocol over TCP. That may already help you a lot. About your actuall issue: Do you see any errors in the log about Reolink? What I need: |
Same problem here after update HA core. It doesn't look to me the sensors becoming unresponsive is connection related as I have no connection drops. POE doorbell, firmware v3.0.0.3308_2407315182. When I have my doorbell camera live view open on my HA dashboard, the sensors become unresponsive after some time. Eg, motion sensor in home assistant doesn't trigger anymore. Same thing when pressing the doorbell button, the sensor binary_sensor.reolink_video_doorbell_poe_w_visitor doesn't respond anymore. All interactivity in de Reolink client app (on mobile) continues to function. To a complete noob as I, it just seems the HA integration doesn't respond anymore with the exception of live camera view. Issue started yesterday after my upgrade to HA 2024.11.1 (coming from HA 2024.03, so older version). Reloading the integration fixes the issue temporary. Reolink firmware: v3.0.0.3308_2407315182 |
@Jieper001 any errors in the log? What I need to resolve this: |
@thedeitz could you provide me the needed debug log? |
This should be solved in HA 2024.12.0 which will be released tomorrow. Please let me know if you still have issues after updating to HA 2024.12.0 If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library or purchase Reolink products through this affiliate link. |
The problem
Hello,
I have been having an annoying issue with my Reolink Wifi doorbell. I am using the official integration and am using a handful of automations for motion and visitor sensors however each time the connection goes down temporarily (usually once every other day or so) when it come back up the sensors will no longer work. The camera feed and everything shows as normal however sensors will not come though. I have to go into the device in HA and reconfigure before it will start picking up again.
After reading several posts on here I turned off RTMP, RTSP, HTTPS in the reolink settings (therefore I am only using HTTP), set my protocol in HA to FLV, and also made sure in HA network settings that the local network is pointing to the actual IP of my HA instance. Doing this made it a little more stable but no matter what if the device disconnects at any time the sensors will no longer work.
Reolink firmware: Firmware: v3.0.0.3308_2407315182
HA 2024.10.4 Docker installation
What version of Home Assistant Core has the issue?
2024.10.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Reolink IP NVR/camera
Link to integration documentation on our website
https://www.home-assistant.io/integrations/reolink
Diagnostics information
config_entry-reolink-186f918ab523bd769d5ec3d70b35e2b9.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: