Duplicated response from Google Console application - dialogflow-es

I have created a Google assistant application which is connected to Dialog Flow project.
And the I have deployed it as Alpha release and tried to test it with mobile phone.
The issue I'm facing is all the responses from the application is duplicated, but when I
test it from the Action Console simulator or from Dialog flow it works fine.
Tried deleting and recreating the google project but to no avail.

In your intent on dialogueflow can you check under Responses if the Google Assistant action is un-toggled?:
Use responses from the DEFAULT tab as the first responses
Alternatively you can try deleting your default responses and set only the Google Assistant action. Possibly the intent's Default and Google Assistant response are sending both responses to dialogflow causing duplicate response.

Related

Dialogflow query working in console but not when you use embedded url

I have made a query flow in dialogflow and it has four intent and in the last intent it uses a webhook to get data from server side and displays the result. It is trained automatically and works perfectly in dialogflow console returning response and query answer. The issue is it does not work when I use embedded url. It fails to recognize the name intent and asks (Can you repeat again or fallback intent). I've removed all intents and made query again, there is no similar name intents. Yet it works well in console and not in embedded url.
For the webhook part I've used node.js service.
Please help in this issue.
By 'embedded url' if you mean Dialogflow Web Demo (DWD), you should keep in mind that DWD can be used only for simple text messages. It does not support messages from webhook or even rich responses. However, if you steel need a web widget to embed your bot to your webpage you either create your own or you should use third party solutions (like Kommunicate). Here's the link regarding the limitations of DWD.

Error: Cannot display response in Dialogflow simulator. Please test on the Google Assistant simulator instead

I am using dialog flow to create an agent. When I try to embed it in my website, it gives me following error, "Cannot display response in Dialogflow simulator. Please test on the Google Assistant simulator instead.". It works perfectly fine in Google Assistant Simulator. I have seen people embed in their websites, but I don't know what I did different.
Any help would be appreciated.Code1 Code2 Code3 Code4
The expected output is a conversation between user and agent.Screenshot of my web page Screenshot of Dialog Flow Console
Okay, judging by the screenshots you added, you are trying to send a Google Assistant specific response to Dialogflow. In your welcome intent you are returning an Permissions object. This is something that only works for the Google Assistant. The web demo that you are trying to embed into your website doesn't support Google Assistant specific objects.
If you want to use the webdemo try sending only texts messages back to your user by using conv.ask("Your response") and conv.close("Your response") or give a response specific for Dialogflow. You can do this by either checking the request in code and sending a different text only response for Dialogflow users or you can create a Dialogflow only response in the Dialogflow console. Dialogflow responses are refered to as Default on the console.

Transaction API not working in mobile google assistance

Google Transaction API has been implemented in Dialogflow Fulfillment. In my intent function my code is like agent.add(agent.conv().ask(new TransactionRequirements())). This code was running properly and giving response in google action console only before deployment in alpha test. But that time in mobile google assistance there were no response as well as no log in google firebase function. After deployment in alpha test the response is coming in google action console i.e
DISPLAY REQUEST RESPONSE AUDIO DEBUG ERRORS Invocation Error You
cannot use standard Google Assistant features in the Simulator. If you
want to try them, use Google Assistant on your phone or other
compatible devices.
Now also in mobile google assistant still response not coming. What is the solution for that?
let tran = new TransactionRequirements();
agent.setContext(context);
agent.add(agent.conv()
.ask(tran)
)
#stackjohnny

Why Dialogflow doesn't work as expected for **alpha/beta** testers?

I am working on dialogflow and actions on Google for Google assistant integration. I have been working on it from last few months, I created dialogflow agent made required changes and setting in actions on Google as well. I used to test each and every day after implementing new features to my app (using Webhook) and found everything well before submitting to apha/beta approval. After completing my work with the app, I just submitted it for alpha/beta approval to Google and they approved it. At this point I just sent the opt in link(provided by actions on Google for alpha users for testing purpose) to the alpha testers. But unfortunately nothing is working as expected. After analyzing I found that all the parameters are always empty in the webhook request sent from dialogflow and intent didn't match as expected. But for me (developer or owner) it works fine, I mean to say alpha/beta versions are not working. The parameters should have the values of matched entity synonyms that have been added/loaded to dialogflow dynamically via dialogflow V2 APIs. It is working fine with owner account or developer account, But not with alpha/beta release.
While checking via postman if the entities gets loaded to dialogflow or not i found entities were loaded successfully to dialogflow with the same dialoflow V2 api, But due some reasons webhook request always sends empty strings for parameters.
Can any one have any idea why is this happening, And what is the solution for this issue?
Thanks in advance.
I have faced the same issue. And I found that my google actions are in deploying state and I have tried to test it with an opt-in link. But After a few hours, it is deployed properly and my custom google actions worked fine. And you also need to do alpha testing enabled in your mobile from an opt-in link.

No access token delivered to webhook after normal account linking

Conversation Flow : android device/web simulator - google assistant - api.ai - webhook - [websocket/FCM push] - android device
From end of last week, access token is not delivered to our webhook server even if account linking was successful and it is displayed on web simulator debugging window. When we logged on webhook server, the account token value from api.ai was NULL. After this happened, next account linking is not processed even if I reset (turn it off and on again) api.ai agent.
I tried to make new actions project and migrate api.ai agent to new one, but it was the same. I make sure the same test has been successful before last week.
If anyone has gone through the similar issue, I hope your help.
I was also very confused because I was expecting the accessToken to be in the same JSON format as shown in the simulator.
if still not working please send the body of the request you receive not what the simulator show you.
but it's under originalRequest.data.user.accessToken.
if you are using NodeJS you don't need to parse anything you will just need to call :
getUser().accessToken
from ApiAiApp object in the actions-on-google node library.

Resources