Nest integration fails to load first time in a new venv

[jretz]

The problem

When recreating the Home Assistant Core venv to pickup new versions of hass, the Nest integration fails to load on the first run. It works fine on subsequent invocations of hass until the venv is recreated.

What is version of Home Assistant Core has the issue?

core-2021.9.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Nest

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nest/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-09-06 19:19:08 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 9357e34937c1a2f1abc1b9a699908ed44b1ef2724fd68c87bdb254218848a307 from 127.0.0.1
2021-09-06 19:19:21 ERROR (MainThread) [homeassistant.setup] Setup failed for nest: unknown error
Traceback (most recent call last):
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/homeassistant/setup.py", line 207, in _async_setup_component
component = integration.get_component()
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/homeassistant/loader.py", line 516, in get_component
cache[self.domain] = importlib.import_module(self.pkg_path)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 848, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/homeassistant/components/nest/__init__.py", line 11, in <module>
from google_nest_sdm.google_nest_subscriber import GoogleNestSubscriber
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/google_nest_sdm/google_nest_subscriber.py", line 15, in <module>
from google.cloud import pubsub_v1
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/google/cloud/pubsub_v1/__init__.py", line 18, in <module>
from google.cloud.pubsub_v1 import publisher
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/google/cloud/pubsub_v1/publisher/__init__.py", line 17, in <module>
from google.cloud.pubsub_v1.publisher.client import Client
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/google/cloud/pubsub_v1/publisher/client.py", line 45, in <module>
__version__ = pkg_resources.get_distribution("google-cloud-pubsub").version
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/pkg_resources/__init__.py", line 481, in get_distribution
dist = get_provider(dist)
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/pkg_resources/__init__.py", line 357, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/mnt/mule/homeassistant/venv/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'google-auth<2.0dev,>=1.25.0' distribution was not found and is required by google-api-core

Additional information

Adding google-nest-sdm to the new venv before starting hass for the first time prevents the issue.

[probot-home-assistant]

nest documentation
nest source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (nest) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[allenporter]

There is a mess of pins of google python libraries here:

core/homeassistant/package_constraints.txt

Line 55 in 789f21c

# https://github.com/home-assistant/core/issues/53427

Because of a grpcio armv7 bug that was still broken as of May 31st.

I'm attempting to try to get to the bottom of it, but making slow progress.

[allenporter]

Do you have steps to reproduce this?

From discussion in #55687 it sounds its easy for other library versions to get upgraded without home assistant knowing about it, so i just want to make sure.

[jretz]

Here are the smallest number of steps I could find that show the problem:

# Start with an empty dir with the simplest possible config
mkdir issue-55883
cd issue-55883
echo "default_config:" > configuration.yaml

# Install hass into a fresh venv
python3.8 -m venv venv
venv/bin/pip install homeassistant

# Run hass
venv/bin/hass --config .

Now go through the on-boarding flow in a browser (defaults are fine). When the on-boarding flow gets to the integrations page, select "More" and install Nest. An on-screen error message will say "Config flow could not be loaded" and the console will have the traceback shown above. As above, doing venv/bin/pip install google-nest-sdm before running hass for the first time avoids the error (perhaps also causing dependency version issues? I haven't seen ill effects yet, but that's not much evidence).

[allenporter]

I ran your repro steps in two separate venvs, one with your original steps and one with your fix steps. I then ran pip3 freeze in the two venvs and diffed the output which shows these differences:

$ diff /tmp/issue-55883-*
30c30
< google-api-core==2.0.1
---
> google-api-core==1.31.2
33c33
< google-cloud-pubsub==2.8.0
---
> google-cloud-pubsub==2.1.0
38c38
< grpcio==1.40.0
---
> grpcio==1.31.0

[allenporter]

This specific failure appears to have been fixed in googleapis/python-pubsub#393 in v2.4.2

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[allenporter]

I consider this still an issue, blocked on being able to upgrade grpcio.