I followed https://developers.google.com/actions/dialogflow/first-app tutorial and built my first google action. The action is working fine on my laptop browser in the test (Followed "Preview the App" section of the tutorial) environment. However, when I am trying to use this action on my phone by saying "OK Google talk to my first app". It's not working. Is it supposed to work on my phone as well? I have logged in with the same Gmail account on my phone also.
PS - I have posted the same question on "actions on google" google plus community google as well but I am not sure if that community is to post such questions or not. Therefore, I am posting it here also.
Thanks in advance!
Once you have enabled testing through the simulator, it should be available on all devices (mobile, speakers like Google Home, etc) with the same account your simulator is running in. Double check to make sure they're the same account.
In your case, however, you may be using the wrong invocation phrase. If you actually said what you did above, you need to say the exact same thing that you typed to invoke it.
If you haven't set a name in the configuration, then that phrase will be
Talk to my test app
Update
As you note in the comments - you also need to make sure you're running the Google Assistant, and not one of the other voice search components. The Google Assistant requires:
Android 6.0 or higher
Google app 6.13 or higher
Google Play services
1.5 GB of memory
720p screen resolution
Phone set to a supported language
As you probably already know you have to enable Web & App Activity, Device Information, Voice & Audio Activity in the Activity controls page.
Then you also have to be sure that the language of your agent is the same used by your google assistant.
I solved thanks this last step.
Hope this helps
Related
I am developing a Google Action for Google Assistant and it is not yet a state where I can release. Even so I want it to be available for some tester, and in a near future, my client.
The simulator with the "test" is somewhat limited at auth request, name recognition (since it will only knows my action) and experience (to show my client), so I prefer not to depend on it for this case.
I found it is only possible to interact with a test version of an action if the project owner's account is logged in as a Google account in the phone where you want to call the action. Is it correct? Or there is another way?
I even tried adding my wife's Google account as a viewer to the project, but I am unable to call my action from her phone.
You can add people as a viewer to the project. Before those users can call your action on any of their devices, they will need to use the test console at https://console.actions.google.com/ once, this will enable testing on their device. After that they will be able to interact with your action on their devices.
Do note, the time in which the action is available on their account is limited by a time period (about a couple of months). If they cant access the action any more after a couple of months, just repeat the above step to reactivate testing for their account.
Update
One thing that you could consider in the two approached posted by #Prisoner and me is if your testers need to test on just a device or need access to the console as well. Using the approach from #Prisoner will allow your users to test on devices. The above approach will also allow testers to use the console at https://console.actions.google.com/.
In addition to #Jordi's answer, you can also do an Alpha Release of your Action. This lets you permit up to 20 additional accounts to the released version
Once you permit them using the console, you will send them the opt-in URL, which they should visit on a mobile device with that account. Once they have opted into the Alpha, they can activate it using the regular trigger phrase.
I am trying to save user information on google assistant bot with the help of dialogflow using actionpermission intent in my webhook to store user previous details which he/she had filled for the first time. Saving like this works perfectly on my developer account and when i add alpha testers for testing my bot and saving their name and type on google assistant bot it works fine for some testers and parallel its not saving information for some other alpha testers. I don't know why its happening. If anyone can help regarding this issue it would be great. Thank you.
I believe the issue is not related to the alpha test but rather to the voice match.
On smart speakers, which are in a multi-user environment, it cannot be assumed by default that the user speaking is always the same. To get around this, smart speakers have a "voice match" feature which needs to be enabled in the device settings.
Until that is enabled, interaction data is not saved between sessions.
I am currently implementing a ChatBot using Google Cloud Speech.
I am using socket.io to record a microphone stream and then sending that through node to Google Cloud Speech.
Everything is working fine on my laptop and my android mobile phone (Nexus 5x, Chrome 68)
I record the audio, and having set single_utterance to true, get a result with "isFinal" as soon as I pause speaking.
But if I set the language code to 'da-DK', I never get a "isFinal" result (unless I end the stream myself) on mobile. Works fine on my laptop, but not mobile.
Have anyone experienced anything similar?
As a bonus info:
If I set interimResults to true, I do get multiple results, but they are just never isFinal.
So just to be clear: everything is working perfectly apart from the one case: da-DK on mobile.
As this behavior is occurring only when using the da-DK supported language on a mobile device, it might be related to an internal service issue; therefore, I think that you should take a look the Issue Tracker tool that you can use to raise a Speech-to-Text API in order to verify this scenario with the Google Technical Support Team. In this way, you will be able to share your code, audio files and internal project information if required by the troubleshooting process.
Additionally, I suggest you to take a look on this link that contains some useful documentation and example to use Google Cloud Speech API on an Android environment that you may use as a reference for your project.
I've tried now several times understanding if it is possible, and if yes how, to create custom actions that are available just for me on a Google Home device. I have a working Dialog Flow agent that works well in the Dialog Flow simulator. It used to work in the Google Assistant simulator and I could enable it for one hour, but now that doesn't work either.
I would be happy using IFTTT if it had webhook responses instead of just fixed responses...
Am I barking up the wrong tree?
There is not a good way to have private actions for a given user. The only way to do it is to enable testing for a given project. Then all devices using your account should be able to "talk to my test app" and communicate to your webhook. However, this test may end after a few days.
I was using google talk chat badge (chatback - small iframe code that enables remote user to chat with you as anonymous) for some years but now it is not working anymore. The generated code is fine as it seems it opens a new window and all but after a second, it redirects to support.google.com page which of course is not of much use.
I rechecked the code, generated new code, didn't help. Again redirects to support.google.com. The code is generated from http://www.google.com/talk/service/badge/New
Anyone knows what's going on? Have they discontinued it or?
Also, a suggestion - is there any alternative web-presence button like that for other messengers which don't require client on other end. For Skype, Windows Live or some other messenger?
According to KatherineG at Google the chat badge is no longer supported. http://productforums.google.com/forum/#!topic/chat/_VpluJc6IfU
We are looking into using Crafty Syntax for a replacement.
http://www.craftysyntax.com/
Yup, been a while now - it was great while it lasted. The personal workaround that I am using is to sign up for a live chat service and hook it up with Gtalk. I am currently using ClickDesk - http://www.clickdesk.com/
Visitors chat using the live chat interface and I use the Gtalk interface.
For a while I used MeeboMe in combination with MeeboMe notifier but then it died as well (company was purchased by Google and the product was killed) I found some good alternatives myself so I am sharing them. Ironically, they are recommended by MeeboMe after they discontinued their service. Both are free.
Zoho Live Support - https://chat.zoho.com/
Yahoo! Pingbox - http://messenger.yahoo.com/pingbox/ (requires Yahoo! account but otherwise is great)
Too bad large companies simply kill useful products. But as far as I am concerned, Yahoo! Pinbox is even better than both Google chat badge and MeeboMe (at least for my needs) and can be customized to great extent.
I recommend ClickDesk - http://www.clickdesk.com too if you like to use Google Talk or Skype.
However, if you want to code - you can use xmpp protocol and hook it up with Pidgin notifications. Google Appengine also has notifications which I believe is what ClickDesk uses.