Mine’s still working with 2.1.5.
Your best bet for debugging is
https://console.cloud.google.com/
btw, I don’t care of the instructions say ‘wait 30 minutes’. Reboot ALL of your homes. Only one random one is used to push and you won’t know which one. For debugging, you may only want to plug in one of them.
i always reboot both of them. what should i be looking at on that url?
i think i just realized something. if i have this in my config:
homeassistant:
#Name of the location where Home Assistant is running
name: Smith Home
would i need to change the info under the MDNS section? If so, any idea what i would change it to?
Yea, changing it to Home didn’t change anything.
You can do it all in the UI:
Settings - system - general
Settings - system - network
You can just change the ‘name’ in teh google actions config to match yours though. I am not sure how a space is handled.
Follow the directions there and look at the console messages to see what the error is.
there are no errors in the console. thats just it. something isnt configured right. i dont really understand why one version works perfectly fine and the newer one doesnt. i am not sure i totally understand the mdns section though. if my hostname is different, do i need to make changes to that section?
Hostname doesn’t matter. It uses mdns.
What I would do is you
avahi-browse -avpr
to see if its broadcasting mdns entries. and then see what they look like.
I’dalso check to make sure you google integration is working. Maybe its having an authentication issue.
i am running home assistant container. i tried to do
sudo docker exec -it home-assistant avahi-browse -avpr
and it failed.
OCI runtime exec failed: exec failed: unable to start container process: exec: “avahi-browse”: executable file not found in $PATH: unknown
my google integration is working fine and on app.js version 1.1.0, local fulfillment also works perfect. the only thing i do is upload the 2.1.5 version, save and reboot the minis and local fulfillment breaks. actually, using the app.js version 2.1.5 breaks all voice commands related to the entities exposed to google through home assistant.
in the inspect logs, i can see all the device exposed to google through hass i just cant control them. says something like, the office light isnt available right now
@Davidy any chance you would be willing to report your results here:
Might help work towards a solution.
Hi,
I’m using the local fulfillment good for couple of months…Now updated HA to latest version and i saw in the logs this:
Local SDK version is too old, see documentationn how to upgrade
But i cant find it, how do i update it?
Sorry but i dont see it 
Been reading it over and over
Its directly in the second link. You replace the app.js.
Thx will try asap
Mmm i deleted the old app.js file.
I uploaded the new app.js file for both nod and chrome… and saved
But still i got the warning “local sdk version is too old, check docu how to update”
restart your google homes. like hte doc says or wait and it’ll eventually do it.
i think its gone now 
thx
The warning is gone, but today i got 2 new ones
Does it relate?
Anyone now where to look for to fix?
No. and those happen quite a bit. The google api…
I updated to 2.1.6 last week and have had no issues with Local Fulfillment since then.
