-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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 RLC-520A V2 not triggering AI sensors #89773
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 |
@dbiczo thank you for reporting this issue and sharing the debug log. Your camera (RLC-520A) does not (yet) support rich ONVIF notifications, therefore when receiving a ONVIF push it will poll the status of the AI detection which takes about 0.5 to 1.5 seconds. During this time the webhook callback task would be cancelled (or garbage collected), stopping the processing while still waiting on the response. I made this PR #89798 that will solve the problem and shields the callback from cancellation. This will make sure all motion events will come through. If you want 100% AI detection, the camera firmware needs to support rich ONVIF notifications: ONVIF WS base-notification messages schould include the Vehicle/Pet/Person rules and states. I do see there is a newer firmware version available for your RLC-520A: v3.1.0.951_22041566, you can get it from https://reolink.com/download-center/ |
If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library. |
Many thanks for your hard work. I believe the RLC-520A: v3.1.0.951_22041566 firmware is for the IPC_523128M5MP model not for the IPC_523128M5MP_V2 version which I have. There have been numerous requests for a firmware upgrade in the community forum to which I have added mine. Fingers crossed. |
Rather than opening another ticket these are my logs |
@Stuartyboy75 your reolink cameras are not able to reach |
@starkillerOG I was watching a video on Reolink with Blue Iris and have changed Frame Rate/Interframe Space/Frame Rate Mode on one camera then enabled your integration and its working far better now. Just need to find out what setting has made a difference so going to work backwards |
I found a newer firmware for the RLC-520A V2 hardware model that is not available on the reolink download centre: |
This will be resolved once HA 2023.04 is released on April 5th. If you still encounter any issues once you are on HA 2023.04, please let me know by making a new issue. |
@home-assistant close |
Great! i have the same problem, and i have resolved! Can you support me? or i have to create a new issue? i'm not sure because my problem probably is not an issue. Thanks |
Standard Ports Open web front end to camera to check |
allow traffic on all ports you have reported, from Camera to HA, the motion detection on HA is delayed of 60 seconds, due to the polling from HA to Camera. If I allow all port, the morion detection from HA panel is near real time. |
@robertoamd90 advanced network configurations like putting the reolink cams in a seprate restricted VLAN are not supported. |
The problem
Vehicle & person sensors are not being triggered by push notifications from RLC-520A V2 camera. It looks like ONVIF motion events are being received by the integration but not triggering the sensors.
The camera has firmware v3.1.0.801_22010701 and there is no available update.
Camera has push enabled and is on same local network 192.168.200.48 as home assistant.
Home assistant has local network set as http://192.168.200.4:8123/ and has webhooks enabled.
I also tried with reolink-aio 0.5.5 with the same result.
What version of Home Assistant Core has the issue?
2023.3.4
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
home-assistant_reolink_2023-03-15T07-25-28.165Z.log
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: