google hub max either? i think the hub max, there is inly model , i think its the “nest” serie
this is an old device - or do you have a google nest hub max?
yes, i have an “google nest hub max” , there is only 1 version i believe
so maybe SDK only works with second gen ?
i do see some “SDK” stuff there tough
ravish
February 8, 2022, 2:09pm
25
Here’s the list of supported devices for local fulfillment:
1 Like
ok, that are all devices
1 Like
Thx for sharing.
That’s funny. All my old Google Home Mini devices have an error in the Chrome Console. All Google Nest devices, on the other hand, run perfectly and do not show any errors.
Got it to work guys , the docs are WRONG!
home-assistant:current ← trvrnrth:google_assistant_local
opened 10:21AM - 04 Feb 22 UTC
## Proposed change
<!--
Describe the big picture of your changes here to … communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Mirrors documentation describing the operation of the local fulfillment feature from https://www.nabucasa.com/config/google_assistant/.
Suggests use of the NGINX Home Assistant SSL proxy add-on to maintain secure external ingress.
Documents setting the local home SDK MDNS scan config Name to prevent IDENTIFY intents being sent for non-HA devices. Omitting this does not break the functionality, but results in a lot of logspam on every discovery round.
## Type of change
<!--
What types of changes does your PR introduce to our documentation/website?
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR.
-->
- [ ] Spelling, grammar or other readability improvements (`current` branch).
- [x] Adjusted missing or incorrect information in the current documentation (`current` branch).
- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch).
- [ ] I've opened up a PR to add logo's and icons in [Brands repository](https://github.com/home-assistant/brands).
- [ ] Added documentation for a new feature I'm adding to Home Assistant (`next` branch).
- [ ] Removed stale or deprecated documentation.
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- Link to parent pull request in the codebase:
- Link to parent pull request in the Brands repository:
- This PR fixes or closes issue:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [x] The documentation follows the Home Assistant documentation [standards][].
[standards]: https://developers.home-assistant.io/docs/documenting/standards
home-assistant:next ← marcusds:marcusds-patch-3
opened 10:08PM - 04 Feb 22 UTC
## Proposed change
<!--
Describe the big picture of your changes here to … communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Enable local query for google_assistant, the functionality is identical to cloud query, so adding the functionality only requires updating the JavaScript that runs on the assistant devices and configuration change.
Also a fix to remove `onProxySelected`. This change was the only way I could make google_assistant local fulfilment work on any of my devices, but I would like to see others results with this. Two years ago this seemed to be a requirement, but none of Google's own docs or examples use it anymore.
## Type of change
<!--
What types of changes does your PR introduce to our documentation/website?
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR.
-->
- [ ] Spelling, grammar or other readability improvements (`current` branch).
- [ ] Adjusted missing or incorrect information in the current documentation (`current` branch).
- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch).
- [ ] I've opened up a PR to add logo's and icons in [Brands repository](https://github.com/home-assistant/brands).
- [x] Added documentation for a new feature I'm adding to Home Assistant (`next` branch).
- [ ] Removed stale or deprecated documentation.
This is a little unclear which type of change because code is included in this documentation.
I would like to longer term look at serving the JavaScript from Home Assistant itself. That will result in easier setup for users (just setting a URL in the Google Assistant developer panel, rather than uploading code) and more importantly code living with code not documentation.
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
This builds on https://github.com/home-assistant/core/pull/63218
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [x] The documentation follows the Home Assistant documentation [standards][].
[standards]: https://developers.home-assistant.io/docs/documenting/standards
Do you have a link with the new JavaScript File?
sgobat
February 10, 2022, 2:45pm
31
I did try all the changed you mentioned, but I still get the same errors
sgobat
February 10, 2022, 3:39pm
33
The usual Device Verification Failed Error everyone seems to be getting lol:
I’m using the settings and the app.js file you linked in the other post.
Nabu Casa GA worked locally like 20% of the time so I think it can work with my current NGINX proxy manager settings. My devices are enrolled in the beta program and are mostly older devices, so I’m not sure if that’s causing complications. I’ll have to read more into the github links you sent to see if I can spot the differences!
Yes, that error I got too, the verification…
Look also here, threads should me merged…
@pergola.fabio yes but not for queries. I think that’s what he was asking about. btw, that image isn’t a local command. It should say local.
If you have DEVICE VERIFICATION ERROR:
Got it again working, change Name Field to : .*._home-assistant._tcp.local , so removed all the \ in that string, before it was like : .*\._home-assistant\._tcp\.local
EDIT: seems the one with \ is still working, i got it to work just by saying “sync my devices” i think that cleared the verification error
Here is new js file:
home-assistant:current ← marcusds:marcusds-patch-3
opened 10:08PM - 04 Feb 22 UTC
## Proposed change
<!--
Describe the big picture of your changes here to … communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Enable local query for google_assistant, the functionality is identical to cloud query, so adding the functionality only requires updating the JavaScript that runs on the assistant devices and configuration change.
Also a fix to remove `onProxySelected`. This change was the only way I could make google_assistant local fulfilment work on any of my devices, but I would like to see others results with this. Two years ago this seemed to be a requirement, but none of Google's own docs or examples use it anymore.
## Type of change
<!--
What types of changes does your PR introduce to our documentation/website?
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR.
-->
- [ ] Spelling, grammar or other readability improvements (`current` branch).
- [x] Adjusted missing or incorrect information in the current documentation (`current` branch).
- [ ] Added documentation for a new integration I'm adding to Home Assistant (`next` branch).
- [ ] I've opened up a PR to add logo's and icons in [Brands repository](https://github.com/home-assistant/brands).
- [ ] Added documentation for a new feature I'm adding to Home Assistant (`next` branch).
- [ ] Removed stale or deprecated documentation.
This is a little unclear which type of change because code is included in this documentation.
I would like to longer term look at serving the JavaScript from Home Assistant itself. That will result in easier setup for users (just setting a URL in the Google Assistant developer panel, rather than uploading code) and more importantly code living with code not documentation.
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
This builds on https://github.com/home-assistant/core/pull/63218
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] This PR uses the correct branch, based on one of the following:
- I made a change to the existing documentation and used the `current` branch.
- I made a change that is related to an upcoming version of Home Assistant and used the `next` branch.
- [x] The documentation follows the Home Assistant documentation [standards][].
[standards]: https://developers.home-assistant.io/docs/documenting/standards
It should looke like below when you inspect devices#devices
, first and second gen
I’ve restarted devices and home assistant multiple times. I will try and wait and see if it fixes itself 
