Googleassistant local SDK

Configuration Voice Assistant
1

Hi,
After the local SDK from GoogleHomeassistant is supposed to work with the new update from HA, I tried it out right away.

I had already configured GoogleAssistant and it is running quite well so far.

Today I then configured the locale SDK according to the official instructions.

Then I listed the devices in Chrome and checked what was happening with the Inspect button. Here, however, error messages are constantly being thrown out:

[134.120s] [smarthome.DeviceManager] Logging to stackdriver: {"requestId":"Axxxxxxxxxxxxxxxxxxxxxxxxxxx6","timestamp":{"seconds":1643917335,"nanos":511000000},"appVersion":"1.0.0","intent":"action.devices.IDENTIFY","severity":"ERROR","message":"{\"requestId\":\"Axxxxxxxxxxxxxxxxxxxxxxxxxxx6\",\"payload\":{\"errorCode\":\"DEVICE_VERIFICATION_FAILED\",\"debugString\":\"VerificationId failed to match any unverified devices.\"}}","errorCode":"DEVICE_VERIFICATION_FAILED"}

Can someone tell me whats wrong?
What can i do?

Regards
Hermann

1 Like
2

yes, i see the same error, any idea? Have you found out?

image
image881Ă—556 60.1 KB

3

I get the same errors too.

4

According to documentation DEVICE_VERIFICATION_FAILED is Returned when the device is not found in sync-ed devices.

May be it is related to a removed exposed homeassistant entity?

5

What do you mean by : removed exposed home Assistant entity?

6

I’ve got it partially figured out now.

Please make sure that your home assistant can be reached locally at http.
Then add another mDNS entry in the Action Console: Home._home-assistant._tcp.local

After a few minutes then restart the Google Smart Speaker.

Now it should work after a few minutes.

Is it possible that older Google Home Mini’s are no longer supported? I no longer have any error messages with the NEST devices, the message only comes up with the Mini of the 1st generation.

2 Likes
7

Another mdns? Why do you need 2 ? And how to obtain that value?

8

I read this notice on the Discord forum. If I run an mDNS scan locally, then you can find it too.

As I said, add the entry, make sure that HA can be reached under http. Then it should work.

9

Ok, worth a try… How to run a mdns scan? To obtain the value?

10

ok, downloaded an mdsn browser, its being discoverd, as you can see below,

and that entry was already added on the actions site, so i think everything is already correct setup

image
image896Ă—459 19.2 KB

image

11

ok, i have it like below, now, added a second with “home.” at the front, now it seems the error is indeed gone when i inspect the devices, but the commands are still not fired local…

do you still have an internal/external url set in the config? people are saying they need to be blanc now?
image

image

image
image840Ă—306 9.67 KB

12

Yes,
i have set the internal URL to http:// and external URL to https://<my.dns.name>

But after i change the Internal URL i have the following error:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 334, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"
2022-02-08 08:01:49 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):

It seems, there is a device that will connect internal via https - my old internal value - but i can’t find this device :wink:

13

it still doesnt work for me, think i’ll give up

14

can you access your HA via http internal? via IP Address without error?

15

yeah, local i always use http , only from companion app, i use duckdns

16

and from outside you can access vi https too?

17

yes, using duckdns via nginx

18

do you have a newer Google Device? My old Home-Mini have always the Problems. So i think, that only newer Devices are supported

19

its a mix , 2 old mini’s first version, and then a google hub max
but tried all devices

20

i think this is the problem. these devices are not supported.