Binary sensor is available in HA, but motion detection is not working

Hi @fwestenberg, Thanks for this integration - I’ve been using it for a few months and it has been rock solid. I run a RLN8-410-E NVR with 5 cameras (RLC-410 & RLC-522). I’ve been running v0.07 since new (I think) with the following config and it has been running pretty much perfectly; Cameras;

 - platform: reolink_dev
    host: 192.168.0.46
    username: !secret dvr_username
    password: !secret dvr_password
    name: Front Door
    stream: sub
    protocol: rtmp
    channel: 0
    scan_interval: 5

Motion Sensors;

- platform: template
    sensors:
      motion_front_door:
        friendly_name: Motion Front Door
        device_class: motion
        entity_id: camera.front_door
        value_template: "{{ is_state('camera.front_door', 'motion') }}"
        delay_off: 
            seconds: 0

In the last month or so I enabled object detection (people only using Tensor Flow), and the this is triggered by motion. It has been working great and only alerts me when it sees people in the cameras.

However, since upgrading to v0.10, and removing the old config, whilst the cameras are all displaying fine, motion has stopped working reliably, and there are a few other issues worth mentioning. Here are the symptoms;

1. Two of the five motion sensors are unavailable at any one time (and this changes on HA restart - sometimes the front door is unavailable, and then it becomes available and another becomes unavailable)
2. Motion on the available motion sensors is unreliable (at best). Sometimes it works, other times not. I have verified that it is working fine from the Reolink app (and the console screen).
3. Sensitivity status within HA does not match sensitivity status within the Reolink app. (eg, one cam is set to medium(33) in the Reolink app, but displays as 18 within HA entity attribute. (See below)

access_token: xxxxxxxxxxxxxxxxx
daynight_state: AUTO
sensitivity: 
- id: 0
  sensitivity: 18
  begin: '00:00'
  end: '06:00'
- id: 1
  sensitivity: 18
  begin: '06:00'
  end: '12:00'
- id: 2
  sensitivity: 18
  begin: '12:00'
  end: '18:00'
- id: 3
  sensitivity: 18
  begin: '18:00'
  end: '23:59'

friendly_name: Front Door
entity_picture: /api/camera_proxy/camera.front_door?token=xxxxxxxxxxxxxxxxxx
supported_features: 2

I am running HASSIO, in http mode, and with a reverse proxy enabling HTTPS (using Caddy add-on). I use a bought certificate and the same hostname inside and outside of my home network (using local and internet DNS to change the IP resolution depending whether you’re at home or away).

What information do you need from me to help sort this out? Thx James

[fwestenberg]

Until v0.8 HA was polling every second on the cgi API for motion. Because it was polling, https or http didn’t matter. Now it has switched to real-time push motion detection, the camera should be able to reach the HA webhook. And for some unknown reason, this only works over http for now. So IMO this is a great improvement, with some things to fix:

• NVR
• HTTPS

[macxq]

HI all! Let’s engage on reolink community forum and express that we need suport for https and prober AI detection propagation https://community.reolink.com/topic/3291/third-party-integration-support-ai-detection-home-assistant