#Google Assistant local fulfilment issues

1 messages · Page 1 of 1 (latest)

dreamy radish
#

If I run avahi-browse -alr, I see _home-assistant._tcp.local

+    br0 IPv6 _home-assistant                               _tcp                 local
+    br0 IPv6 homeassistant [7e136c6b71314c48ac5c4fbe5fb855ac] Workstation          local
Failed to resolve service '_home-assistant' of type '_tcp' in domain 'local': Invalid service type
+    br0 IPv4 _home-assistant                               _tcp                 local
+    br0 IPv4 homeassistant [7e136c6b71314c48ac5c4fbe5fb855ac] Workstation          local
+    br0 IPv6 Home                                          _home-assistant._tcp local
+    br0 IPv4 Home                                          _home-assistant._tcp local
=    br0 IPv6 Home                                          _home-assistant._tcp local
   hostname = [96bfa232c8ea4eb6931d3a55e2610cfb.local]
   address = [192.168.86.68]
   port = [8123]
   txt = ["requires_api_password=True" "base_url=https://XXX:8123" "internal_url=" "external_url=https://XXX:8123" "version=2022.2.0" "uuid=96bfa232c8ea4eb6931d3a55e2610cfb" "location_name=Home"]
=    br0 IPv4 Home                                          _home-assistant._tcp local
   hostname = [96bfa232c8ea4eb6931d3a55e2610cfb.local]
   address = [192.168.86.68]
   port = [8123]
   txt = ["requires_api_password=True" "base_url=https://XXX:8123" "internal_url=" "external_url=https://XXX:8123" "version=2022.2.0" "uuid=96bfa232c8ea4eb6931d3a55e2610cfb" "location_name=Home"]```
dreamy radish
#

Made some networking changes to get multicast to go to my bridge and it now shows up in the discovered devices on the Home, but getting other errors.

dreamy radish
#

Apparently the issue I am having now is related to none of the devices showing up in the GH having customId.webhookId prop as seen in the function findHassCustomDeviceDataByMdnsData

#

Is something not being exposed that is supposed to be?

dreamy radish
#

This whole issue seems to be related to https://github.com/home-assistant/core/pull/64983

Since I am using SSL/HTTPS I cannot use local fulfillment.

I really hope that this issue can be worked around.

At the very least, users need to be informed that this is a limitation.

tawny cloak
#

In the action console Fulfillment URL says The URL must start with https:// and if that in turns require any ssl certificates to be valid, then i dont see how that would work. I have valid ssl for internal hosts using dns challenge but either dns lookup is done in the cloud or the google devices use google dns servers and not my local that resolves my internal hosts with valid letsencrypt certs.

dreamy radish
#

I think part of the point is is that it doesn't use the fulfillment URL instead it uses something that's passed to it during MDNS

dreamy radish
dreamy radish
dreamy radish
#

OK I finally have it working, to get it working I had remove the function call to onProxySelected in app.js not sure why, but it works great after removing it.