Nest thermostat connectivity lost to Alexa and Home Assistant

[Paulb007]

Received a strange email today from Google saying to check my permissions as a new device was added. Logged in to account and can only see both these allowed connections, both enabled fine. But I have lost the connection from both these but my Nest app still works fine. So all signs are that it is working ok, all connected but there is some issue with allowing it to share data with Alexa and HA. Anyone else? Any ideas as I cannot see how to fix.

thanks.

[humbertogarcia]

Hi Paulb007,

Thank you for posting in the community! I understand your Alexa and Home Assistant connections to Nest have stopped working, even though the Nest app itself is fine. The email you received from Google is a key clue, and I'll be glad to help you resolve this.

This scenario is usually caused by an issue with permissions or authorization, and the most reliable way to fix it is by re-authenticating your connections.

• In both your Alexa app and Home Assistant settings, completely remove the Nest integration.
• Next, follow the setup process to re-add the Nest integration from scratch. This will force a new login to your Google Account and refresh the connection.

Please let me know if these steps solve the problem. If they don’t, feel free to read the help article: Control Google Nest products with Amazon Alexa. 

I'm here to assist you, and I may have a few more questions for you to help us get to the bottom of the situation.

Regards,

Humberto

[Paulb007]

Hi, ok, I had already deleted about 10 times from Alexa but done that again and with reluctance deleted from HA. I checked in my google partner access and all empty. 

I added back to HA and it goes all through the steps ok to add back my GCP credentials and connects ok. It asks me to provide access again which I have. It still doesnt work.

On Alexa, it goes all through adding the skill back in and granting access. It then will not find the device.

Now, the add in back to HA also is different in that it seems to have connected Home and even though it has my thermostat (Hallway) as allowed access it doesnt find it as an entity.

So, here is where we are, it seems for some reason that any partner apps now cannot see the thermostat itself yet the Nest and Google Home app does.

The slightly strange thing is in the Google Home app I can control it fine but when I select the settings icon I get 'requested entity was not found'. 

So what has changed? Why did I get this strange email (as some others have on the HA community forum) and why now can I not access it from any other partner apps?

Views below show 1. emptied partner data, 2. HA re-added, 3. Alexa re-added.

[humbertogarcia]

Hi Paulb007,

I appreciate you taking the time to troubleshoot and to share your concern about the Nest thermostat's connectivity to partner apps. Thank you also for sharing the views.

To help me investigate what’s happening, could you please provide a bit more information?

• What is the specific model of your Nest thermostat? The help article "How to tell which Nest thermostat you have" can assist you.
• Did you already contact Amazon regarding this situation? Check Control Google Nest products with Amazon Alexa.
• Are you able to control other Google Nest products you may have with Alexa or Home Assistant?

This information will allow me to provide more targeted assistance. I look forward to your reply.

Regards,

Humberto

[Paulb007]

Hi, many thanks.

I dont have any other Google devices. I havent raised an Amazon issue as frankly no point as previous hlp on any Amazon devices has been laughable and as it broke same day on my Home Assistant its Google side for sure. The version is of the display when I go to Technical info is 3.4 so my understanding is this is a 3rd gen but not sure now. Your table shows 3rd gen with a 8.26cm illuminated area display which is really big and bigger than the 4th gen. But the tables also shows 2nd gen as 4.57cm illuminated display - mine is inbetween at 5.5cm. I would say the whole screen including the black non-illuminated is 8.2cm. So is the version shown in the settings the gen? or another more technical way to tell than measuring the screen which doesnt fit any?

My issue really is why did I get this email from Google when I did nothing: Link your new Nest device to your partner connections. This corresponds to when it broke so what happened?

Thanks for help, driving me mad. Paul.

[humbertogarcia]

Hi Paulb007,

Thank you for your prompt response. I understand that identifying your Nest Learning Thermostat's exact generation can be a bit confusing given the different measurements.

To confirm if it's a 2nd or a 3rd generation device, which is crucial for understanding its compatibility, please re-check the software version displayed under 'Technical Info'. You can also refer back to the visual guide in the article: How to tell which Nest thermostat you have. Especially the paragraph “Differences in the thermostat base”. Your previous note about version 3.4 is a significant clue, as that software version is typically found on 1st or 2nd generation Nest thermostats.

I look forward to your confirmation on the thermostat's generation. Once I have that, I'll be glad to help you with the next steps to investigate this.

Regards,

Humberto

[Paulb007]

Brilliant thanks. It has a home link which after looking at some other Google info I wondered if useful to know.

software says 6.4-5. No updates. Model-3.4

base software 2.3.27/3.1

backpkate 6.5

heatlink s/w 2.1.2-1. Model Amber-2.5

I can’t help feeling that there is something that happened in the allowing of the device itself to be seen by other partner apps. This would tie in with the email also.

thanks for help, Paul

[humbertogarcia]

Hi Paulb007,

Thank you for the time to investigate on your side and for sharing your concern about the issue.

The team would like to learn more about this situation. When you get a chance, please fill out this form and let me know when you’re finished. We’ll have someone reach out to you via email from there. 

Regards,

Humberto

[Paulb007]

Hi Humberto, I have completed the form. Many thanks for supporting.

[Paulb007]

Any update on this? The initial response was to do what I had done several times already, remove/re-add... 

Thanks, Paul.

[humbertogarcia]

Hi Paulb007,

Thanks for filling out the form and the update on the escalated team's first response.
I understand it can be frustrating to be asked for information you've already provided. Often, the team needs to confirm details directly to ensure they have the most accurate and up-to-date picture as they begin their investigation.
To help them focus quickly on a solution, I recommend providing them with a concise summary of

• All the troubleshooting steps you've already attempted, along with the results for each.
• Your specific reasons for not being able to contact Amazon regarding the Alexa connectivity.

If they contacted you via email, replying with this summary will be very helpful.
Please keep me informed of your progress with the escalated team if you feel it's necessary. While the specialized team has the advanced tools to resolve this particular issue, I remain here to support you in any way I can throughout the process.

Regards,

Humberto

[Paulb007]

Thanks, I believe I gave this info in the email answer.

I have not contacted Amazon as the same day it broke in my Home Assistant as well so the common factor here is only Google/Next/some other issue like home network. The last seems unlikely as it works fine in Nest app still.

I have multiple times deleted it all, restarted apps (Alexa and HA), restarted Nest device including the heat link.

I have ensured it is all removed, check that the partner connections are gone, in Alexa made sure the skill is removed. All clear.

Then re-added in Alexa by adding the skill. This then adds the partner connection back in as expected in the Google partner manager. It is also set to allow including at the device level (my hallway thermostat). All good but then Alexa cannot find the device.

In Home Assistant similar in that I re-add the integration, this then re-adds HA in the Google partner manager, I ensure all parts are allowed including the device. In HA it looks great in that it adds all the integration back in but it never sees the device. This aligns exactly with Alexa.

I am lost what else to try as Nest app sees and controls the device so would assume its seen fine in my network (and yes have checked everything on the same wifi all round) and it adds in the Google connection manager fine. So, whatever happened on the day that prompted the email is surely the key. This was 10th July.

I am truly stuck on what else I can try and its very annoying! If Google has done this on purpose to get rid of old devices then it would be good to know. Not great and pretty annoying as it worked fine but at least it would be an answer...

Thanks, Paul.