Google Assistant Local SDK - Local Fulfillment

Feature Requests
181

something is not right…
it was working, did a HA restart, then i saw some webhooks , probably the google devices that were not able to connect to nginx, those are the rejected promises below

then it switched back to cloud it seems

and then finally when i turn on a light, it doesnt work anymore, not with local or cloud
got a google message like :

Looks like HA is not avaible at this time

verry frustating

image
image1169×458 106 KB

182

i think it doesnt connect anymore, maybe i need to wait again for tha max 30 min after a restart of HA

183

omg, rebooted HA, and devices, now the verification issue is back
what a mess!! this script / local sdk is not ready yet

image
image1308×259 15.9 KB

184

my recommendation. Leave it alone. See if it fixes itself.

185

yeah, its reverted to cloud, lets wait indeed

186

how is it going on your side?

187

btw, is that marcusds guy, the one that updated the js file also on community or discord? maybe he can help us?

created issue thread here:

188

Mine is fine. Been working through restarts.

189

It has something to do with Name, the name field cleared the verification issue before, not sure why it doesn’t work anymore after a restart… Allthough I have setup it with a *

What is your Name on HA? And how did you setup on the actions page?

190

Could the name be this we set for the Home Assistant Instance ?
Where we also set measurement units and location for example.

191

Yes, the Name field is indeed important, not sure why…

192

That is why it is important. I am not sure if the home assistant “Name” (configuration pages) influences the name. I’d guess it does and you’d need to make sure it is finding it.

If you do a mdns scan you can see the names. Mine is just 'Home" so no issues.

I’m guessing if you have multiple HAs, you’d need them different for the scan to know which one? But regardless, you should make sure the Name in google actions matches your name in a mdns scan. However that is derived.

193

Yes and that’s why I wanted to suggest to fill the name field with the Home Assistant instance name, which is returned by a mdns scan.

1 Like
194

I’m actually wondering if the recommendation for

'.*\._home-assistant\._tcp\.local'

is incorrect. I am wondering if it should be ‘Home’ in my case or a regex for it. I dont want to touch it as its not broken. :upside_down_face:

Looks correct though. :thinking:

195

I have used the * before, it works for me, untill a reboot… Gonna rename my instance later and test again

196 
avahi-browse --all --ignore-local -p  --terminate  | grep ho
+;wlp58s0;IPv4;Home;_home-assistant._tcp;local

Personally, based on my data above, I don’t think its defined incorrectly. If my instance is ‘Home’. I would have thought:

Home\._home-assistant\._tcp\.local

based on their example:

my-device-[0-9]{4}\._http\._tcp\.local
197

how do you have it now setup on the actions page?

198 
.*\._home-assistant\._tcp\.local

If it stops working at any point, i’m going to use the one I believe it should be.

199

I have it now configured as :

.Home\._home-assistant\._tcp\.local

homeassistant:
  internal_url: !secret internal_url
  external_url: !secret external_url
  name: Home

restarted everything, no more verification issue, but also, the script isnt activated, the google device doesnt connect to HA
Are you using the original script? or the modifled .js file?

image
image709×296 7.22 KB

200

The latest one. No modifications on my side