Google assistant: disconnect user agent when not found in google

[bramkragten]

Proposed change

Google assistant: disconnect user agent when the user agent is not registered with Google

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[bramkragten]

CC @elupus

[elupus]

Looks good. Seems it also partially fixes the 404 on missing entities for report state. By making sure a sync is done on startup for local installs too.

Should we perhaps fix so we schedule a resync for local for all types of config entry changes (since they can have added entities).

[bramkragten]

Looks good. Seems it also partially fixes the 404 on missing entities for report state. By making sure a sync is done on startup for local installs too.

Should we perhaps fix so we schedule a resync for local for all types of config entry changes (since they can have added entities).

I guess that could be moved to the AbstractConfig in a future PR.