this post was submitted on 07 Mar 2024

9 points (90.9% liked)

homeassistant

12080 readers

4 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

[email protected]

Nest Integration (lemmy.world)

submitted 8 months ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

Hi all,

Is Nabu Casa required for Nest Integration in HA?

I didn't see anything in the documentation up front noting it as a requirement. However, after a failed attempt at adding - along with a configuration requirement for home-assistant.io for authorized domain settings in OAuth Consent, I am having second thoughts.

Thanks!

top 13 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 8 months ago (1 children)

Hey I just went through google hell, make sure you are the Nest owner account, the project ID from the cloud page and the project ID from the nest page are whats needed on the last step, and at this part for me it still errored out after the redirect but did integrate nest.

You also as far as I am aware need external access with HTTPS set up, Porkbun was a breeze and I got myself a 10$/y .dev domain, and for that you will need to be able to open ports on your router. Honestly everything networking was easy compared to getting Google to play nice.

Also also its easiest if your browser session only has one Google account logged into it, good luck!

[–] [email protected] 2 points 7 months ago

Finally got it working - followed the directions. No ports to open. Thanks for the recommendations.

[–] [email protected] 2 points 8 months ago (1 children)

Not the original question, but if you have just a normal "Nest Thermostat" (Not learning or E) it has matter support and you can add it over matter without paying $5

[–] [email protected] 2 points 7 months ago

This is good to know the next time around. Thanks!

[–] [email protected] 3 points 8 months ago (1 children)

No. It is not a requirement

[–] [email protected] 1 points 8 months ago (3 children)

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

[–] [email protected] 2 points 8 months ago (1 children)

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.

[–] [email protected] 3 points 7 months ago

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!

[–] [email protected] 2 points 8 months ago

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.

[–] [email protected] 1 points 8 months ago (2 children)

Just checking, you're using a supported device, right?

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago) (1 children)

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.

[–] [email protected] 1 points 8 months ago

Yup just checking to eliminate anything obvious.

[–] [email protected] 2 points 8 months ago

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.