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
Related
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.
Have recently started using Flutter and so can deploy apps to Google Play as well as to Apples App Store. When I want to put an app out for internal test though I am finding some difficulties. With The App Store I can make internal tests for up to 25 users immediately (it doesn't have to be reviewed). However Google Play's Internal test channel still requires a review (which has taken 6 days recently). Is there any offering in Google Play that I can use deploy quicker to my Android users?
Thanks for any advice
Your first upload must be approved. After that they are automatic.
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'm developing a game as a Chrome Packaged App and I want to use Google Play Games for the leaderboards, but it's turning into a little bit of a process.
I'm having trouble getting the Chrome Packaged App to authenticate with Google Play Games.
I've got most of it nailed down:
I've created a game in the Google Play Developer Console
I pretty quickly got everything working by uploading the game to my server and going to Linked Apps and creating a Web App entry. Leaderboards, achievements and everything works great.
I followed the All-The-Stars-JS example to get everything into the package so gapi.auth.authorize() can work within the packaged app... but using the call returns "OAuth2 request failed: Service responded with error: 'bad client id: NON_NATIVE'"
This makes sense-- the OAUTH2 Client ID from the Linked App manager is expecting a web app. There isn't a way to create a Linked App for the Chrome Packaged App so I created one using the Google API Console as the example suggested. This gets me authenticated!
Now, when I try to pull a list of leaderboards I get a response: "There is no linked app associated with this client ID."
Right, that makes sense because I created Client ID manually in the Google API Console and there's probably no "link" to Google Play Games... but I can't link it to the Google Play Games service manually, and there's no way to just link a Chrome Packaged App from the Google Play Developer Console. Am I missing something?? I've been chasing this issue for months!
Thanks in advance to anyone who can help!
#Brian I think you are doing everything correctly. Currently there is not a way (that I'm aware of) to link a Chrome packaged app to Play Game Services. The reason you are able to get authenticated but not see Leaderboards is that you created the Client ID through Google Developer Console, which does not create the necessary entries in the Games back-end.
I will report your experience to the Play Game Services team, maybe this is something we could support in the future.