06-15-2023 10:46 AM - edited 06-15-2023 11:07 AM
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:
09-10-2023 01:19 PM
Hello, is it possible to have zones person detection? Currently it's only letting me choose person detection without a condition if it's inside or outside the zones
09-11-2023 05:38 PM
Hi, I am trying to create a script to disarm security once the door lock has been unlocked.
I wrote it as:
actions:
- type: device.command.ArmDisarm
devices: Security - Entryway
arm: false
But I am getting an error message that I have to add cancel field. According to the documentation it's not mandatory. Any suggestions?
09-24-2023 10:46 PM
Firstly | Great advancement with Script Editor.
I have used this editor for the following:
1. Medication reminder | turns on & changes led strip lights to purple between 08:30 & 09:30
2. Reminder to take out the trash | turns on & changes led strip lights to blue between for 30 minutes on Thursdays @ 16:00hrs
Now I would like to modify this script to flash led strip lights between red & green & yellow & green on alternate weeks, lighting the led strip lights for 30 minutes on each occassion. A little stumped on the coding...!!
We have three trash bins Red, Yellow & Green, I always get mixed up as to which ones to put out for collection.
Any suggestions would be welcome .. Kelan
10-10-2023 08:21 PM
Any update on the ThermostatSetModeCommand command? It's in the documentation. But the script editor doesn't recognize it as valid. It would be really useful.
11-05-2023 05:52 AM
Hi, I've looked but can't see anyone trying this (sorry if this has been covered).
I'm looking to setup an automation, where is any one of my 3 Nest Thermostats call for heat, then they will trigger a relay, but then if they no longer require the heat it will turn the relay off.
I have cracked "on" part, but I cannot work out what option to use for the "off" on the thermostats?
ON
- type: device.state.TemperatureSetting
state: activeThermostatMode
is: heat
device: Kitchen - Kitchen
OFF
- type: device.state.TemperatureSetting
state: activeThermostatMode
is: ?
device: Kitchen - Kitchen
Once I crack this part I will then look at the conditions so that all 3 need to be "off" before the relay will turn off.
Thanks for any help
11-05-2023 06:20 AM
Just created a new automation to turn on/off Christmas lights. I now get this warning that I don't get on any other automation that turns light off and on. Is this new in the editor?
11-06-2023 08:00 AM - edited 11-06-2023 08:09 AM
The following script does not run. It gets a"safety" warning on the action. Looks like their examples.
metadata:
name: test # Choose a short name that summarizes important starters and actions, like “Sunset lights”.
description: Scripted automation # Write a detailed description that includes everything the automation does, like “At sunset, on weekdays, close blinds, turn on lights to 50%, and play the sunset playlist on certain speakers.”
automations:
- starters:
- type: device.state.OnOff
state: on
# [available operators: is, isNot]
is: true
device: Chair Light 2 - Office
actions:
- type: device.command.OnOff # Turn the device on or off.
# Whether to turn the device on or off.
on: true
devices: Credenza Light 1 - Office
After some more testing, if I turn the light on manually (with control) it does not recognize change of state.
Guess that makes sense
11-17-2023 09:40 AM
Hi!
The execution log for my scripted automations appears to halt abruptly after several executions. The log starts again if I deactivate and activate routines. Because of this, it’s not possible for me to know if the scripts are running or not. As you can see, there's a gap in log entries from the 11th to the 17th of November, resuming only after I deactivate and activate the routine.
automations:
starters:
- type: device.state.MotionDetection
state: motionDetectionEventInProgress
is: true
device: Living Room Sensor - Living Room
condition:
type: and
conditions:
- type: device.state.TemperatureControl
state: temperatureAmbient
lessThanOrEqualTo: 21C
device: Living Room Sensor - Living Room
- type: time.between
before: 01:00
after: 06:00
actions:
- type: device.command.OnOff
on: true
devices: Living Room Heater - Heating
Any idea why this is happening? Thanks!
02-20-2024 06:24 AM
What kind of sensors do you use? I am using Tapo T100 motion sensors and starters don't seem to work because nothing happens when movement is detected.
02-22-2024 04:22 AM
Hello, I'm using Phillips Hue motion sensors. The problem I previously mentioned resolved itself a few days after my post. Since then, I've occasionally noticed delays in automation execution.
02-20-2024 06:22 AM
Looks very promising! It's not working for me, For example Tapo T100 motion sensors don't seem to trigger any action in Google Home (they do in Tapo, I can see it in the native app). But if this improves and provides real support for Google enabled devices, it will be awesome! I will keep revisiting to see the improvements 🙂
07-17-2024 06:47 AM
Is there a script that turns off an existing automation? Not the able/disable button in the automation program, a separate automation that can activate or deactivate an existing automation or several automations.
08-27-2024 04:38 AM
Still waiting on google cameras update for live viewing. Will comment on every thread your in. Until it’s fixed.