Nest Hello Person Detection

[elmigbot]

Motion and Sound are working fine except for person detection. The person detection never occurs, despite the app showing a person detected event. I can confirm it works just fine on a Nest Indoor Cam. A quick look at Nest docs say they have implemented the Nest Hello API the same as any other camera. I am using this in Home Assistant, but was instructed to submit the issue here.

[awarecan]

I don't have Hello, so I won't be able to test it. I am guessing the person detection event in Hello may have different format than Indoor Cam since Nest Hello's person detection feature including "Familiar Face Detection" with Nest Aware subscription, which is not in Nest Indoor Cam

[elmigbot]

Yeah, and the Nest API (just read) makes no mention of familiar faces, so may not be added yet. I wonder if turning off the familiar faces feature would put the person detection back into the supported format. I guess I'll give it a try. Thanks.

[towerhand]

@elmigbog, Did turning off familiar faces fix the person sensor?

[elmigbot]

Unfortunately, no it did not.

…

On Thu, Sep 20, 2018 at 8:46 AM towerhand ***@***.***> wrote: @elmigbog, Did turning off familiar faces fix the person sensor? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#154 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQIKWvjKTuI434WgWVbd2DGUWJGBnftsks5uc5w4gaJpZM4V-B70> .

-- Michael B. Hirschberg

[towerhand]

Hopefully it can be fixed someday.

[snicker]

could be related to this (and possible fix) #92 (comment)

[elmigbot]

Interesting. So it only happens to Hello and IQ, not the older ones? I'll give it a try tomorrow and reply back. Hopefully no ill-effects to my already working NestCam (nonIQ) and dropCam.

[snicker]

I can't say for sure as I only have the Hello, unfortunately. The monkey patch could be changed to check self.camera.model and only add delays for according camera types.

[elmigbot]

Applied the monkey patch, and it seems to be working well for the hello. The older nest cams seem to be working fine too, but I'd guess the end time is off by 30 seconds. Not a huge deal... Thanks for this! The correct fix would be on Nest side right? Is there a place to report issues with their API?

[medic459]

Does the sensor revert back after 30 seconds? Myself (and others) are seeing that it stays on...
#92

[snicker]

Another user said that behavior went away after a reboot. HomeAssistant might need a "hard" reboot (stopping and starting the service from the shell, or restarting the docker container on hass.io), not a reboot from the config page. I think the config page reboot may not unload all python code from memory to get a monkey patch working right. This is speculation on my part... but all of this feedback is good, it might mean a permanent implementation is not the way to go since it doesn't seem to work for everyone.

@elmigbot : I'm not sure if Nest would really want to modify this behavior.. their "end_time" for the event may get continuously modified as motion is continuously detected (not sure). The issue just happens to be the delay. Most motion sensors (PIR etc) have a built in or modifiable "reset time", so even if motion is detected for a fraction of a second, it will continue to report motion for X seconds. That is essentially what I'm doing here, but it may not be the preferred implementation for everyone.

[elmigbot]

Since the issue only exists with the newer cams, I've always figured they could fix the issue. I think you have found the problem: Too long of a delay. Fixing that would make the alert more meaningful as well.

Getting rid of the delay may prove difficult, as I assume it was introduced with some of the advanced features of the newer cams. Maybe instead, the check in CameraEvent.is_ongoing could be omitted or modified (I have never looked into this code).