I followed the procedure to configure dialogflow and google assistant but every time I ask a question google home mini says that it cannot run it or that it does not find the device, as if there was not the connection between HA and GA. From the site dialogflow, trying the commands in the appropriate section of the site always responds with the default “Sorry but I can not connect to your Home Assistant”.
In the google home app I have already add all the devices of my home assistant.
Can you help me?
- did you add the webhook link to your HA in dialogflow?
- did you add the dialogflow component in the config file in HA ?
- check the Json file generated when you try in dialogflow. and see the if there is an error generated.
- yes, I did add webhook link: https://myhome.duckdns.org/api/dialogflow?api_password=HA_PASSWORD in dialogflow Fulfillment page.
- yes, in the configuration.yaml I added
dialogflow:
intent_script: !include assistant/intent_script.yaml - If I try to “turn on living room light” in the JSON file a part of the answer is:
“fulfillment”: {
“speech”: “Sorry but I cannot connect to your Home Assistant”,
“messages”: [
{
“type”: 0,
“speech”: “Sorry but I cannot connect to your Home Assistant”
}
]
},
“status”: {
“code”: 206,
“errorType”: “partial_content”,
“errorDetails”: “Webhook call failed. Error: Webhook response was empty.”,
“webhookTimedOut”: false
},
thanks
does the Action: name in the dialogflow matches the action name in the config file ? because it seems to be connecting but not accessing the action side.
but if you are trying to switch on-off devices and such i guess better for you to follow this guide, without going through dialogflow.
this guide will integrate all your switches directly with GA and no need to teach the GA how to control them. check it.
I have noticed that the webhook is changing from dialogflow to apiai by itself. is that happening with you ? please check the webhook url fully… at least happening with me.
From what I saw api.ai changed its name to a dialogflow.
Some time ago I had tried api.ai and it worked but since it changed its name I cannot make it work.
I configured GA as your suggested, it works I don’t have a list of commands so I do not know how to activate them while with dialogflow you can customize the questions and commands inside the configuration of HA
Hi,
I’m currently trying to set up Dialogflow to work with Home Assistant and later the Test version of my Google Home / Assistant app.
I followed the instructions on the component page for the set up, but it seems that it is not working.
When opening the API URL in the Browser i get a Error 405: Method not allowed
which should be OK in my opinion, as the API only allows POST requests(?)
This is my HA URL: https://raspberrypi.XXXX.myfritz.net:8123/api/dialogflow/?api_password=XXXXX
It is only accessible via IPV6 but it works for the Google Assistant component and is successfully linked to a Google Home.
The action for my intent is called SetMusicBose
and is supposed to change the input of media play to my Bose Sound system.
The JSON response from Dialogflow looks like this
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: Webhook response was empty.",
"webhookTimedOut": false `
While I created the Dialogflow project I linked the new project to my existing Assistant project. Currently it is NOT using Dialogflow V2 API.
my configuration.yaml
looks like this
dialogflow:
intent_script:
SetMusicBose:
speech:
text: Ok, changing input
action:
service: media_player.select_source
data:
entity_id: media_player.BOSE
I already added the KEY / VALUE pair to the HEADERS in Dialogflow but it did not help.
What did I do wrong? I cannot figure it out and a google search has not brought up anything new.
Thanks!
Are you using a self signed certificate?
yes, until it was called api.ai it worked but suddenly it stopped. I think it takes a patch to make it work .
Just setting this up myself. I have seen references to needing to use a public cert because of Google restrictions. Can you set the test environment up to use DuckDNS and a public cert? There was a comment from someone (which I can’t find again) about using the Basic Auth setting in the Fulfillment tab, so you may be able to change the security settings.
I have the intents in Home Assistant working from the Dialogflow web page. Just can’t invoke Dialogflow from a Google Home Mini.
no, I’m using Let’s encrypt.
Since I connected my Dialogflow project with my Google Assistant (Actions on Google) setup it suddenly stopped working. So… right now nothing is working anymore
I can’t even readd my test app (Actions on Assistant) under Assistant / Home Control as it won’t show up anymore.
did you add the dialogflow to google assistant console?
https://console.actions.google.com/
you should go there and create a project and add dialogflow to it and link them so when you speak to google assistant, you have to say " i want to talk to “project name” " and then you can send commands and such
Yes, I think I had to set the project up in the Google Console as part of the initial setup. But I don’t think I had completed this, so the two were not properly linked, so went back through the steps again. Also remembered from other HA integrations that you have to use the “Test Draft” option, which seems to publish it.
Made the name of the app Holly to Come Online, so you can say “Hey Google, ask Holly to come online”. (Go Red Dwarf. )That then drops you into the Dialogflow actions and you can use the Dialogflow Intents.
There is an option to add invocations to call the app, but only the two default invocations that the app setup as samples seem to work at the moment.
Looks like it will be fun to use the intents to call the HA scripts and automations, and it can be made a bit more natural and interactive.
Hey all-
I feel like I’ve followed all the directions perfectly. I had API.AI working a few months ago, but since then, I’ve redone my HA setup and can’t get it working now that it’s called Dialogflow.
I have dialogflow: added to my configuration.yaml file and have created several intents in Home Assistant. I’ve setup SSL with a certificate I’ve purchased for the domain. When I look at my Home Assistant log, I don’t see Dialogflow hitting the server when I try to test my phrases.
I have the Google Assistant component working properly, but I’d like to use Dialogflow so I can access more information from Home Assistant.
Any help would be greatly appreciated!
Thanks
If you still have this problem, changing to v1 did it according to this link:
could someone please help
i can get pass the error
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: 404 Not Found"
ensured i’m using V1
ive loaded in the example zip file and set up everything in home assistant and added the url
https://home.mydomain.com/api/dialogflow?api_password=mypassword
what am i missing
i have ifttt triggering scripts that work fine
Hey, I just got startet with HA, so sorry for the late answer. In case you still have this problem, you might change the fulfillment URL to the webhook-URL (instead of …/api/dialogflow…).
I also had to search through dozens of outdated guides and threads. The current way seems to be:
- add the dialogflow-component to your configuration.yaml
- in HA, go to settings -> integration -> dialogflow, confirm the question and then make sure to copy the new generated webhook-url straight away, because you won’t find it there again afterwards. This is the url that you need to specify as fulfillment-url in dialogflow!
- create the dialogflow-project with API v1 and the copied url
It’s quite obvious once you saw the entry in the integrations
Trying to set this up again, now that they have cloud support. In the browser console in the test app, everything works fine, and communicates with homeassistant.
But when I try to say “talk to my test app” or “talk to my (app-name)”, from google home mini, or from my phone, it doesn’t understand. Anyone here who have had this issue?
Have you deployed your app for alpha review?
No, I haven’t. Do I need to do that now? Believe I didn’t have to do that before. But it should work if I deploy it for alpha review?