this post was submitted on 07 Mar 2024
9 points (90.9% liked)
homeassistant
11878 readers
3 users here now
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No. It is not a requirement
I've double-checked settings.
I can select the Google Nest Integration. I enter my Cloud Project ID and click Submit with no error. I am then prompted for my Device Access Project ID, which I enter and click submit. I am then presented with a screen from Google saying that it can't link to project. No other information and no error. Nothing in the home assistance core logs. I've double checked the settings and I know that Project ID is correct as it returns the project name that I set, "HA Nest Project".
Not really sure where to look for issues - any suggestions are appreciated.
Just upgraded to the latest update. Running: Core 2024.3.0 Supervisor 2024.02.1 Operating System 12.0 Frontend 20240306.0
Can you share a screenshot of the error? (Block out any PI of course.) I run into this issue due to my DNS blocking things that Google uses for the integration. I take my cell phone off WiFi, run the integration steps and viola, it connect.
I don't believe remote access is required but I pay the subscription cause lazy and want to help fund the project.
Finally got it to work. I think that on a previous try and failure, my credentials were saved while I had gone back and recover everything over. Cleared out the old credentials, started all over and worked!
I've integrated a Nest E thermostat myself so I know Nest devices work. The setup is a bit of a ball ache though.
For an age I had issues with Google Assistant integrated products though. It would be connected and then lose the connection and sometimes it would just not want to reconnect, for days at a time.
I've found it was mainly due to how I was remote accessing my instance. I was using DuckDNS and Nginx. I moved to using Cloudflare and bought my own domain name, and suddenly everything worked much better.
I would however have Nest drop off and require reauthenicating every time my HA instance was rebooted. This was until I had someone suggest I make my Google Project "Production" rather than "Testing" which stopped that.
I now have a rock solid connection to Google and my Nest thermostat works as expected except for one little quirk where temperatures are displayed in HA 0.2 degrees higher than they actually are.
Just checking, you're using a supported device, right?
Supported as in a yellow or green device? No, I'm running virtually off a booted SSD on a PC.
Why is that relevant to my problem? Same software as everyone else and, otherwise, has been running reliably.
Sorry, just realized you meant Nest device support. Yes, per the instructions, and the Google Device page:
" Thermostats
All Google Nest thermostat models are supported in the Device Access program and the API functionality is the same for all models. See the Thermostat device guide for more information.
Yup just checking to eliminate anything obvious.