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

[TekFan]

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.

Well motion detection works perfectly via ONVIF in Surveillance Station (Syno. NAS), so I'm sure ONVIF push is supported on my cams.

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.

I see the RLC-511W is listed as ONVIF capable but not my RLC-511 POE, but it's support ONVIF OK, as I said it works perfectly with my NAS and the ONVIF port is set in the camera config.
So I guess this list is quite incomplete.

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.

Yeah, I'm afraid that's not a good idea, it will load the network, the cameras and HA and you will still miss very short events anyway.

[starkillerOG]

@TekFan do note that ONVIF does also support polling wich I do not use because the HTTP API is better for that. The pushes are comming from the ONVIF WS base notification pushes, not the ONVIF pull point subscription.

It might still be that the Surveillance Station is using the ONVIF pull point subscription, I do not know....

I really need a debug log to see what is going on.

[TekFan]

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

Jeez, Im stupid, I completely forgot about this option, thanks !

[starkillerOG]

@TekFan just for a test, could you turn off your Syno NAS/Survailance Station and then restart HomeAssistant and see if it is then working?
Maybe the camera can only handle a single ONVIF WS base subscription and the Survailance Station and HA are fighting for the same subscription???

[capsel22]

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.

I can run another debug and will upload later. I don't have logs from 2023.3 though

Looking at this list you linked my camera 420-5mp does not support ONVIF which would explain the error and why it's not receiving expected ONVIF. Interestingly the webgui of the camera does have setting to change the ONVIF 8000 port, so not sure if list is inaccurate or the setting doesn't do anything.

As mentioned before, motion works and everything else does too just the error.

You mentioned in another comment about network setup. In my case, I've got a flat network everything on the same IP range. The cameras and HA don't even go through a router, don't think anything is being filtered.

[starkillerOG]

@capsel22 In that case I would be really interested in a debug log when you wave in front of the camera mentioned in the repairs issue/warning. Please restart HomeAssistant while debug mode is on, I can then see what is going on and can adjust the code acordingly.

[TekFan]

@TekFan do note that ONVIF does also support polling wich I do not use because the HTTP API is better for that. The pushes are comming from the ONVIF WS base notification pushes, not the ONVIF pull point subscription.

It might still be that the Surveillance Station is using the ONVIF pull point subscription, I do not know....

I really need a debug log to see what is going on.

Got it, but as notifications are instantaneous in the SS UI, I don't think it's polling.

@TekFan just for a test, could you turn off your Syno NAS/Survailance Station and then restart HomeAssistant and see if it is then working?
Maybe the camera can only handle a single ONVIF WS base subscription and the Survailance Station and HA are fighting for the same subscription???

Yeah, I thought about that as well. I could try this if it occurs again, because.... actually now it works !
I don't get it, I swear, it was not working, I tried several times this evening to no avail.
Now, I reloaded the integration, I restarted the core, several times, but mostly to try to get rid of the repair notification so I didn't try the motion detection during all these attempts .
So I'm not sure what fixed that part.
But at least it seems more in sync with what others are experiencing in this thread.
I think I was the only one not receiving motion notifications.
That said, the repair error is still there but now at least doesn't impair normal use.
Sorry to have waisted your time.

I just had time to do a debug session and it's full of this:

2023-04-06 20:17:17.561 INFO (MainThread) [reolink_aio.api] Reolink Entree ONVIF event channel 0, Motion: True
2023-04-06 20:17:21.604 DEBUG (MainThread) [homeassistant.components.reolink.host] Webhook 'reolink_0123456789ab_ONVIF' called

So I guess the webhook is working ?

[capsel22]

@capsel22 In that case I would be really interested in a debug log when you wave in front of the camera mentioned in the repairs issue/warning. Please restart HomeAssistant while debug mode is on, I can then see what is going on and can adjust the code acordingly.

Right ok, so this is getting wierd now.
I've enabled debug, restarted HA and motion alerts are no longer coming throught. I'm not getting any SSL errors or anything just the ONVIF error. But I stood there was waving my hands and HA not registered any movements. I can see the movement triggered in Reolink app, just not pushed to HA.

not quite sure where to go from here

home-assistant_reolink_2023-04-06T18-50-17.081Z.log

[TekFan]

Mmmm, I'm going nuts...
Like I said previously, motion was finally working, I could see the web hook calls in the log.
Now, to be sure everything was "clean" after all my fiddling, I deleted the camera and the integration and reinstalled them afterwards.
It wen well, except now the web hook is not called anymore...
So no more motion notification, again.
I tried everything again and again, even disabling the camera in Surveillance Station, restarting everything, HA, the camera, etc, multiple times.
And...nothing. Webhook dead, nothing in the log but the regular polling with no error, except for the audio (ability)
I give up for today, I will try to downgrade tomorrow to see if fixes anything.

[capsel22]

Same boat as you @TekFan motion was working, restarted not working. Removed integration and readded; motion works, enabled debugging - stopped. Really fiddly. I'm trying to catch some useful data to analyse but can't work this out.

I'm also using QNAP with QVR but looks like I'm not using ONVIF but RTSP. At least that's what the QVR setup shows

[starkillerOG]

2023-04-06 20:17:17.561 INFO (MainThread) [reolink_aio.api] Reolink Entree ONVIF event channel 0, Motion: True
2023-04-06 20:17:21.604 DEBUG (MainThread) [homeassistant.components.reolink.host] Webhook 'reolink_0123456789ab_ONVIF' called

Yes that means the webhook is working and you are receiving ONVIF events

[starkillerOG]

I'm also using QNAP with QVR but looks like I'm not using ONVIF but RTSP. At least that's what the QVR setup shows

@capsel22 As far as I am aware RTSP is only video so in that case QNAP would not have any awerness of motion/people/vehicle events etc. If QNAP does show the events it is most likely using RTSP for the video feed and ONVIF for the notifications, or it is doing its own AI processing to detect events. No idea how QNAP works.

[starkillerOG]

I think it is a bit of a coincidence that both @capsel22 and @TekFan are having issues while they both also have a NAS connected to the camera. So it might be the NAS having some connection to the camera causing these issues.

[capsel22]

I think it is a bit of a coincidence that both @capsel22 and @TekFan are having issues while they both also have a NAS connected to the camera. So it might be the NAS having some connection to the camera causing these issues.

yes it could be. Just strange on 2023.3 everything worked. I will turn my qnap off and do a few tests

[TheCruelSloth]

I think it is a bit of a coincidence that both @capsel22 and @TekFan are having issues while they both also have a NAS connected to the camera. So it might be the NAS having some connection to the camera causing these issues.

I'm also having these problems. Thing is, the video doorbell is connected to my NAS (Synology) and is working alright. The indoor cam (E1 Zoom) is not connected to my NAS and is giving me an error.
It gave me also a "integration broken" after I rebooted the camera it was gone.
There was a line in the log when it occurred with something "not being able to access the ONVIF port".

[Lezcarr]

Good morning The webhook message has now gone, will monitor and give feedback Thank you again for your invaluable assistance

…

On Thu, 20 Apr 2023 at 13:00, starkillerOG ***@***.***> wrote: @Lezcarr <https://github.com/Lezcarr> in that case I am not sure why it is not working. Do you have the doorbell in a seperate VLAN perhaps? Any other non basic network configurations? Could you enable debug logging under Settings->Devices & Services->Reolink integration overflow menu (three vertical dots)->Enable debug logging, Then restart Home Assitant, wait untill it is fully stated, press the doorbell and make some motion events in front of the doorbell, disable debug logging and post the log here. I can then have a look if I can see anything out of the ordinary. — Reply to this email directly, view it on GitHub <#90931 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOHKWUB6IM5LWVIOKKYPQD3XCEQM7ANCNFSM6AAAAAAWVLFTDM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Valiante]

I have this morning received updated firmware for the E1 Zoom from Reolink support (v3.0.0.2138_23042609), which they asked me to test. Unfortunately it appears to have broken something in HA:

I wonder whether I should try any troubleshooting before going back to them?

Edit: Added debug logs: home-assistant_reolink_2023-05-03T09-53-33.214Z.log

Edit 2: I tried removing and-readding the camera to HA, only to be met with "Host 192.168.1.161:443: failed to subscribe, could not find TerminationTime". I tried enabling HTTP only (disabling HTTPS) but the same message is received on port 80. All errors seem to pertain to this missing TerminationTime.

[starkillerOG]

@Valiante I looked through your debug log and this is the subscription response your camera is sending:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:ns1="http://www.onvif.org/ver10/actionengine/wsdl" xmlns:ns10="http://www.onvif.org/ver10/events/wsdl/PullPointBinding" xmlns:ns11="http://www.onvif.org/ver10/events/wsdl/CreatePullPointBinding" xmlns:ns12="http://www.onvif.org/ver10/events/wsdl/PausableSubscriptionManagerBinding" xmlns:ns13="http://www.onvif.org/ver10/network/wsdl/RemoteDiscoveryBinding" xmlns:ns14="http://www.onvif.org/ver10/network/wsdl/DiscoveryLookupBinding" xmlns:ns3="http://www.onvif.org/ver20/analytics/wsdl/RuleEngineBinding" xmlns:ns4="http://www.onvif.org/ver20/analytics/wsdl/AnalyticsEngineBinding" xmlns:ns5="http://www.onvif.org/ver10/events/wsdl/PullPointSubscriptionBinding" xmlns:ns6="http://www.onvif.org/ver10/events/wsdl/EventBinding" xmlns:ns7="http://www.onvif.org/ver10/events/wsdl/SubscriptionManagerBinding" xmlns:ns8="http://www.onvif.org/ver10/events/wsdl/NotificationProducerBinding" xmlns:ns9="http://www.onvif.org/ver10/events/wsdl/NotificationConsumerBinding" xmlns:tad="http://www.onvif.org/ver10/analyticsdevice/wsdl" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:tdn="http://www.onvif.org/ver10/network/wsdl" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tls="http://www.onvif.org/ver10/display/wsdl" xmlns:tmd="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:trc="http://www.onvif.org/ver10/recording/wsdl" xmlns:trp="http://www.onvif.org/ver10/replay/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:trv="http://www.onvif.org/ver10/receiver/wsdl" xmlns:tse="http://www.onvif.org/ver10/search/wsdl" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:wsdd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:wsrfbf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:wsrfr="http://docs.oasis-open.org/wsrf/r-2" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xmime="http://tempuri.org/xmime.xsd" xmlns:xmime5="http://www.w3.org/2005/05/xmlmime" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Header>
      <wsa5:Action SOAP-ENV:mustUnderstand="1">http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/SubscribeResponse</wsa5:Action>
   </SOAP-ENV:Header>
   <SOAP-ENV:Body>
      <wsnt:SubscribeResponse>
         <wsnt:SubscriptionReference>
            <wsa5:Address>http://192.168.1.161:8000/onvif/Notification?Idx=676163</wsa5:Address>
         </wsnt:SubscriptionReference>
         <wsnt:CurrentTime>2023-05-03T10:08:11Z</wsnt:CurrentTime>
      </wsnt:SubscribeResponse>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Indeed the TerminationTime is missing from this response, so the integration does not know for how long the subscription will last.

Please report back to Reolink that the (beta) firmware you received is missing the TerminationTime in the ONVIF subscription response, and ask them to add it back.

[Valiante]

Did as you suggested and they came back with another (beta) firmware (v3.0.0.2115_23050409) today, which I have just installed. I have successfully re-added the camera and I'm no longer getting the webhook URL unreachable error after restarting HA.

Would you like me to gather any logs or do any specific testing again this latest version? On the surface it appears to be working correctly.

New subscription response, including TerminationTime:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsdd="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:xmime="http://tempuri.org/xmime.xsd" xmlns:xmime5="http://www.w3.org/2005/05/xmlmime" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:wsrfbf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsrfr="http://docs.oasis-open.org/wsrf/r-2" xmlns:ns1="http://www.onvif.org/ver10/actionengine/wsdl" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:ns10="http://www.onvif.org/ver10/events/wsdl/PullPointBinding" xmlns:ns11="http://www.onvif.org/ver10/events/wsdl/CreatePullPointBinding" xmlns:ns12="http://www.onvif.org/ver10/events/wsdl/PausableSubscriptionManagerBinding" xmlns:ns13="http://www.onvif.org/ver10/network/wsdl/RemoteDiscoveryBinding" xmlns:ns14="http://www.onvif.org/ver10/network/wsdl/DiscoveryLookupBinding" xmlns:tdn="http://www.onvif.org/ver10/network/wsdl" xmlns:ns3="http://www.onvif.org/ver20/analytics/wsdl/RuleEngineBinding" xmlns:ns4="http://www.onvif.org/ver20/analytics/wsdl/AnalyticsEngineBinding" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:ns5="http://www.onvif.org/ver10/events/wsdl/PullPointSubscriptionBinding" xmlns:ns6="http://www.onvif.org/ver10/events/wsdl/EventBinding" xmlns:ns7="http://www.onvif.org/ver10/events/wsdl/SubscriptionManagerBinding" xmlns:ns8="http://www.onvif.org/ver10/events/wsdl/NotificationProducerBinding" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:ns9="http://www.onvif.org/ver10/events/wsdl/NotificationConsumerBinding" xmlns:tad="http://www.onvif.org/ver10/analyticsdevice/wsdl" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tls="http://www.onvif.org/ver10/display/wsdl" xmlns:tmd="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:trc="http://www.onvif.org/ver10/recording/wsdl" xmlns:trp="http://www.onvif.org/ver10/replay/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:trv="http://www.onvif.org/ver10/receiver/wsdl" xmlns:tse="http://www.onvif.org/ver10/search/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
	<SOAP-ENV:Header>
		<wsa5:Action SOAP-ENV:mustUnderstand="1">http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/SubscribeResponse</wsa5:Action>
	</SOAP-ENV:Header>
	<SOAP-ENV:Body>
		<wsnt:SubscribeResponse>
			<wsnt:SubscriptionReference>
				<wsa5:Address>http://192.168.1.161:8000/onvif/Notification?Idx=2329981</wsa5:Address>
			</wsnt:SubscriptionReference>
			<wsnt:CurrentTime>2023-05-04T12:05:28Z</wsnt:CurrentTime>
			<wsnt:TerminationTime>2023-05-04T12:20:28Z</wsnt:TerminationTime>
		</wsnt:SubscribeResponse>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

[starkillerOG]

@Valiante great to hear Reolink came back with a working (beta) firmware so fast.
If everything appears to work and if you restart the integration a few times and never see the repair issue again, I believe they have indeed implemented the initial ONVIF push upon subscription, a debug log would show if this is indeed the case, but I don't think it is nessesary.

Please report back to Reolink that the (beta) firmware (v3.0.0.2115_23050409) is working and fixed the issue, please also ask them to include this fix in a new firmware release for all users.

[TekFan]

Hi @starkillerOG , do you have an eta for the repair message suppression for older firmwares ?
In all my cameras, I have a couple of them (3 or 4 years old) getting very rare motion, so the repair message can stay there for a few days and although not impairing functionality, this is still a bit annoying.

[starkillerOG]

@TekFan, unfortuanetely I do not have a ETA, I am still waiting on a review for the PR: #91015
There are meany PRs open on HomeAssistant, so I will just have to wait untill someone finds some time to review this one.

[rleongcs]

@starkillerOG I just updated to HA 2023.6.0 and I am still getting the webhook error for my E1 Zoom. Is it because the firmware is not old enough that PR: #91015 is not able to fix? Snapshot from Reolink website of the firmware my E1 Zoom is currently on.

[starkillerOG]

@rleongcs yes the firmware version is too recent, but apperently might still not push its initial state on the ONVIF ws base notification then.
Does the issue automatically disapear if you make motion in front of the camera?

[rleongcs]

Does the issue automatically disapear if you make motion in front of the camera?

Yes, it does as previously mentioned in this thread. Was just hoping that the fix would help as it does takes some time before there is a movement on that camera. 😃

[starkillerOG]

@rleongcs I will work on improving this in the future with ONVIF long polling, but that requires quite some effort and time, so it can take quite long before I get that implemented.

[dellspector]

I would like to chime in briefly and say that I was having no luck linking my ReoLink NVR/cameras to HA using ONVIF and was getting that same error message (only intermittent polling, no person/pet detection etc), but after manually updating the firmware on all my cameras and the NVR itself everything seems to be working well and not getting the error even at the start. My cameras are RLC_820A's and the NVR is RLN16_410. Found some posts from two years ago that ReoLink's auto-updating doesn't work, I guess it still doesn't!

[starkillerOG]

@dellspector you are right, build in firmware upgrade from reolink does not work.
The next HA release 2023.7 will have new code that ensures the firmare is checked against the reolink servers directly (not using the camera API) in that way the update entity of the reolink integration will finally reliably show if there is a new firmware version update :)

[starkillerOG]

@rleongcs good news, I have the ONVIF long polling working now and the PR to get it into HomeAssistant is under review:
#94770

[starkillerOG]

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.

[starkillerOG]

The long polling PR #94770 is merged and will be included in HomeAssistant 2023.7 which will be released July 5th 2023.

It will add a aditional long polling fallback for receiving events (motion/people/visitor etc) and should get rid of the warnings.

If you still experiance problems when on the latest camera firmware and on HA 2023.7, please let me know.

[rleongcs]

@starkillerOG I just updated to 2023.7 and still see the error. Just wanted to confirm if I will see the error but it will go away or I should not see it at all?

[TekFan]

I confirm, error is still there until the first event.

[starkillerOG]

@rleongcs @TekFan that is not what I was expecting.
Could one of you turn on debug logging for Reolink, restart HomeAssistant wait 2 minutes, stop debug logging and post the .txt debug log here?
Of course when using HA 2023.7.

I want to see how the old E1 Zoom is responding to the long polling requests.

[rleongcs]

@starkillerOG Attached please find the log file. The camera in question is Foyer E1 Zoom.

home-assistant_reolink_2023-07-07T12-22-06.130Z.log

[starkillerOG]

@rleongcs thank you for the debug log, that helps!
I am working on it, this PR #97383 will ensure the issue will clear itself after 60 seconds.

I will make a (more complex) PR to prevent the repair issues from beeing created at all (delay the creation of the repair issues with 90 seconds such that the ONVIF long poll is already received).

[rleongcs]

@starkillerOG Great to hear that the debug log helps. Thank you very much on working to help better this integration. I have also sponsored some coffee for you 😉

[starkillerOG]

@rleongcs thank you, much appreciated:)

[starkillerOG]

@rleongcs @TekFan both PRs #97383 and #97476 have been merged and have been added to the 2023.8.0 milestone.
So this issue should finally be fully solved once HA 2023.8.0 is released in 2 days time.

Please let me know if it works on HA 2023.8.0!

[rleongcs]

@starkillerOG I am not seeing the previous error after upgrading to HA 2023.8.0. 🎉

Thank you!

[starkillerOG]

Greath, glad it is finally resolved

[TekFan]

I can confirm for my RLC-511's as well.
Thank you @starkillerOG !