Reolink "Did not receive initial ONVIF" after upgrade to 2023.4.0

[capsel22]

The problem

Getting Reolink webhook URL unreachable // Did not receive initial ONVIF state from CCTV Camera after updating to 2023.4.0. No issue on 2023.3.6

Screenshot attached.

I've removed integration and re-added all my cameras, however this error message doesn't clear.
I also checked if my https/http links changed after upgrade, but everything looks correct. Changing them creates the usual SSL error for motion sensors. So I think everything is correct in "Network" tab.

Not sure where to find any additional logs, if you let me know I'll be happy to supply.
Those are RLC-420-5MP , no NVR

What version of Home Assistant Core has the issue?

2023.4.0

What was the last working version of Home Assistant Core?

2023.3.6

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

[home-assistant]

Hey there @starkillerOG, mind taking a look at this issue as it has been labeled with an integration (reolink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of reolink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign reolink Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

reolink documentation
reolink source
_{^{(message by IssueLinks)}}

[capsel22]

Think I managed to work out how to enable debug mode.

I'm not sure what I am looking at but the only thing which keeps repeating is
"cmd" : "GetAudioAlarm",
"code" : 1,
"error" : {
"detail" : "ability error",
"rspCode" : -26

home-assistant_2023-04-06T13-27-01.114Z.log

[cmille34]

Think I am in the same boat here. Oddly enough, it only references 1 of my 2 cameras in the error message

[starkillerOG]

@capsel22 try changing the local HTTP URL to the IP adress of the HomeAssistant device (as the example states) instead of your duckdns URL.

@cmille34 how does your HTTP URL look like?

[starkillerOG]

@capsel22 the "ability error" is unrelated.

[capsel22]

@capsel22 try changing the local HTTP URL to the IP adress of the HomeAssistant device (as the example states) instead of your duckdns URL.

@cmille34 how does your HTTP URL look like?

Yes I've tried this and other variations of the http address and nothing seem to clear the ONVIF error. I think the http is set correctly, if I misconfigure it I get the SSL error for motion sensor and as far as I can tell everything works except this ONVIF error showing.

[TekFan]

Same problem here with my RLC-511, I tried to fiddle with the network settings with no result, error is still there.
And the consequence is that events don't go through anymore (motion detection).
Everything was perfectly working in 2023.3.6

[cmille34]

@cmille34 how does your HTTP URL look like?

@starkillerOG my HTTP URL in network settings looks right. http://192.168.1.104:8123 The URL is accessible fine, the camera is on the same VLAN and wired. The camera that is triggering the repair notifiication is:

DrivewayDuoCam
Reolink Duo PoE
by Reolink
Firmware: v3.0.0.1388_22100600
Hardware: IPC_528B174MP

The other camera below isn't mentoined in the error:

CatioCam
RLC-810A
by Reolink
Firmware: v3.1.0.956_22041503
Hardware: IPC_523128M8MP

For reference, below is the full "error"/notifcation I get when HomeAssistant starts up now.

Did not receive initial ONVIF state from DrivewayDuoCam. Most likely, the Reolink camera can not reach the current (local) Home Assistant URL http://192.168.1.104:8123, please configure a (local) HTTP address under "Home Assistant URL" in the [network settings](https://my.home-assistant.io/redirect/network/) that points to Home Assistant. For example http://192.168.1.10:8123 where 192.168.1.10 is the IP of the Home Assistant device. Also, make sure the Reolink camera can reach that URL.

Both cameras appear to be working though. I see motions alerts being recognized and cleared on the device page for each camera.

[TekFan]

My cameras are:

RLC-511
by Reolink
Firmware: v3.0.0.142_20121803
Hardware: IPC_51516M5M

Hard wired, HA url is ok, I tried direct ip and normal .local address and HA is perfectly reachable in both cases

But contrary to cmille34, I don't see anything in the log, only the repair notification in system.
And in my case, motion detection is not registering anymore.

[starkillerOG]

The repair issue is new in HA 2023.4, but even if it is raised, the underlying connection is not changed.
So in 2023.3 the same problem could be present, but you would just not get a notification about it and not know the ONVIF pushes were not working.

As a backup in both 2023.3 and 2023.4 polling of the motion/AI state is done every 60 seconds, but that is a game of change if it catches the motion/AI event. About 20% of motion events is captured using polling at 60 seconds and is therefore quite unreliable.

It seems unlikely that ONVIF pushes were working in 2023.3 and stopped working on 2023.4, If that is really true, I would need 2 debug logs: one on 2023.3 and one on 2023.4 in the same situation, one showing the ONVIF pushes in the debug log and the other not.

[starkillerOG]

If you turn on debug logging and see the ONVIF pushes comming in for the camera that is giving the repairs issue, it could be that only the initial state is not pushed by the WS base subscription and then there is potentially something I can do about it.

If you never see ONVIF pushes from the camera, there is some issue in your network configuration, which I can do nothing about.
This can also be because your router/AP is blocking the ONVIF pushes at some point in your network.

At last a possibility could be that your specific camera model does not support ONVIF WS base notifications. In that case I would be really intrested to know which models do not support this. I do see this list on the reolink site: https://support.reolink.com/hc/en-us/articles/900000617826-Which-Reolink-Products-Support-CGI-RTSP-ONVIF but I have no idea if that is accurate. If that is the case I could increase the polling intervall for those models to not mis so much motion/AI events, but than there will always be a delay between the detection and HomeAssistant showing the change. And this is resource intensive on the camera, HomeAssistant and your network.

[Lezcarr]

Same happened for me, same boat as you guys

[TekFan]

It seems unlikely that ONVIF pushes were working in 2023.3 and stopped working on 2023.4, If that is really true, I would need 2 debug logs: one on 2023.3 and one on 2023.4 in the same situation, one showing the ONVIF pushes in the debug log and the other not.

It could be possible that I had the chance to just be in a polling event when I saw motion detection working with the previous HA version. To be honest, I never checked if it worked every time.
I could try to have a debug trace tomorrow, but how do I put this integration in debug mode ?
Or is it only via the global setting in configuration.yaml ?

[starkillerOG]

@TekFan you can enable debug mode by going to settings->devices->reolink integration of the camera overflow menu (three dots)->enable debuging