Motion detection not working since upgrade

Describe the bug I’ve upgrade from the configuration.yaml-integration to the fully HACS integration. But since the upgrade the binary sensors are no longer changing states on detection. I get a push from the Reolink app when motion is detected, but binary sensors are not changing state.

No particular errors can be seen in the logs

Some settings such as stream type are also missing in OPTIONS

The setup worked flawless in prior reolink_dev version when used in configuration.yaml

To Reproduce Upgraded to reolink_dev 0.9 through HACS Removed reolink_dev and binary_sensors from configuration.yaml

Logs from startup:

2020-12-18 13:42:32 INFO (MainThread) [homeassistant.setup] Setting up reolink_dev 2020-12-18 13:42:32 INFO (MainThread) [homeassistant.setup] Setup of domain reolink_dev took 0.0 seconds 2020-12-18 13:42:32 DEBUG (MainThread) [custom_components.reolink_dev.base] {'port': 80, 'host': '192.x.x.x’, 'username': ’user’, 'password': ’pass’, 'channel': 1} 2020-12-18 13:42:32 DEBUG (MainThread) [custom_components.reolink_dev.base] {} 2020-12-18 13:42:32 DEBUG (MainThread) [custom_components.reolink_dev.base] {'port': 80, 'host': '192.y.y.y’, 'username': ’user’, 'password': ’pass’, 'channel': 1} 2020-12-18 13:42:32 DEBUG (MainThread) [custom_components.reolink_dev.base] {} 2020-12-18 13:42:40 INFO (MainThread) [custom_components.reolink_dev.base] Host 192.x.x.x subscribed successfully to webhook https://192.x.x.x:8123/api/webhook/9db17eec865ef2f867b548d7693a36b166774ef54a29fa18331517e7d0a293dc! 2020-12-18 13:42:41 INFO (MainThread) [custom_components.reolink_dev.base] Host 192.y.y.y subscribed successfully to webhook https://192.y.y.y:8123/api/webhook/9122b2a5aad7009a862fa25d027af0750391881cd27ec194c803b79694ba62e6! 2020-12-18 13:42:41 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.439 seconds 2020-12-18 13:42:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 3.319 seconds 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.camera] Setting up camera.reolink_dev 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.switch] Setting up switch.reolink_dev 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.reolink_dev 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.camera] Setting up camera.reolink_dev 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.switch] Setting up switch.reolink_dev 2020-12-18 13:42:44 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.reolink_dev 2020-12-18 13:43:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.306 seconds 2020-12-18 13:43:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.430 seconds 2020-12-18 13:44:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.269 seconds 2020-12-18 13:44:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.364 seconds 2020-12-18 13:45:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.250 seconds 2020-12-18 13:45:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.359 seconds 2020-12-18 13:46:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.237 seconds 2020-12-18 13:46:44 DEBUG (MainThread) [custom_components.reolink_dev] Finished fetching reolink data in 0.373 seconds

Expected behavior State change in binary sensors when motion is detected

Screenshots Device info:

Options (with missing stream type):

Binary sensor:

Motiondetection log with no events, but should be: I changed the state manually just to test (can be seen below)

Environment: Homeassistant 0.118.5 Reolink_dev 0.9 2 pcs RLC-410-5MP v3.0.0.136_20121100 (Also tried with a lower fw-version)

Additional context Any idea why sensors are not updating as they should?

[Lybbe77]

Update: Motion detection and binary sensors confirmed working as soon as SSL on HA was disabled.

I do think that many people are using SSL on their installations, so it might be an issue getting the reolink-integration working “out of the box” with SSL enabled.

When i have some spare time, i will setup nginx to make this work the way i want.

Thanks to all for help with troubleshooting 👍

[badabing2005]

Finally caught a motion related xml data

<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/NotificationConsumer/Notify</wsa5:Action></SOAP-ENV:Header><SOAP-ENV:Body><wsnt:Notify><wsnt:NotificationMessage><wsnt:Topic Dialect="http://www.onvif.org/ver10/tev/topicExpression/ConcreteSet">tns1:RuleEngine/CellMotionDetector/Motion</wsnt:Topic><wsnt:Message><tt:Message UtcTime="2020-12-21T22:32:27Z" PropertyOperation="Changed"><tt:Source><tt:SimpleItem Name="VideoSourceConfigurationToken" Value="VideoSourceToken"/><tt:SimpleItem Name="VideoAnalyticsConfigurationToken" Value="VideoAnalyticsToken"/><tt:SimpleItem Name="Rule" Value="MyMotionDetectorRule"/></tt:Source><tt:Data><tt:SimpleItem Name="IsMotion" Value="true"/></tt:Data></tt:Message></wsnt:Message></wsnt:NotificationMessage></wsnt:Notify></SOAP-ENV:Body></SOAP-ENV:Envelope>

Hope this helps