I tried testing my Dialogflow Agent by Calling on the Dialgflow Provided Number, But It says "the number you are trying to call is currently busy".
I tried testing my Dialogflow Agent by Calling on the Dialgflow Provided Number, But It says "the number you are trying to call is currently busy". I created another agent and tried on it, and it was working but this one stopped working.
It's possible that the Dialogflow phone number you are trying to call is experiencing technical issues or is temporarily unavailable. You can try calling again at a later time to see if the issue has been resolved.
If you continue to experience problems with the Dialogflow phone number, you can try the following steps to troubleshoot the issue:
Check the Dialogflow agent's status. Make sure that the agent is published and active, and that there are no issues with the agent's fulfillment or integration.
Check the Dialogflow phone number's status. Make sure that the phone number is enabled and active, and that there are no issues with the phone number's configuration.
Check your network connection. Make sure that your device has a stable internet connection when you try to call the Dialogflow phone number.
Restart your device. Sometimes, simply restarting your device can resolve any temporary issues that may be causing the problem.
If none of these steps help, you may want to contact Dialogflow support for further assistance. They will be able to provide more detailed information about the issue and help you resolve it.
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 have installed the Google assistant service by following the guide in the official documentation. Now, I want to add custom actions in the SDK.
Just to test, I used the same action and code they have given. But, as it runs, it just says Sorry, your app is not supported on this device . I then wandered around in the troubleshooting page to find out that this was already addressed by Google. They have mentioned just about the issues caused due to triggering surface capabilities related to the screen ON. But in my case, all the surface capabilities are turned OFF. But, I'm still facing the same issue. Can anyone please help..?
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'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 understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.