a month ago
Hey everyone,
As of today, our script editor in Public Preview now supports camera event types as starters, custom notifications, suppression, and more. If you haven't already, check out our blog: camera events, custom notifications and more now available in the script editor in Public Preview
Which new features are you excited to try? With custom notifications now available, what’s something you would love to create? We'd love to hear how you are using the script editor, let’s discuss in the comments below.
Quick reminder of helpful guidelines when sharing your automations in the Community discussion forum:
a month ago
None of the new starters or actions are showing up in my script editor yet - is this a staged rollout?
a month ago
Same! Excited to try them out.
3 weeks ago
2 weeks ago
شكرا
a month ago - last edited a month ago
^^ likewise, when can we expect it to be rolled out to everyone in the public preview?
3 weeks ago
Hey @willz - these new features should now be available in the script editor. Let me know if you don't see them.
a month ago
I was excited to try the new time delay action (DelayAction) but it doesn't seem to work delaying activation of Google Assistant commands (OkGoogleCommand) or media control actions (like, device.command.MediaStop). It works fine delaying lights and scenes though.
In the below automation, I want to speak an Assistant command and have a Nest Speaker play music for 5 minutes, then activate a lighting scene and begin playing Google Sleep Sounds. The light action works fine, but I've tried numerous variations of this with different delayed Assistant Commands and they never trigger. So the initial song just continues playing while the lighting scene activates after the 5 minute delay. Can somebody help?
metadata:
name: Bedtime music
description: My son's music plays for 5 minutes, then lights turn off, and Google Sleep Sounds-Country Night Sounds plays.
automations:
starters:
- type: assistant.event.OkGoogle
eventData: query
is: Bedtime music
actions:
- type: assistant.command.OkGoogle
okGoogle: "Play Lost Woods | Zelda: Breath of the Wild" # A 60min song that plays fine here.
devices: Charlie’s Room speaker - Charlie’s Room
- type: time.delay
for: 5min
- type: device.command.ActivateScene
activate: true
devices: Charlie Sleep Lights
- type: assistant.command.OkGoogle
okGoogle: Play Country Night Sounds
devices: Charlie’s Room speaker - Charlie’s Room
a month ago
It's working for me now!
a month ago - last edited a month ago
Hello, I have access to the new features, however, I do not have the Familiar Face function as in the example you give. Also, the Home Notification command does not work, I do not receive any notification on my mobile ... It seems that an update of the Home application is necessary for it to work ... because I do not see in Parameters - Notifications - Automation Notifications - Enable Custom Notifications
a month ago
Familiar Face isn't showing up at all for me either (and neither is the Home Notification command, so at least yours is an option even if it doesn't work haha). I assume they're just slow on rolling this out to everybody, unfortunately.
a month ago
it's ok for Home Notification command since last night
4 weeks ago
Yeah, it won't auto-populate the home notification as an option for me, but if I type it all in it works, so that's something. Still no familiar face detection, though, even if I write it in manually (verbatim from the Google examples).
3 weeks ago
Hey @austinsmith - Are you still having issues with familiar face detection populating as part of autocomplete? Just checking if you have a device that supports familiar face detection and that familiar face detection has been configured for your home.
If it's autocomplete that's not working, do you get a validation error when typing in the info manually as you mentioned from the example docs?
3 weeks ago
It still isn't working. I get the following validation error when I type it in manually: "[device.event.FaceFamiliar Detection] is not supported by device [Front door - Front door]. The list of supported events: [device.state.Online, device.event.Doorbell Press, device.state.EnergyStorage, device.state.Motion Detection, device.event.Motion Detection, device.event.PersonDetection, device.event.Moving Vehicle Detection, device.event.AnimalCat Detection, device.event.AnimalDogDetection, device.event.AnimalOtherDetection, device.event.PackageDelivered]."
I definitely have a Nest Aware subscription (just checked, it renews in January) and familiar face detection works when someone rings the doorbell (it will say "John is at the front door" on my Google Home devices).
As I'm looking into this, the problem might be that my browser doesn't recognize that I have that subscription. On this support page for Familiar Face detection, it begins by saying "You’re currently not subscribed to Nest Aware and don’t have access to Nest Aware features. Learn more about what you get with a Nest Aware subscription." even though I'm signed in to the same account that has the subscription—it has my profile photo in the top right of the Chrome window (the one that lets you click on it to manage your google account).
So now I'm wondering if it's not a problem with the home automation page, but at the browser/account level?
tl;dr still not working
3 weeks ago
Thanks for the details @austinsmith. I'm not sure why you're getting that message on the support page but I'll follow up with my team about why familiar face detection is not working in the script editor.
3 weeks ago
Hello, I just made a request to my community (I am the administrator of a Facebook group for Google Home in France) and it doesn't work for anyone. The FamiliarFAce option does not appear and if you enter manually: device.event.FaceFamiliar Detection , the type is not recognized. I would like to point out that we have Nest Aware and that face detection is active. Personally, I have 2 Nest Doorbells, 2 Outdoor Cameras, and 1 Indoor. So all the conditions are met...The most likely hypothesis is that you have not fully activated the type in the Script Editor
3 weeks ago
Thanks for trying this out on your end @WadeWilson. Let me follow up with my team about familiar face detection not working for you. Thanks for your patience!
3 weeks ago
Hi Nick, I just wanted to mention that Familiar Face Detection is also not available for me - I have 5 Nest Camera (Battery) and a Nest Doorbell with Nest Aware subscription active.
3 weeks ago
2 weeks ago
The familiar face option isn't showing up on my script editor?
a month ago
Audio plays from the speaker where the voice starter was issued, not the speaker specified in the automation.
The starter is an OkGoogleEvent voice command and the action is an OkGoogleCommand to play audio from a specific speaker, but the audio only plays from the speaker where the initial OkGoogleEvent voice starter was issued.
For example, I say the voice starter, "Ok, Google. It's time to go to sleep" to my 'Couch speaker - Living Room' device, but the audio 'country night sounds' starts playing from that speaker instead of 'Charlie's Room speaker - Charlie's Room' as specified in the OkGoogleCommand action in the automation.
metadata:
name: Charlie Sleep 2
description: When Charlie goes to sleep, play Google Sleep Sound "Country Night Sounds" on his speaker.
automations:
starters:
- type: assistant.event.OkGoogle
eventData: query
is: It's time to go to sleep
actions:
- type: assistant.command.OkGoogle
okGoogle: Play Country Night Sounds
devices: Charlie’s Room speaker - Charlie’s Room
a month ago
How do you use the "Starter Suppressions"?
3 weeks ago - last edited 3 weeks ago
Hey @jkane001 - We've got more info on starter suppression in our help center article here - https://support.google.com/googlenest/answer/13460475?#zippy=starters. You can use the suppressFor key to suppress a starter for a specified period of time.
3 weeks ago
My Google Nest Doorbell battery doesn't show up as a starter under People Detection. Is the subscription also necessary for recognition. I thought only for familiar faces and longer video history. So I should actually be offered the starter.
Also, I had already asked in the old post (probably fits better here):
I currently have the problem that "members" does not work in the notifications. As soon as I type in members, the two household members are suggested with their names and email addresses. However, as soon as I want to shoot down the automation, I am told that this is not a member of the household. How can I solve the problem?
I also connected an Aqara M2 Hub with multiple contact sensors to Google Home via Matter. Unfortunately, the alarm or security system can only be controlled via Aqara. Does anyone have an idea how to sharpen the "fake" alarm. So due to this, Automation will receive a notification and the Nest audio will play a sound when a window has been opened. This is basically possible, but of course only if I have started an automation for it. I didn't want to rely on the presence and absence detection, but rather switch it on and off manually. i.e. an automation that creates a notification and the Nest audio emits a sound when a window is opened. This is basically possible, but of course only if I have started an automation for it. I didn't want to rely on the presence and absence detection, but rather switch it on and off manually.
3 weeks ago
I also intermittently get the error that a household member suggested by the Script Editor isn't a member of my household once I try to save or validate. The first automation I was able to get it to work after I submitted feedback about it in the editor but then it stopped working on the next script I tried to write. Very frustrating, especially since the FamiliarFace event isn't showing as available either. Something seems to be broken in the editor reading your household and subscriptions.
Monday
Hey @ThorsReign - We rolled out a fix for the notification action last week. Can you try again and let me know if you're still facing issues with that feature? Thanks!
Monday
I tried editing the previous routine and creating a new one, both of them suggest my wife in the "members:" but then gives the error that she isn't part of my household on validation or save.
2 weeks ago
I solved the problem with the video doorbell. It is now shown to me. The problem was the name.
However, the problem with messages for certain people still exists. In general, notifications to all household members work, but for some automations this is not necessary. It would therefore be great if the error did not exist that the person is not part of the household.
Another question:
How do I get a smart speaker to play a specific song or sound in the script editor.
2 weeks ago
Hi. How did you solve the problem? What name did you choose to make it work?
a week ago
I changed the device from "front door" to "doorbell". It was probably a problem because my contact sensor had the same name.
a week ago
Unfortunately still nothing new. Notifications to household members don't work even after three weeks. That's really a pity.
Monday
Hey @il_Capitano_25 - Are you still having issues with the notification action in your script? It should be fixed as of last Friday but let me know if you're still getting errors so I can follow up with my team. Thanks!
Monday
Unfortunately yes. The error continues to appear that I am not a household member, even though I am offered the members to choose from
2 weeks ago
Hello, is the familiar face event already working for everyone? I still don't see it on my end
2 weeks ago
I don't think so, nothing to see on my end too
2 weeks ago
Did anyone get the custom notification working?
Also with the familiar face I can't add 'faceName' to the starter? It give's an error...
a week ago
Still not seeing device.event.FaceFamiliarDetection in device starters. I have nest aware and the new cameras.
a week ago
I've got a automation set up that turns on the light in my hallway when my Nest camera detects motion using device.event.MotionDetection. This works fine, however, device.state.MotionDetection doesn't seem to be supported by any of the Nest cams which means I can't have that same light turn off when there's no motion unless I use a time.delay action.