Google Nest Integration Broken Suddenly

Configuration
1

I have been using the Google Nest integration for a very long time without issue. However, earlier this week it stopped working for no apparent reason. I deleted the integration and set it back up again, and it worked, at least for a few hours. Now it’s dead again, reporting little more than ‘timeout’ in the debug logs.

Is anyone else having similar issues with the Google Nest integration? Any suggestions on what to test or look for? I’ve checked my firewall and verified that all IDS/IPS features are disabled, and I have an exception specified in AdGuard for the ‘real’ IP of my HA server, as well as the docker network. Neither the firewall or Adguard logs show anything dropped or blocked in the logs from HA or any of the containers.

It’s very likely that if I delete the integration and set it back up, it will probably work again for another few hours. However, that’s not a real solution. Debug output below.

2025-04-04 07:38:55.552 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home for nest
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 703, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 548, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1056, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1362, in _create_direct_connection
    hosts = await self._resolve_host(host, port, traces=traces)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 970, in _resolve_host
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 753, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/nest/__init__.py", line 203, in async_setup_entry
    await auth.async_get_access_token()
  File "/usr/src/homeassistant/homeassistant/components/nest/api.py", line 49, in async_get_access_token
    await self._oauth_session.async_ensure_token_valid()
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 537, in async_ensure_token_valid
    new_token = await self.implementation.async_refresh_token(self.token)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 118, in async_refresh_token
    new_token = await self._async_refresh_token(token)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 199, in _async_refresh_token
    new_token = await self._token_request(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 218, in _token_request
    resp = await session.post(self.token_url, data=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 607, in _request
    with timer:
         ^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/helpers.py", line 671, in __exit__
    raise asyncio.TimeoutError from exc_val
TimeoutError

You can actually see the moment it stopped working

Screenshot 2025-04-04 at 2.19.22 PM
Screenshot 2025-04-04 at 2.19.22 PM1985×1300 197 KB

2

I have not run into this issue so this might not be the answer you are looking for but the Nest design (I had a Nest Learning Thermostat) often had connectivity issues since they are cloud based and after endless tweaking with a very strong network connection with even a dedicated WiFi SSID with endlessly tweaked settings and even a new wireless access point right nearby, as well as replacing the thermostat with the latest version, etc., etc., - I finally threw in the towel on Nest altogether. Also the Google Nest integration is a convoluted mess to set up online with a google developer account tro then pay $5 to set up etc. which is absolutely ridiculous unnecessarily jumping through hoops to get something to work…

With the idea of only wanting rock solid 100% uptime AND LOCAL connectivity, after some research I finally landed on the Ecobee ECB501. I did not like that I had to connect to it directly for HA through the Apple HomeKit integration, but it has NEVER been disconnected ever since buying it three months ago. No ISP is perfect. It does also have a cloud connection for one’s ecobee acocunt and more detailed historical analysis of activity etc., but the HA connection to it is COMPLETELY local. I did some network analysis after buying it - and from time to time it is disconnected from the internet and then reconnects on it’s own - but I believe that may be ecobee servers or my ISP - but that is unrelated to it’s direct connection to the local network so it’s connection to HA has been continous and never went down.

I hope you resolve your issue - but even if you do - it will from time to time not be available because it is 100% cloud based. Therefore I strongly suggest you would want to switch to something that connects to HA through a LOCAL connection. After three years of struggling to get 100% reliability with Google Nest (which is literally impossible with any cloud based solution - which also introduces latency even if connected) - I can tell yuou you will have to go the completely local connection route to approach 100% reliability.

Good luck

3

Yeah, that is where I am, once this heating seasons ends, I’m tossing out the Nest and going to Ecobee.

4

That’s a good choice. There are others out there but not very many that have a local connection to HA.I just wanted to mention, I am not sure what power utility you use, but in northern NJ (USA) I found a web site that is called the PSE&G (Public Service Electirc & Gas - my utility) “marketplace”. I got mine for $100 off there, about $149 or so. So, your local utility may offer a big discount, definately worth looking into :slight_smile:

Of course I had to change alot of automations etc., and the scheduling for the HVAC settings is very differently set up with alot less granularity, but after a little head scratching getting used to it and changing your automations all around you’ll be good to go. It’s the HA way - (we all enjoy riding the struggle bus!!)

(P.S. their scheduling in the Ecobee app has a couple of bugs in that you cannot add more than 10 settings in one area, etc. (the phone app blows up) but you’ll discover that and work around it lol)

5

Thanks for the tip. I’m in upstate NY and just checked NYSEG and they offer similar discounts!

I have all my scheduling in HA, so as long as I can set the target temperature via HomeKit that should work. I’m also assuming the hvac action comes through?

When you say “loss of granularity” is that is setting up schedules of the thermostat? Or data reporting? What’s the temperature granularity that is reported (1 degree, 0.5, etc.)

I also use Honeywell T6 zwave thermostats which have been super reliable but the UI is weak. I run 3 of those and 1 NEST. There’s also benefits of not having everything on zwave.

1 Like
6

By granularity I meant for setting up the schedule in the thermostat app