ah, you mean this one?
In the Actions console, right below where you add the .js files.
But do not run off and tick it yet!
I believe it makes no difference, as the Query intent is not fulfilled by HA anyway:
I have just enabled logs on my Action and will test further to check if the Name field makes any difference at all.
name field does remove errors , noticed when enabling local query tickbox, it gives errors again
1 Like
if i enable that “support local querey” with also Name field configured, i receive the error below
gonna try now, without a name field and local support ticked , like you
EDIT: tried without Name field, and “local support query” ticked, still above error, and still no local command
what firmware do you have on your google mini’s?
You did fill in the correct fullfilment url in the top of the actions page ?
https://mydomain.nl/api/google_assistant
- 1.54.277099 on Nest Minis
- 1.56.282045 on first-gen Home Minis
EDIT: I just updated the action, rebooted every Google device and then HA. Local Fulfillment still works for me.
From this test, I learned:
- the Support local query does not apply and the box should be left unticked.
- Setting the
Namefield to.*\._home-assistant\._tcp\.localdoes removeDEVICE_VERIFICATION_FAILEDerrors from the logs (thanks to @Tyrian81 for the tip). I suspect it makes the Action talk only to HA devices, filtering other mDNS devices on the network (such as Google speakers), which just get rejected anyway while throwing that error.
yeah, otherwise i wouldnt be able to link the “test” app 
1 Like
ok, my first gen mini’s have the same firmware, so thats not the culprit then
hmm, the error is back, just with ticking the option "enable local support’ on and off again
what a crap
Edited my posts above.
Adding the Name field fixes those errors, but the issue of Local Fulfillment not working must be somewhere else.
really frustating
I think it is not fulfilled by HA if enabling state reporting, so when setting report_state: true in the YAML configuration.
If set to false I suppose it will be fulfilled locally but on Nest Hubs state won’t work in real time.
For Nginx users: check if there is no trailing slash at the end of the proxy_pass directive, as specified in the documentation.
I have now set as test : report_state: true
But doenst make any difference, what do you mean by that “proxy_pass” ? i dont have that setting anywhere?
i installed the basic nginx addon, not the manager , and this is my http config
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
It might make a difference when local actions will work.
OK so with the addon this trailing slash should be the issue as you only specify domain name.
And if you set the internal URL but no external in HA settings it does not make any difference?
yes, i tried removing internal + external url also, seems HA only makes the internal url visible in mdns
so tried all combinations, no success
also that proxy_pass, i have the basic nginx addon, so dont have that setting i think
I’ve tried literally all the hints in this thread but never could get it to fullfill locally. The adding of the ‘name’ did temporarily stop errors but they came back and even then just wouldn’t fullfil locally. idk why.
Same boat here, never got it too work
I just got mine to work. I am not sure why though. But I am not clear as to why or how. I’m trying to make it break now to understand what change I made actually helped. I didn’t make a lot. I’m quite baffled at the moment.
EDIT: I actually think that the root of the fix is simply telling google to sync devices after rebooting HA. As obscure as that is… I just undid all my test changes just now. restarted HA, local didn’t work. I said “hey google sync devices” waited a few seconds. Then it works?
Nope. That’s not it either. I have ZERO idea why it is now working. But happy to compare settings @pergola.fabio if you want.
Yes, where do we start?
Would be helpfull to others too I think?