On the Voice & Audio section of the Google My Activity page, you can see your history. The recordings it keeps are only after triggering it to wake up with the wake word (OK Google). It also has the ability to delete your history.
Yes, there is an official list:
Simply say "Ok Google" or "Hey Google" before any of the voice queries below.
Those are currently the only two wake words. There's some speculation that other wake words will be coming at some point, but until then, the only two wake words are "Ok Google" and "Hey Google".
As Helmar has pointed out, any alternative ...
For an end user, using IFTTT or another connector service as described in mico's answer is probably the best way.
If you want to develop an action on the Google Assistant platform, you can use Actions on Google, a toolkit with everything you need to develop a new action that other users can interact with. Note that, unlike Alexa, Google Assistant actions ...
Well, I can answer only two of the queries:
First two get answer "No, they aren't supported."
The guy in this reddit article played with one Google home device and found that out.
There is a hidden usb port in machine, but both ADB nor fastboot don't work.
Wireless abd tries to connect some IP but IP remained offline despite efforts of pushing device ...
To make this kind of experiment most easy is to use API.ai (a tool acquired by Google just before Google Home was born ).
In API.ai you can very easily imitate the flow with data that is given with one command and read with another, but with actual Google Drive it is also possible to build the exact flow you have.
Your described flow is done like this:
Cloud-based services are unlikely to offer much 'local-lan' functionality without some competitive pressure. Specifically, a lan implementation requires a local hub. That could be the service's native hub, or it could (in your case) be a 3rd party hub. Generally, LAN functionality seems to be supported only where there is a WAN fallback (to hide the local ...
Google Assistant's Actions can return a subset of SSML, part of which allows you to instruct the device to play an audio file such as an MP3. An example is given of the SSML to use in the Actions on Google documentation; I've adapted it below for reference:
Here is an MP3 file.
If the phone is new enough to run a version of Android with full Google Assistant then it should work for most things.
The main points that differ will be:
The microphone on the phone won't be nearly as good as the microphone array in the dedicated Google Home device. So voice recognition across the room will likely be not as good.
You won't be able to set ...
To create voice commands for google home follow the below given steps:
Go to IFTTT.com.
Sign in or up
Click Search. Search for "Google Assistant."
Click Google Assistant Google Assistant and then Connect.
Choose a Google Account and grant IFTTT access to it. Make sure to choose the account you used to set up Google Home or the Google Assistant on your ...
Although it's not ideal, you could use two IFTTT recipes to allow you to call your phone: one to set the ringtone volume to maximum, and one to actually call the phone. It's a little more involved than I'd like, but since IFTTT offers no chaining of actions, it's the best you'll get.
Recipe 1: If Amazon Alexa > Say a specific phrase Then Android Device > ...
Basically what you can do for training by yourself is to retrain the device for your voice. You'll say consecutive times the wake words as they are prompted by the app.
I found a post stating you should tell the wake words all around your home to get different conditions better taken in care. My claim is that the same would apply if you imitate little bit ...
Unfortunately, any Action that is intended to imitate Google Home system functionality is explicitly banned, and the API doesn't really facilitate doing that (not surprising, I suppose, that the API doesn't let you do something that Google doesn't want you to do!):
We don't allow actions that mimic or interfere with device or Assistant functionality. ...
Despite what Belkin says on their website, Wemo and Google Home aren't fully compatible.
Some Wemo smart home products are natively compatible with Google Assistant / Home. These include:
Belkin Wemo Mini Smart Plug,
Belkin Wemo Insight Smart Plug,
Belkin Wemo Light Switch.
It does not include Belkin Wemo Bulbs or anything not on that list. It doesn't ...
I don't think there is a point to having them on the same network (in the same physical building).
The implication of the feature is more for it you have multiple locations (e.g. home and office or holiday home) so you can have them work with the same account but organise the devices logically.
There is negligible difference in the assistant functionality between a Google branded Google Home device vis-à-vis an OEM speaker with google Assistant. Lets, take Google Home and LG WK7 Speakers, various demo show that Google Assistant feature works the same.
Apart from Google Assistant there are notable differences, such as
Google Home runs CastOS ...
The API for this sort of thing is here
Google Assistant lets you write Smart Home Actions which let you add your devices to Model and then pass messages to your backend to then control the devices.
Unless you want to end up writing a LOT of code, do a load of testing and then get it approved by Google, you don't want to try and do this from scratch. Using ...
You could use the competitor Stringify which supports subsequent actions as well as conditions in their rule engine. This rule for example does three actions:
WHEN I say "OK Google, tell Stringify Good Night"...
THEN turn on my Hue Bulb A19 to orange at 15% brightness,
AND set the cool temperature on my Nest Thermostat to 69F...
THEN fade off ...
Yes, the Google Assistant supports Actions which allow developers to respond to requests from users. Actions can only respond if prompted, they cannot speak unannounced at this time.
Using the Actions SDK, you must first define some actions:
This is now possible with the continued conversations feature is deployed, announced at Google I/O 2018.
If continued conversations are enabled on your Google Home, the microphone will continue to listen for 8 seconds after the reply (or until you say "thank you", if you wish to prematurely stop it listening). A demonstration of the new flow is avaiable ...
The Google Home does support alarms.
“Set an alarm for 5 PM called Mary's homework”
Your device will then ring an alarm sound at 5 PM, as expected. However, it will not announce what alarm is ringing, according to the documentation:
Alarm sounds will only be played from the internal Google Home speaker and not other Cast devices (e.g. TVs, other ...
I have been able to say "Eggrole" to trigger the Google Home, and that works fine, despite it not sounding anything like "Ok Google" or "Hey Google". It seems that the wake word detector misrecognises "Eggrole" as being one of the wake words.
That diagram is describing Google Assistant's Local Control SDK.
Currently, there is no support for NFC on the Google Home. I couldn't find an authoritative source to say that there isn't support, but there are no known features as of writing that use NFC capabilities. I'm also not aware of any plans in the near future to use the chip.
Note that the chip is used by several other devices (most notably the Xbox One) which ...
It seems, from this forum post that you can use ha-bridge which masquerades as a Philips Hue bridge, permitting it to consume the basic lighting commands. If you have Hue devices, you need a real Hue bridge behind ha-bridge.
Since this supports Google Home, you're able to implement voice command, but potentially some limitations to the scope of the commands....
Google Assistant recently added the ability to execute multiple commands in a shortcut, which solves this problem for me. I was able change my "tea time" shortcut to look like:
"Set a 4 minute timer called tea and turn on the 4 minute timer light."
They didn't use to be, but it appears that they now are - at least on Android phones, as of April 2018.
See this article on android central. They mention that:
When Google Assistant debuted with the Google Home, the features were quite different between the shiny new home speaker and the phones that it became available on. Google Assistant on phones felt ...
Well, it can be done by switching to Alexa ;-)
I'm in a similar fix: I have a weather station that can report current conditions with a JSON message in response to an HTTP request. I was able to write an Alexa skill that could fetch the message and compose a spoken response.
I picked up a Home Mini during the Christmas sale because I've read it does ...
There are a slew of wake up words for Google, try Cocaine Poodle
I've been doing my best to trick any assistant I can to see if I can get some unexpected result. I've found Google Home to be especially vulnerable to a cadence.
1. OK Gokoku - There's a few weird variants to this that also work. It's the real outlier in terms of any ...
The commands e.g. on/off, set brightness are all handled in the language the device is set to. They are then converted to a set of enum values that are passed to the backend for control as part of a JSON object. The Google Home Smart Device API is here for a list of available commands and what gets passed: https://developers.google.com/actions/smarthome/