reolink_dev
reolink_dev copied to clipboard
fwestenberg
Person detection sensor is not working
Describe the bug Motion detection works with the integration - in my case: binary_sensor.reolink520a_motion. But person detection not - binary_sensor.reolink520a_person_detected.
Anyway, the person detection works, is available with the integration, but the dedicated sensor for it doesn't work. I set up my own binary sensor accessing the attributes of the motion sensor.
To Reproduce I can compare the states in motion and person detection sensors: The motion sensor has attributes: people_state: true/false vehicle_state: true/false
In case of motion by person: {{ state_attr("binary_sensor.reolink520a_motion", "people_state") }} --> TRUE {{ states("binary_sensor.reolink520a_person_detected") }} --> FALSE
Expected behavior binary_sensor.reolink520a_person_detected has the same state as attribute in motion sensor.
Environment: Please provide useful information about your environment, like:
- Home Assistant 2021.11.5
- Reolink camera model: 520a
- Camera firmware number v3.0.0.177_21012100
Additional context In Reolink app the person detection works.
Hello, was looking for an answer for the same issue. The general motion sensor in HA triggers, people or vehicle do not. I have three Reolink Outdoors all with the same issue.
Version | core-2021.11.5 Installation Type | Home Assistant Container Development | false Supervisor | false Docker | true User | root Virtual Environment | false Python Version | 3.9.7 Operating System Family | Linux Operating System Version | 5.10.63-v7l+ CPU Architecture | armv7l Reolink IP camera | v0.42
edit: Maybe should have a separate issue about this, but wanted to just mention that it seems that also se setting are not correctly reflected in HA. E.g. all cameras have IR light active (auto), one is showing it off, likewise FTP was active on all camera, one showed it disabled.
Please up your firmware to v3.0.0.494
And make sure you apply the following advices: https://github.com/fwestenberg/reolink_dev/blob/master/TSHOOT.md
This document will also tell you how to enable better logging
Thank you, I have it, that's stupid... It is not that I would not read that page, BUT I thought I'm using the latest FW. The Reolink apps are not providing this latest version (v3.0.0.494) automatically - I had to dowload it manually from their download center. Maybe a local issue, here in Czechia ...
Thank you very much, after FW update it works as it should!
Can it be about the camera firmware if motion sensor triggers but person/vehicle detection do not? I have the latest available firmware downloaded from Reolink site in my E1 Outdoors so not sure what to update...
Having same issue, motion sensor is available, but vehicle and person are not available as seen in screenshot..
Tried deleting camera from ha but same entities appear after adding camera again.. What am I doing wrong?
Hi, firstly it is not the same issue as originaly posted. Have you tried to check in developer tools - states for an entity like: binary_sensor.cam1_person_detected ?
The screenshot may not show everything what is available by the integration.
No there are no more entities available for cam1, and person/vehicle are not listed as attributes as well.. - so not able to access them
Solved my issue - turns out I did not have the latest integration - updated and now its solved. Sorry to hijack the original issue - though it was the same issue I experienced.
Reolink RLC-520A platform IPC_523128M5MP, firmware v3.0.0.494_21073000 (last official), I have 6 items.
The "person" and "motion" detection sensors in the fwestenberg/reolink_dev does not match the detection in the camera.
@tomasjuchelka 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.