We've been having trouble keeping Wonder available on Google Assistant and Home. We keep resubmitting and then find out there's some bug that gets us taken down.
One thing that has made it hard is that we cannot test Wonder in the simulator in the Actions Console. Here is what a session looks like: Wonder test session
When I expand the last message I see the following error: Cannot use standard Google Assistant features in the Simulator
Is there any way you could help us get this fixed?
The Google Assistant available in the simulator has a subset of the features of the assistant available in your phone or Google Home device. If you want to use the entire set of voice interactions, please use the assistant on your physical devices. If you want to test your smart home action, you can use Test Suite.
Also note that Google Home projects do not support dialogflow anymore. I see you have the dialogflow-es-fulfillment tag in your project. If your project is set up as a dialogflow project, you might need to set up a new Smart Home project on the actions on google console.
Related
I have a Raspberry Pi running Home Assistant (Hassio actually) and it is communicating with Google to make the lights go on and off using Google Assistant. To do that I have followed the cook book on the home assistant website. When Hassio updated from an API password to Oauth, I created a new project, because I had some issues with discovering devices.
In the current situation, when I ask Google to turn on the lights, it turns on the light, but also states that [lastprojectname] is not reachable. I did remove the project from the Google Actions console, but it does still show up in the Google Home app. I unlinked the account there, but still the same issue. So the old project is still in the linkable account list.
When I ask Google to turn on the lights in the 'office' (for example), it states, 'OK turning off 4 lights' while there are only 2. The lights are not in the app anymore, the account is not linked. Very weird. Any ideas?
This happens to me some of the time (I'm also using Home Assistant, but just starting with Google Assistant integration). When it happens, I just link, and then re-unlink the app. It usually sticks the second time.
I know that's the equivalent of "turn it off, then turn it back on", but it works, and I don't have a better solution :|
I am able to run the simulator on my test project within the console actions webpage. However when I test it on the google assistant app on my phone, the test project opens and replies “this application isn’t available in your country”. I am located in Canada.
Would appreciate any assistance on why this restriction is coming up.
I changed my phone language from English (Canada) to English (US) and it works. I’m not sure why English isn’t universal but at any rate that solved the problem!
I am currently working on a IoT device to control lights. This device is implemented using FreeRTOS.
I am little confused how to provide Google Home integration with this device, could someone shed some light on this.
You can use the Smart Home API. The Google Assistant works with a webhook, sending commands to SYNC, QUERY, and EXECUTE on that URL. You will then need to send these commands to your device.
Setup happens through the Google Assistant app, where users must link with your OAuth server.
Here is a sample project for Smart Home, using virtual devices.
I am new to google home. I had an experience in Amazon Alexa custom skill development. In Alexa, I had deployed my codebase in lambda function and also test my custom skill using actual Alexa device register with my email id.
So, Now I need to develop similar skill in google home device. Till now, I didn't get any good tutorials.
Is it possible to create & test Google Home app like Alexa skill?
The steps you go through to develop a Google Home action or app are very similar to creating an Alexa skill. There are a couple of differences, but logically they are the same.
If you use a NLP system such as Dialogflow (which is strongly suggested), you build the suggested phrases that the system responds to and the Intents they correspond to. You would specify your webhook as part of building these phrases. If you don't wish to use an NLP, you can specify the initial Intent phrases using the Actions SDK and specifying the configuration as part of a .json file. Other actions you'd do in the Alexa console are similar to what you'd do in the Assistant console.
You can deploy your Action on any public server that accepts HTTPS connections. This can include AWS Lambda with an AWS API Gateway trigger, or a Firebase Function, or a web server you more directly control that has a valid SSL certificate. This webhook would get a JSON body and needs to send back a valid JSON response. Google has libraries for node.js to help with this.
Google has a relatively full-featured simulator which you can use to test your Action. Once it is available in the simulator, it is also immediately available on every device attached to that account. You can permit other accounts to the project as well and, once they have activated it through the simulator, it is available on all their devices as well.
A full set of documentation is available at https://developers.google.com/actions/. It includes links to sample code, and you can find more step-by-step codelabs at https://codelabs.developers.google.com/?cat=Assistant
If you're familiar with how to develop skills for Alexa you might want to check out the jovo-framework. It makes it pretty easy to create skills that work for both Amazon Alexa and Google Home.
Here is a good starter template and walk-through that will get you going. https://github.com/rmtuckerphx/ask-cli-jovo-starter
I accidentially moved to the new Actions on Google dashboard. Since then my project does not really work anymore.
I changed the json structure and uploaded a new version that is now running fine on the simulator.
Unfortunately, my Google Home device is not recognizing that such an action exists. This was working before when using the old actions on google api.
Ciao
Fabio
The invocation name has changed when testing apps on the Google Home device.
You should now say
Talk to my test app