PersonDetection or FaceFamilarDetection syntax for particular person

[KonaBlueShelby]

I would like to know what the correct syntax is for a script to use the PersonDetection starter for a particular face.  I saw two different ones in the screenshots of this blog post: https://www.googlenestcommunity.com/t5/Blog/Camera-events-custom-notifications-and-more-now-availabl...

Those examples are using a device.event.FaceFamilarDetection which isn't available but show a faces or faceName field.

However, neither one of those validate correctly when I try to use them with PersonDetection.  The documentation doesn't explain it either.

Thank you,

Mark

[marilynereiche]

For person detection or face familiar detection, you typically need to use a specific programming or machine learning framework or library such as OpenCV, TensorFlow, or a dedicated facial recognition API like Microsoft Azure's Face API. The syntax can vary significantly depending on the chosen tool, so it's essential to refer to the respective documentation for the correct syntax and implementation details. For more details visit here

[nickfromgoogle]

 Hey @KonaBlueShelby - Are you able to copy and paste the examples from the reference docs to see if they work for you? You'll need to edit the device names based on what you've named the devices in your home. You'll find the supported starters under https://developers.home.google.com/automations/starters-conditions-and-actions (filter by " Device event starters"). Note that PersonDetection is different than FaceFamiliarDetection in that PersonDetection is whether the camera sees a person vs. a familiar/unfamiliar face on cameras that support the familiar faces feature.

[KonaBlueShelby]

@nickfromgoogle thank you for the response. I tried manually putting in FaceFamiliarDetection and I get the validation error below.  This is for a Nest Doorbell (battery) and it has faces detected and saved.  I have the public preview active for my Google Home account.

[device.event.FaceFamiliarDetection] is not supported by device [Porch doorbell - Entryway]. The list of supported events: [device.state.Online, device.event.DoorbellPress, device.state.EnergyStorage, device.state.MotionDetection, device.event.MotionDetection, device.event.PersonDetection, device.event.MovingVehicleDetection, device.event.AnimalCatDetection, device.event.AnimalDogDetection, device.event.AnimalOtherDetection, device.event.PackageDelivered].

[nickfromgoogle]

Thanks for checking and sharing the details. I'll follow up with my team to see why this is happening.

[KonaBlueShelby]

@nickfromgoogle - find anything out on this?  Thanks.

[nickfromgoogle]

Hey @KonaBlueShelby - Sorry, the team is still looking into this issue. I'll reply once I have more info. Thanks for your patience.

[KonaBlueShelby]

@nickfromgoogle I have FaceFamilarDetection available now.  But it doesn't look like the faceName or faces are valid options like shown in these screenshots https://www.googlenestcommunity.com/t5/Blog/Camera-events-custom-notifications-and-more-now-availabl...

I was hoping to automate unlocking my Nest Yale lock if the Nest Doorbell recognizes me, but it doesn't look like unlocking is supported for the lock.

[NickP-Dublin]

I just posted a similar question in as a reply in the another post. I used the example shown in the blog post about camera events and everything seems good apart from when I validate its says "Field [faceName] is unexpected in the struct".

Has the format for identifying individual faces in the script changed since the blog post?

[nickfromgoogle]

Hey @NickP-Dublin  we've issued a fix so that the FaceFamiliarDetection starter shows up in auto-complete and works without the faceNames parameter. We're working on removing the parameter in auto-complete until we get it fully implemented. Apologies for the inconvenience. In the meantime, you can use FaceFamiliarDetection as a starter so any familiar face detected starts the automation.

[Moziqui]

I'm having the same issue, whether I use 'faces' or 'faceName', I get the same error: Field [faceName] is unexpected in the Struct.

[nickfromgoogle]

Hey @Moziqui,  we've issued a fix so that the FaceFamiliarDetection starter shows up in auto-complete and works without the faceNames parameter. We're working on removing the parameter in auto-complete until we get it fully implemented. Apologies for the inconvenience. In the meantime, you can use FaceFamiliarDetection as a starter so any familiar face detected starts the automation.

[lalbdl]

so in this below if the "faceName" doesn't work  how would i format below to trigger on annoyingone?
metadata:
name: greet the annoying one
description: annoy one fear my politeness

automations:
- starters:
- type: device.event.FaceFamiliarDetection
device: Garage camera - Garage
faceName: annoyingone
actions:
- type: assistant.command.Broadcast
devices:
- Garage camera - Garage
message: "Thanks for the warning!"

[Super_paulie]

you cant. Even a year and a half later after announcing the feature it still doesnt work. Probably due to how awful the detection is these days.

[Super_paulie]

add me to the list, face or faceName are not recognised as valid.

[nickfromgoogle]

Hey @Super_paulie, we've issued a fix so that the FaceFamiliarDetection starter shows up in auto-complete and works without the faceNames parameter. We're working on removing the parameter in auto-complete until we get it fully implemented. Apologies for the inconvenience. In the meantime, you can use FaceFamiliarDetection as a starter so any familiar face detected starts the automation.

[Super_paulie]

That's kinda ok, however I need to be able to use specific familiar faces as my starter. Just having general familiar faces isn't specific enough sadly.

[KonaBlueShelby]

@nickfromgoogle - it looks like I'm not the only one looking for the correct format to add 'faces' or 'faceName' or whatever it should be to get this working. Can you help with this please?

[nickfromgoogle]

Hey @KonaBlueShelby, sorry for the delay. We've issued a fix so that the FaceFamiliarDetection starter shows up in auto-complete and works without the faceNames parameter. We're working on removing the parameter in auto-complete until we get it fully implemented. Apologies for the inconvenience. In the meantime, you can use FaceFamiliarDetection as a starter so any familiar face detected starts the automation.

[Matt_HGR]

Hi @nickfromgoogle  sorry to be another pest on this thread!

I'm also looking to get the faceName(s) parameter implemented to my automation. i've been lurking on this thread for around 3 weeks myself!

Do you happen to have an ETA (or a loose window) for when you'd like to get this re-added?

Thanks so much!

Matt

[nickfromgoogle]

Hey @Matt_HGR - Sorry for the delayed response. I'm still following up with the team on this request so nothing to share at this time.

[gamingdexter]

Any update on the script for stating the name of the person?

[Super_paulie]

i also would like to know of any updates, i mean its been half a year at least.
Surely Google can see how important it is to distinguish between familiar faces and named people as a trigger. The guy from Amazon who is familiar is fine but i dont want him to trigger all my lights in the house.

[Super_paulie]

still waiting for this... i saw that there was an update to automations so i came back to check and the "faceNames" is still not available/working. A shame as why would i want to just use a generic "Familiar face" as a starter.

I mean i want specific people to use as starters for example "If Paul is at the door and its dark, then turn on lounge lights". What use would it be if its just a generic familiar face, for example why would i want the lights to come on when im not at home and say my grandmother is at the door. She would just assume i was in as the light came on...? not ideal Google, come on.

[Super_paulie]

Here again, any update?

For example tonight, a "familiar face", ie my mother, gets recognised on camera and all my lights come on so she thinks I'm at home. I'm not at home, I'm at work, but my mother is stood there waiting as she thinks I'm at home and turned the lights on.

With the familiar face parameter this can be avoided. We don't just want "familiar face", we need "familiar face with an associated name/criteria. It's surely an obvious and basic association.

[Super_paulie]

even the "Help me script" function automatically generates the syntax for it, but then you cant validate it.  @nickfromgoogle any update on this? its quite an important feature, i dont want my house lights turning on when "The Postman" is recognized at the door, but i do need them to come on when i personally am recognized. I cant logically get around it at the moment and it seems like a feature that is almost available, but not... 

[nickfromgoogle]

Hey @Super_paulie - Sorry for the delayed response but I don't have any updates to share yet. I'll continue to check in with my team and will follow up once I have more to share. Thanks for your patience.

[Super_paulie]

I appreciate the response Nick, please let us know. It's quite an important trigger as there is no real alternative for personal routines.

[Super_paulie]

thought PersonDetection would work, but the same boat.

[zane1788]

I would also like to know if this will become available again, as I used it on a day-to-day basis

[DiegoPatrocinio]

Well, please add me to the list of people who would like to have this working again, as this feature is the biggest reason for me to pay for Nest Aware.

[kaiclubbe]

also want to see this feature.

[Super_paulie]

@nickfromgoogle still nothing? All my "Familiar face" routines are getting triggered by the postman rather than myself.

"If Paul is at the door then turn on porch light". What im stuck with is "If a familiar face is at the door then turn porch light on". You can see how this would be troublesome for people registered as familiar such as the postman or even friends, i dont need lights to come on when the postman is on the path outside. Home or Away is no good either as there is more than me who lives at the house.

[Herwerd]

Come on team, please get this feature working! We need to be able to specify specific people, not just whether they are known people. 

[BryanBowie]

Tossing down on this topic as well because the familiarName field that gets generated doesn't work either. Kind of a bummer as we pay for these sweet advanced features and we can't take advantage of them further.

[NigelSmithworth]

+1 on needing this. If I can't write a script that changes all my outdoor flood lights to red and plays a "threat detected, initiating combat mode" message over a speaker when my nest doorbell sees particular friends, what is the point of even having a script editor

[Matt_HGR]

@nickfromgoogle anything yet? It's such a powerful yet simple addition!

[ArdillaTactica]

@nickfromgoogle+1 I really want this feature, please help!.

[KonaBlueShelby]

Can someone from the @GoogleNestTeam please provide a response to this?  Not sure if @nickfromgoogle is still around.

[nickfromgoogle]

Hey everyone, I'm still around! Sorry I don't have much to share in terms of feature updates but I am continuing to share your feedback with our team. We understand how this can unlock more automation capabilities for your use cases.