search

fwestenberg / reolink_dev

Home Assistant Reolink addon
MIT License
550 stars 102 forks source link

Person detection entity turning off too quickly #357

Closed Bruskey closed 2 years ago

Bruskey commented 2 years ago

RLC-810a camera recently upgraded to firmware version v3.0.0.494 and since then, the person detection entity state changes to "detected" when a person is detected as expected, but it quickly changes to "clear" within a few seconds, even though a person is still clearly in the view and moving around. With previous firmware version v3.0.0.136 the entity will stay on until the person leaves. Nothing else changed since upgrading firmware version.

HA 2021.10.4

I have 2x 810a cameras, one on the older firmware which behaves as i would expect, and downgrading firmware back to the older version fixes this

cpainchaud commented 2 years ago

Hi,

It's the new way that Reolink has implemented their firmware, they clear the flag after 5 seconds and they don't give a f$ck about our opinion.

Bruskey commented 2 years ago

Hmm ok. How has nobody else complained about this though? Ive searched through everything and havent found anyone mentioning this.

cpainchaud commented 2 years ago

The fact is that if you want to build automation or get alerts, it shouldn't be a problem if the "ON" time is short so most people won't notice it.

I asked Reolink to go back to previous norms and/or include timestamps in events but they dont seem to care much

Bruskey commented 2 years ago

Ok. So how does that logic actually work then. If it goes off after 5 seconds, how is the next motion event captured? My expectation would be then that after it going off for 5 seconds it would come back on straight away as there would be a new event? In my testing it appeared very random as to when it came back on.

cpainchaud commented 2 years ago

that is their 'magic'. our integration will update whenever it receives a webhook call from them. They have failed to provide the new algorithm they are using. It is truly annoying ! :)

On Tue, Nov 9, 2021 at 10:57 AM Bruskey @.***> wrote:

Ok. So how does that logic actually work then. If it goes off after 5 seconds, how is the next motion event captured? My expectation would be then that after it going off for 5 seconds it would come back on straight away as there would be a new event? In my testing it appeared very random as to when it came back on.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/fwestenberg/reolink_dev/issues/357#issuecomment-963990182, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTC5PVUQE3AD4DKH5UKCLLULDWADANCNFSM5HT44MBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.