Detections missing

[Lieberkind72]

Describe the bug 3 days ago the camera stopped sending motion alerts to HA. The camera sends alerts to mobile app.

To Reproduce Steps to reproduce the behavior. Please provide the error from the log if possible.

Expected behavior I expect to receive alerts in HA as before.

Screenshots If applicable, add screenshots to help explain your problem.

Environment: Please provide useful information about your environment, like:

• Home Assistant 2021.12.1 supervised in raspberry pi 4
• Reolink camera RCL-811A
• Camera firmware v3.0.0.494_21073008

Additional context Add any other context about the problem here.

[cpainchaud]

Hi, can you check this please:

HomeAssistant must have an internal URL configured and:

• IT MUST NOT USE HTTPS : Reolink doesn't support HTTPS based Webhooks.

• URL also should not be using a DNS name but an ip address instead unless you have a solid DNS setup your camera is probably not able to resolve your address

[timknowlden]

I have the same issue. Using internal URL and http. Only 1 camera reliably reports motion and that is my e1 zoom. My 4 POE do not.

[timknowlden]

Hi, can you check this please:

HomeAssistant must have an internal URL configured and:

• IT MUST NOT USE HTTPS : Reolink doesn't support HTTPS based Webhooks.
• URL also should not be using a DNS name but an ip address instead unless you have a solid DNS setup your camera is probably not able to resolve your address

I have also noticed that when not using HTTPS there are only half the entities available for each device

[TravisRoy]

I am also not getting motion alerts on my RLC-810S

[magicianeire]

Hi Guys, same issue here, RLC-4205MP i actually found this integration couple of hours ago, installed and see no motion detected main stream : 25601920 25 fps fluent stream 640480 10 fps

update1: after changing in core.config_entries to not use https: "version": 1, "domain": "reolink_dev", "title": "House Front", "data": { "host": "192.168.0.20", "port": 80, "use_https": false, "username": "onvif", "password": "***", "channel": 1

getting following error: Logger: reolink.camera_api Source: /usr/local/lib/python3.9/site-packages/reolink/camera_api.py:869 First occurred: 11:53:32 PM (1 occurrences) Last logged: 11:53:32 PM

User onvif has authorisation level guest. Only admin users can change camera settings! Switches will not work.

thanks a mil

[iamakshar]

Having the same issues.... I am connected via port 80 and my internal URL is correct.

However, none of the motions are "available" in addition -- when I click on the image itself, I get a loading message error to see the logs...

Any help with this?

[magicianeire]

Update#2 guys, i've spent some time on meditating ;) and changing Integration settings and \config.storage\core.config_entries with different ports/streams/protocols

finally i was able to have some detections, some with this configuration : { "entry_id": "dea4f5e583b6085396cb852c40fe8ae3", "version": 1, "domain": "reolink_dev", "title": "House Front", "data": { "host": "192.168.0.20", "port": 80, "use_https": false, "username": "admin", "password": "**", "channel": 1 }, "options": { "protocol": "rtmp", "stream": "main", "stream_format": "h264", "motion_off_delay": 60, "playback_months": 2, "playback_thumbnail_path": "/", "timeout": 30

the problem is - camera became not accessible by my QVR Pro on my qnap and also became not accessible if i try to open it in the chrome by http://192.168.0.20:80/ :( - throwing request timeout and also, i dont really want to login as an admin to this camera

disabled an integration for the moment if required - can re-enable it and get a copy-paste of error log

stay safe and happy new year ;)

[simonkarrlsson]

Host 192.168.1.76 subscription failed to its webhook, base object state will be set to NotAvailable. Subscription process ended with wrong HTTP status: 400: Bad Request Host 192.168.1.76 error renewing the Reolink subscription

Anyone have the same issue?

[TravisRoy]

Update#2 guys, i've spent some time on meditating ;) and changing Integration settings and \config.storage\core.config_entries with different ports/streams/protocols

finally i was able to have some detections, some with this configuration :

I tried that, didn't work for me. Just trying to provide more info. RLC-810A

[arjungopisetty]

I'm encountering this issue with my setup as well. Internal URL uses http and the HA instance's IP address. Connected to the cameras via port 80.

This seems to be an intermittent issue, as some motion events are received but not all of them.

Environment:

Home Assistant 2021.12.0 in VirtualBox VM Reolink camera RLC-511W Camera firmware v2.0.0.654_20040905

[cpainchaud]

@Lieberkind72 v0.47 is out and the following was added in https://github.com/fwestenberg/reolink_dev/blob/master/TSHOOT.md: You can re-configure default timer called "Motion states update fallback delay (seconds)" for a specific camera, it defaults to 30 seconds but you can go down to 2-5 seconds. Because it will hammer your camera's API every X seconds, it may have CPU/RAM/stability impacts on your camera.

[TravisRoy]

Since the update, I'm still not getting motion detection, but the motion sensor is going unavailable every so often.

[cpainchaud]

Please enable debug logging (https://github.com/fwestenberg/reolink_dev/blob/master/TSHOOT.md) and provide logs

[drlauridsen]

Same here, no motion detections. Latest integration, RLC520A with latest fw 764. HA internal url config with local ip and http.