topic Re: Let's discuss: creating powerful automations with our new script editor! in Home Automation

Let's discuss: creating powerful automations with our new script editor!

kelanfromgoogle — Thu, 15 Jun 2023 18:07:05 GMT

Hey everyone!

This week, we released the script editor, a tool for creating advanced home automations, on Google Home for web and the Google Home app. Learn more about it in our community blog: New to Public Preview: create powerful automations with our script editor.

You can unlock the full potential of home automation by building advanced, personalized automations. Here are some examples that can be done only in the script editor:

We'd love to hear about how you are using the script editor. Share your favorite use cases for the script editor, and your automation scripts in the comments below!

Here are some helpful guidelines for sharing your automations in the Community discussion forum:

Use clear and concise titles in your post. For example, Automation Script: Water the lawn in the mornings.

Include why you created the automation. Describing what this solved for you may inspire others to try it out. For example, "My schedule can vary a lot during the week so it's helpful to add a few conditions to create the automation flexibility I need."

Share the script in text format. Copy and paste your automation script so that other users can learn from what you’ve created.

Do not include personal information. To ensure your safety, security, and privacy, make sure your custom automation doesn’t include any personal information you don’t want to share.
Use the category “Sharing an Automation.” Using the correct category helps other community members find your post.

Re: Let's discuss: creating powerful automations with our new script editor!

Prafulla — Thu, 15 Jun 2023 17:56:38 GMT

Thanks @kelanfromgoogle

Looking forward to seeing what everyone is creating. We are here to help if there are any questions.

Re: Let's discuss: creating powerful automations with our new script editor!

William1701 — Thu, 15 Jun 2023 18:20:38 GMT

I am working on creating a routine that turns my porch light on/off based on two motion sensors. ("or" condition for both sensors to turn the light on and an "and" condition for both sensors to turn the light off) The single light source affects two motion zones, so the ability to write a routine should help. I will find out if it works when it gets dark.

I am struggling with the save feature if I apply a "for" condition to both sensors with the "motionDetectionEventInProgress" state identified as "false." I can apply the "for" condition to one of the sensors and the routine will save, but not both. My preference is for both sensors to have to not sense motion for several minutes before the light turns off. Any thoughts?

automations:
starters:
- type: device.state.MotionDetection # This function belongs to devices that can detect motion.
state: motionDetectionEventInProgress
is: false
for: 3min
device: Front Door MotionSensor - Front Porch
- type: device.state.MotionDetection # This function belongs to devices that can detect motion.
state: motionDetectionEventInProgress
is: false
for: 3min
device: Front Porch MotionSensor - Front Porch

Re: Let's discuss: creating powerful automations with our new script editor!

adriangalbincea — Thu, 15 Jun 2023 20:39:40 GMT

I created a script that will play sound on a device in the house when I am away and the Sensor is open.

The issues I have are. It is very delayed and sometimes does not trigger and set volume on device does not seem to work. Media shuffle resume is temperamental too.

What I am trying to achieve is to start music on a few devices when the alarm is triggered.

Below is the script.

# ------------------------------------------------------------------------------------------ #
# Any line that starters with "#" sign is a comment and gets ignored.
# Indentation (i.e. Number of spaces before each line) is used to decide information hierarchy.
# To populate the template, please follow instructions listed via comments in this template.
# To learn more, please visit g.co/home/scripts for full documentation.
# ------------------------------------------------------------------------------------------ #

metadata:
name: Alarm Front Door # Update automation name e.g. "Movie time"
description: Scripted automation # Update automation description

automations:
# Update "starters", "actions" and optionally "condition" sections to create an automation
# Duplicate these three sections under "automations" to add more automations in the same script

# ---- STARTERS ---- #
# Starters describe events that should start the automation
# Duplicate "- type" section under "starters" to add more than one starters
# If you add multiple starters, any one of them happening will start the automation
# Automations will run if any of the starters meets the criteria

starters:
# Use Ctrl + Space to get autocomplete suggestions
- type: device.state.OnOff
state: on
# [available operators: is, isNot]
is: true
device: Smart Meter - Generic devices
# ---- CONDITIONS ---- #
# Conditions are optional checks that can limit an automation to run only in certain cases
# If your automations does not require conditions, please completely delete the CONDITIONS section
# To use advance conditions that use logical operators ("and", "or", "not") please visit our documentation

condition:
# Use Ctrl + Space to get autocomplete suggestions
type: home.state.HomePresence
state: homePresenceMode
# [available operators: is, isNot]
is: AWAY

# ---- ACTIONS ---- #
# Actions are performed when a automation starts and all conditions are met
# Actions run sequentially and respect any delay introduced between them
# Duplicate "- type" section under "actions" to add more than one action

actions:
# Use Ctrl + Space to get autocomplete suggestions
- type: device.command.SetVolume # Set the volume of a given device.
devices: Livingroom speaker - Livingroom
volumeLevel: 50
- type: assistant.command.Broadcast
message: The front door has been opened
devices: Livingroom speaker - Livingroom

Re: Let's discuss: creating powerful automations with our new script editor!

Toner — Thu, 15 Jun 2023 20:42:18 GMT

Hi!

The scripting is great. But I tought there would be more starters than only our devices.

- I'd suggest to have a Weather based starter (Sun, Rain, ...)

- Nest Camera Events Starters (Person detected, Zones, ...)

I'm eager to see those!!

Thanks

Re: Let's discuss: creating powerful automations with our new script editor!

lardo5150 — Thu, 15 Jun 2023 22:12:19 GMT

Looks like you can't set the volume on Nest Audio, or the JBL Portable Smart Google Speaker.

Nothing happens. No errors, but the volume never changes.

I have several switchbot devices, and I need to "toggle" some of those. there is no toggle action.

Re: Let's discuss: creating powerful automations with our new script editor!

RyanTai — Fri, 16 Jun 2023 00:53:46 GMT

Great suggestions.

Beyond device starters there are Assistant voice starter:

starters:
- type: assistant.event.OkGoogle
  eventData: query
  is: Movie time # No need to add "Ok Google" to the query here.

Home Presence starter:

starters:
- type: home.state.HomePresence
  state: homePresenceMode
  is: HOME

condition:
  type: home.state.HomePresence
  state: homePresenceMode
  is: AWAY

Time schedule starter

https://developers.home.google.com/automations/schema/reference/standard/time_schedule_event

Re: Let's discuss: creating powerful automations with our new script editor!

Prafulla — Fri, 16 Jun 2023 01:02:46 GMT

Thanks for sharing @William1701 - That's a very interesting use case but is not yet supported. Currently:

all starters are separated by "or" and automation runs whenever any of the starters is true.
all conditions get checked only when a starter has started the automation. Hence, "for" works for starters but not for conditions.

The closest workaround for your case could be to use sensor1 as starter using "for" and sensor2 as condition (motionDetectionEventInProgress = False)? You would need to do that both ways.

Re: Let's discuss: creating powerful automations with our new script editor!

Prafulla — Fri, 16 Jun 2023 01:06:04 GMT

Thanks for the feedback @Toner - "Camera events" are coming very soon as we shared in our announcement (https://www.googlenestcommunity.com/t5/Blog/Create-powerful-automations-with-our-new-script-editor-now-available-in/ba-p/433461)

Weather event starters is another top use case that the team is actively exploring.

Re: Let's discuss: creating powerful automations with our new script editor!

Prafulla — Fri, 16 Jun 2023 01:10:56 GMT

@adriangalbincea - thanks for the feedback. Do you mind sharing which smart devices / speakers are you using? How often is it working? and what's the latency you are seeing?

Re: Let's discuss: creating powerful automations with our new script editor!

Prafulla — Fri, 16 Jun 2023 01:16:25 GMT

Thanks for the feedback @lardo5150 - We are investigating the volume issue.

Re: Switchbot - can you toggle them using Google Home app and not via the script editor?

Re: Let's discuss: creating powerful automations with our new script editor!

jkane001 — Fri, 16 Jun 2023 01:53:50 GMT

I was looking forward to trying something with my Aqara FP2, using OccupancySensingState as a start state. However, when I tried to do so, using something like the example on that page, i.e.:

- type: device.state.OccupancySensing
   device: Desk - Master Bedroom
   state: occupancy
   is: OCCUPIED

I found that the editor highlighted the type as not being a valid type, and the script would not save. In fact, if I ctrl-spacebar in "type," that OccupancySensing does not seem to exist. Is the documentation wrong, or is the editor?

Re: Let's discuss: creating powerful automations with our new script editor!

Eurik123 — Fri, 16 Jun 2023 06:57:53 GMT

Is it possible to make custom variables

Re: Let's discuss: creating powerful automations with our new script editor!

adriangalbincea — Fri, 16 Jun 2023 07:17:29 GMT

Hi @Prafulla, the speaker is Nest mini. The other device used as a trigger is a smart switch(Smart Life).

I did a test today and after 80 seconds was triggered. Very slow...

Re: Let's discuss: creating powerful automations with our new script editor!

Diazed — Fri, 16 Jun 2023 11:23:49 GMT

The section about variables is documented very briefly.
I would like to see a larger example using variables.

It would also be great to have the possiblity to create variables that are used inside multiple Script Automations.

Is it possible to start audio inside an action? For example my favorite podcast in the morning.
And if so, is it possible to start the podcast on multiple devices?

I only found the setInput action but i guess that means VideoInput for TVs right?

I am deeply in love with the new possibilities this offers. I am very thankful for all the work that has been poured inside this new feature.

Re: Let's discuss: creating powerful automations with our new script editor!

Diazed — Fri, 16 Jun 2023 11:28:03 GMT

It would also be great to have the possibility to ask for a confrimation.

Have the assistant ask a question i provided as string.
If i reply with yes the condition is met.

Just an idea.

Re: Let's discuss: creating powerful automations with our new script editor!

lardo5150 — Fri, 16 Jun 2023 12:21:10 GMT

yes. if I set it up to be a on/off button.

Here is an example of having a toggle option AND a repeat.

I am controlling the volume on a receiver that is not smart.

To change to bluetooth, I have to turn "on" and "off" that button to get it to the right input.

Then same thing for volume, I have to keep processing the on and off to get the volume to 30. A repeat would be good here.

Re: Let's discuss: creating powerful automations with our new script editor!

Titof174 — Fri, 16 Jun 2023 12:47:32 GMT

The weather to know if is necessary or not to open blinds (if too sunny, no open because too hot in the house)

Re: Let's discuss: creating powerful automations with our new script editor!

Vitor_Videira — Fri, 16 Jun 2023 15:16:58 GMT

Hi Kelan,

Are there any chances of triggering automations based on weather conditions?

Regards,

Vitor Videira.

Re: Let's discuss: creating powerful automations with our new script editor!

bothygesen — Fri, 16 Jun 2023 15:22:22 GMT

Actually, to control blinds/ curtains it would be more useful to use level of light (usually measured in LUX) from a sensor.

For instance all HUE motion sensor also measure LUX. These values are not available to see in the Google Home app nor the native HUE app itself. But the 3rd party app "Hue essentials" gives you access to level of light measured by the motion sensor.

At the moment i have a HUE motion sensor sitting in my window. Once it measures more than 30.000 LUX - which is direct sunlight - it will trigger a lamp to turn on, and when that lamp turns on my blinds/ shutters will close.

This is of course a workaround, and i would obviously be much more happy to be able to create this scenario and automation directly in the Google Home app.

One thing that i dont understand is, why not all sensor data is available in the Google Home app.
I have several Shelly products, and on my Google Nest hub i can access both temperature and humidity data. But in the Google Home app only humidity.
How hard can it be to display the data, when the sensor is providing it?

Same with the HUE motion sensor. They measure both movement, temperature and light level/ LUX. It should not be that hard to make the data available in the Google Home app.....