googlehome | Google Home Integration for Home-Assistant

The platform does not provide a mechanism to programmaticlly broadcast messages to different devices.

Try using send_keys(Keys.RETURN) instead of clicking the submit button.

Edit: Sending the RETURN key where you would normally click the submit button in your code should yield the same result.

The gactions file you downloaded is the executable itself - not an installer or anything along those lines. You can put it somewhere in your PATH or call it directly by giving the full path when you're calling it, but it will not be automatically available unless you do so.

You can see your PATH with echo $PATH. If you wish, you can place it in one of those directories.

If you wish to continue to run it out of your Download directory (which I do, since I rarely use the command), you can open an iterm2 command line and call gactions with the full path:

The code you have written is using the Dialogflow Detect Intent API. This is meant to run on consoles and servers to send a message to Dialogflow, which will parse it, determine which Intent it matches, call fulfillment with that information, and return all the results.

You don't need to run this on a Google Home, since the Google Assistant does all this for you.

What I think you're looking for is to develop fulfillment with Actions on Google and the Dialogflow Fulfillment API. This handles things on the other end - after Dialogflow determines what Intent matches what the user has said, and if that Intent has fulfillment enabled, it will send the information to your webhook which is running on a cloud server somewhere. You would then process it, send a reply (either using the actions-on-google library or the dialogflow-fulfillment library is easiest), and it would send it back to the Assistant.

You indicated that you want the Action to "let my GoogleHome device speak first, without the word "Ok, Google" and wait for a response from the user". This is much more complicated, and not really possible to do with the Google Home device right now. Most Actions have the user initiating the conversation with "Ok Google, talk to my test app" or whatever the name of the Action is.

You don't indicate how you expect to trigger the Home to begin talking, but you may wish to look into notifications to see if those fit your model, however notifications don't work with the Home right now, just the Assistant on mobile devices.

There is unfortunately no way to style the icon of an HTML webpage. You would have to do this in a form of image editor.

Good luck!

Sincerly Herman

You have to pass webdriver from test into pytest reporting system. In my case I use webdriver as fixtuer. That have a lot of other advantages - for example you can test for any set of browsers and control that from one place.

I think the problem is with the name. The Dialogflow Docs for Developer Entities states that they should "start with a letter and can contain the following: A-Z, a-z, 0-9, _ (underscore), - (dash)".

Have you tried removing the @ and just use dev-city as entity name?

In the devicetool, the --client-secrets argument is in relation to the tool itself, not the command.

The correct order of arguments would be:

googlesamples-assistant-devicetool --client-secrets register-model ...

Notifications on the Google Assistant platform are currently in Developer Preview. You can't release an Action that supports them, yet, and they currently on work on mobile devices - not speakers such as Google Home.

This will likely change as it moves out of Developer Preview and into production, but they haven't announced a time frame for this yet.

The solution you cite from Reddit uses the Google Home as a Chromecast Audio device, so requires a (separate) local agent to cast to it. The notes about Google Home refer to the consumer feature from Google that allows you to set notices and reminders - not for other applications.