Using latest instructions and app.js works locally with debug but once uploaded never reaches home assistant instance

[tailg8nj]

I'm not sure what else to try here but I'll describe my problem:

I had a 5 year old Google cloud project that was set up and working with local fulfillment.

I deleted the project to start from scratch and created a new one following the entirety of the instructions up to and including https://www.home-assistant.io/integrations/google_assistant#enable-local-fulfillment.

Both were leveraged in the same docker container style Home Assistant install running on a pi.

Cloud fulfillment works fine. Local fulfillment works fine in debug mode when starting the server up as found in this README although it launches on port 8081 instead of 8080 like listed. Therefore I point both testing URLs to http://{home network ip of my laptop:8081}/test_receiver.html.

I can confirm the local messages are getting to my Home Assistant instance seeing things like:

2025-12-04 19:17:41.396 DEBUG (MainThread) [homeassistant.components.google_assistant.helpers] Responding to local message CD753C381CE0926EAA476E92EB14BFE5

And launching Chrome DevTools does indeed show appropriate event handling in the Javascript as well.

However, once I upload the JS file found in the releases section on GitHub, or my own from the npm commands above, I fail to see any local messages hit my Home Assistant instance.

It looks like each time I upload a new JS file, the URL changes that is found under the chrome://inspect/#devices inspection and always has a format similar to https://storage.googleapis.com/ndc-prod-{my project name}-public/TempFile_5354c401-b735-4173-b69d-14291ae64b48.html. I can't view that HTML file because I do not have the appropriate permissions to debug any further.

Does anyone have any advice on how to further debug?

• I restored my previous Google cloud project, disabled local fulfillment, and re-shutdown, however it won't be fully evicted until January.
• I've cut power to all google homes except one in my house to try to narrow down the issue, but each permutation suffers same. They all point to the same temp HTML file though when I inspect them in chrome://inspect/#devices.
• I've tried uploading the app.js from ubuntu and Mac in case permissions, line endings or anything like that could be involved.
• Because this once worked before, and currently works in debug mode, I think my mDNS and zeroconf settings are correct. I can see my home assistant instance using avahi-browse.

Has anyone tried to start from scratch lately and run into the same issue?

[tailg8nj]

Following up, I tried bootstrapping a completely new project using the same steps yet again, and noticed a brief toast/error message that pops up upon the first and only the first time trying to enable local fulfillment:

The member bindings allUsers and allAuthenticatedUsers are not allowed since public access prevention is enforced

It does not show up in subsequent saves. I redid everything yet again and enabled developer tools to see if there are any more details and I see the following response trying to PATCH the project:

Form payload section on saving in the Developer Console:

{
    "nodeJsSourceUrl": "https://storage.googleapis.com/smarthome-agents-prod-dropzone/TempFile_aff21009-499b-4b46-929c-4a7ac9999506.js",
    "executableJsSourceUrl": "https://storage.googleapis.com/smarthome-agents-prod-dropzone/TempFile_4fa762b2-4dfd-406d-a308-33e399c5428c.js",
    "supportLocalQuery": true,
    "scanConfiguration":
    [
        {
            "discoveryProtocol": "MDNS",
            "deviceIdentifier":
            [
                {
                    "type": "MDNS_SERVICE_NAME",
                    "value": "_home-assistant._tcp.local"
                },
                {
                    "type": "NAME",
                    "value": ".*\\._home-assistant\\._tcp\\.local"
                }
            ]
        }
    ]
}

{
  "error": {
    "code": 400,
    "message": "The member bindings allUsers and allAuthenticatedUsers are not allowed since public access prevention is enforced.",
    "status": "FAILED_PRECONDITION"
  }
}

On a subsequent save, I do see a response that shows URLs similar to what I described above. All existing in /ndc-prod-{my project name}-public/TempFile*.html that do not seem to be publicly accessible.

When I try to debug using Chrome developer tools, the debugger keeps disconnecting with the Home, and I can never catch it in time to see if it is downloading the HTML correctly, although it does show up in the sources tab. When right clicking, "Open in Network Panel (missing request)" is disabled.

For what it's worth, I can again confirm the local testing URLs work when hosted on my laptop and send appropriate local requests to HA. It's just not the js files I upload.