Hmm, that doesnt work for me,…
if i fill in as name:
.*\._home-assistant\._tcp\.local
Then i receive error below
If i fill in as name :
home._home-assistant\._tcp\.local
Then no error, but still doesnt work, commands ane not sended with local SDK
Do you see it using local? in your logbook?
Do you have setup an internal/external url in your config, or are they blanc?
how did you obtain that Name field anyway, where is it coming from?
If i fill in : home._home-assistant\._tcp\.local
Then no errors, but still no (local) command
also not after a reboot of google device or resync
Yes doing local , but understand that these settings do not apply for Nabu Casa users.
And in my HA both internal and external URL’s are set.
another way to check if its doing local is by seeing your google cloud logs btw.
https://console.cloud.google.com/logs/
It’s sending the command locally , then sending back the state of device via cloud.
yeah, i dont nabucasa, its tha manual setup
ok, gonna setup my internal/externa url back
how did you obtain that “name” field?
also that logs pagen it looks different for me?
You have to click on the “Add Field” button on the actions page under develop to add the name field.
You can hide the Log fields and Histogram if you like, by clicking the eye icons
Then you can add the exectution type and latency to your log query by clicking Partner_cloud → add field to summary line.
executionType: "PARTNER_CLOUD"
latencyMsec: "31"
requestId: "825943507253339269"
I would add the *.\ in the name as not every user has the same instance name …
but its strange, i still see verification error below, but if do the inspect devices, i dont see any error there
i think it related to that “name” field, need to know the correct value there?
When saving your MDNS name , restart your google device , and HA
ok, Name : .*._home-assistant._tcp.local
that looks better indeed, after restart HA and devices… i see more now when i inspect devices…
but you told earlier: by clicking Partner_cloud → add field to summary line.
Where do you se that partner cloud? i also see errors below, you too?
Click on one log query, expand nested fields, and look for execution type and latency , click them and add field to summary line. You can also save this query by clicking the floppy disk.
No after adding a Name: field I have no more errors in logs
yeah, i dont have those logs it seems, but maybe i know why
i all have first gen devices (minis) and my google hub max is also a first gen device
maybe thats why i dont see those
The only thing that’s bugging me is the latency , local in logs seems slower for me than the cloud 
Locally i would expect latencies below 20ms
Must be some network setting, still trying to figure it out.
You can try to add your google devices in the preview program, which all of my devices are.
https://support.google.com/chromecast/answer/6343937?hl=en#zippy=%2Chow-do-i-join-the-preview-program
Preview firmware gets loaded to your devices.
Which may take a while btw , up to google servers.
ok, i can do that indeed, preview is off
what type of devices do you have?
A Nest hub , 2 Nest mini’s and a google home mini , haven’t tested on the home mini yet , could be unsupported for local.
but are they first or second gen ?
hmm, seems my hub max was already in preview, firmware : 276689
added the google minis now too, need to wait now
In my case, Local Fulfillment is still working on 2022.2.3, what I have different is:
Not sure if any of those factors apply.
Edit: I can also confirm, by asking a first-gen Google Home Mini to turn on a light, that the action runs ands shows as (via local) on HA logbook.
interesting, where is that " * I did tick the Support local query box." ??
