Recently, my application has stopped working on Actions on Google, with a message of "Sorry I can't help". When viewing inside the simulator, i see a properly formatted response, with output messages that application sends, however, the response is "Sorry i can't help". This doesn't happen on the same intent, it happens after having a conversation for a few minutes. If i restart the intent, and ask the same question/intent, then the response is good, until a few minutes pass by, and then "Sorry I can't help" comes up again.
So it turns out you can only have "Default Fallback Intent" respond 3 times in a row, before the application closes.
Related
I have an action that no longer works when issuing an utterance with "ask [invocation name] [utterance]"
it just returns with a "The agent returned an empty TTS".
However, if i set up nGrok, and try to debug it, the request never gets sent to nGrok and thus never hits my endpoint (backend code base).
Looking for next steps to debug this issue.
Note, "Talk to [invocation name]" works perfectly fine.
Also, if i use the "try it now" feature for utterance testing within dialogflow, with the same utterance, it triggers my endpoint.
The intent that is to be triggered is set as "Implicit Invocation"
While testing in the Simulator, Request tab is empty, Response is empty, Debug shows "the agent returned an empty TTS.", and Errors is empty as well. StackDriver logs does not even show this request being made.
While searching for other ideas, it appears this is possibly the same issue
Try to change your invocation name.
I had the same problem and that minor change fixed it!
Maybe is because you have some reserved word in your invocation
I have a very basic/general question:
Is there any way for me to interrupt Google Home while it's talking? I currently have developed an app that asks the user a question. However, I am running into usability issues because the user begins to respond to the question before the mic activates, because they already have predicted the question and as a result the app doesn't pick up their response and waits. The user, however, gets confused because they don't know that the app is waiting for the response.
Users can interrupt Google's reply at any time by starting with "Hey Google" or "OK Google" or the equivalent hotword phrase in their locale. If your action is running, what they say after that will be sent to you.
I´m using DialogFlow to create a chatbot. I want to keep the mic open along a conversation so the user doesn´t have to press the mic button every time.
Is this possible?
Thanks!
If you are referring to Dialogflow test console ("Try it now" prompt) - it doesn't seems you can.
But I will assume that you are referring to Google Assistant integration.
First of all you will have to end each answer with additional question, eg "Can I help you with anything else?" - this will be verified when you will deploy your bot to production in Actions on Google console. For each intent that you want to keep the microphone listening, you will have to make sure that it has "Set this intent as end of conversation" option disabled.
I had submitted my app for review, but Google replied with "mic" issue. Google Replied :
During our testing, we found that your app would sometimes leave the mic open for the user without any prompt. Make sure that your app always says something before leaving the mic open for the user, so that the user knows what they can say. This is particularly important when your app is first triggered.
Some Points:
1. app.ask()---leaves the mic opens.
2. app.tell()---app leaves the conversation.
I have also enabled the "toggle" of "Set this intent as end of conversation".
Any suggestions??
My app is one to one i.e. If user ask "my address" then address is shown, If "show me direction to PLACE_NAME" then directions are shown. BUT after it mic opens. How to close it?
-----UPDATED-------
fuction someName(app)
{
//---code-----
app.ask('Alright, your address is '+ user_address);
}
I don't want to use app.tell() as it closes the app.
Some other suggestion for this one to one Q/A conversation.
If you are doing fulfillment through a webhook, then the "end conversation" toggle is ignored in favor of what you are sending from your webhook.
You don't show any code, but as noted:
If you use app.ask() or one of the variants of it, the message will be sent to the user and the microphone will be left open. In this case, you should make sure it is clear what you're expecting from the user - in other words, ask a question or prompt them.
If you use app.tell(), the message will be sent to the user and the microphone will be closed. This will end this conversation.
It sounds like, in your case, you should be using app.tell().
I've gotten a subscription product working fine with Google's Wallet for Digital Goods, but I can't make user's cancelling their orders work correctly.
If I cancel for them via the merchant center, it works just fine (I get the postback with the orderId as expected). If the user tries to cancel (and this is the same in the sandbox and in production), they see the "Are you sure you want to cancel" dialog, and when they say "yes" it immediately fails. There is simply no delay there.
From everything I've looked at I'm not getting a postback at all in this case (and I'm handling the postback fine when we cancel from the merchant center). I've looked through the logs on our web server, as well as instrumented the postback handler, and it seems to be failing before it ever gets to my code.
I got the same problem. Seems like there is something wrong at Google. These errors appear in the console.
GET https://224.32.32.221/90187 gr_full.js:26
GET https://224.32.32.221/90188 gr_full.js:26
POST https://wallet.google.com/manage/r903944a86542ecd9d4195e49cd5a8668/rpc/subscription 500 (Internal Server Error) com.google.checkout.buyercenter.client.buyercenter-0.js:4267