Google Home
Devices known to AutomationManager can be made available through Google Home, allowing voice and other Google Assistant actions. See AutomationOnDrive for adding AM devices to Google Home. (Note, the integration service in the Google Cloud so a small subscription fee is charged to fund the service).
In AutomationOnDrive you select the devices you would like to make available in Google Home. Some devices types can be changed to allow different behaviors.
Note: needs AutomationManager 16.13.3 or later and AutomationOnDrive 5.0.4 or later.
Troubleshooting
If you attempt to link your AutomationOnDrive account and it fails you may need to wait 60 minutes before the account is cleared and you'll be able to link again.
If your AoD server is down for a longer time google may mark the AM service as inactive. Open google home, select the "+" button, "Set up device", "Works with Google". Find the Automation Manager service, select "Reconnect account" and follow the prompts.
For other issues use the contact page to email me.
Google Home Types
Switch - responds to voice on and off commands and queries.
Outlet - responds to voice on and off commands and queries.
Bulb - responds to voice on and off commands and queries.
Dimmer - responds to on, off, and set/change brightness commands and queries.
Color, Temperature, Color+Temperature bulbs - responds to on/off, brightness, set color and set temperature commands and queries.
Lock - for door locks, responds to Lock/Unlock commands and queries.
Door - responds to open/close commands and queries.
Event - responds to a start or activate command (triggers the event in AM)
Garage Doors
A garage door control is often triggered by an event to open/close a garage door. Caution is advised as a garage door should only be closed when it is in sight to avoid accidents. It's also advisable to avoid triggering the door to open if it is already open (e.g. by repeating the open command) as this could cause it to close accidentally. If you have a sensor for the garage door state a better approach is to use AM automation events to control it.
Create a flag GarageDoor in AM (under search/custom devices). Use the AM device menu to mark it as persistent (so it won't be reset if AM or the rule engine is restarted). Select the type "Door" when mapping it to Google Home.
Create a "Follow Sensor" rule with the GarageSensor as the sensor and GarageDoor as the target.
Create a rule triggered with WhenDevice GarageDoor turns ON
Condition:
GarageSensor as FALSE/OFF.
Actions:
trigger the GarageEvent (the event that opens/closes the garage door)
refresh the GarageSensorCreate a rule triggered with WhenDevice GarageDoor turns OFF
Condition:
GarageSensor as TRUE/ON.
Actions:
trigger the GarageEvent (the event that opens/closes the garage door)
refresh the GarageSensor
Now when you say "Open the garage door" the event will only be triggered if the door is closed. Similarly a close command will only trigger the door event if the door is open. The door flag will follow the state of the sensor so you can ask Google whether it's open or closed.
Routines
Google routines provide a mechanism for you to trigger AM actions and scenes using any phrase you desire. I am reluctant to rely on the internet & cloud for important sequence of actions, so sequences or multiple actions may be better implemented by creating rules fired by events using OnEvents triggers that then runs the actions within AM. Then use AoD to expose the event to Google Home as a Scene or Device. In the google home routine I can start that scene (event) by voice with "Start" or as a device (switch) with "Set" or use it a Google Home routine and trigger with any phrase. If for some reason my home is offline I can still trigger it from my phone via AM with a single touch.