cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Person event not recognized as a Familiar Face

rz1926
Community Member

I often receive a notification of an (anonymous) Person event, rather than as someone already in my Familiar Faces library.  How do I add a photo of the event to the existing set of images for a person already listed as a Familiar Face, so it gets correctly classified in the future?  Thanks ...

5 REPLIES 5

Brad
Community Specialist
Community Specialist

Hi there, 

I apologize for my late response and thank you for all of your patience while waiting for a reply. I understand how frustrating your situation must be, and I would love to help however I can. Please check out this article on how Familiar Face works.

Best Regards, 
Brad

rz1926
Community Member

The documentation you referred me to is not accurate or out of date.  When I navigate to Settings -->  Nest Aware --> Familiar Face Detection, there is no "New Faces" option to tap on (even though I've received many new Person events).  If I go to the Feed tab, I don't see any unfamiliar face events.  If I view the home history, I see video clips of events, but there is no way to reclassify them.

Finally, the documentation says:

When your camera spots a face it doesn’t recognize, or if it’s unsure, it assumes the person is unfamiliar to you and sends notifications that asks whether you know the person. 

I do get a notification,  but it doesn't ask me whether I know the person.   Clicking on the notification just shows me a video clip of the event.

 

So none of methods described in the documentation work for me.

Brad
Community Specialist
Community Specialist

Hey there again,

 

Unfortunately you cannot add a photo to it. This is an automated process.

 

Best regards,

Brad

rz1926
Community Member

 

Ugh - what a poorly designed product.  Will attempt to return it.

Brad
Community Specialist
Community Specialist

@rz1926

 

Alright I will be locking this thread as it looks like the issue is resolved.

 

Best regards,

Brad