I'm not sure what else you want from me. The logs you are looking for do not exist.
If the Thermostat is not linked to the 'Nest Structure' as you say, well, I have no idea how to do that as it clearly shows up in the Nest app, the Google Home app, and on the thermostat itself it shows it's connected to the Nest app.
So again, I'm not sure what to do at this point. It's strange that the same connection module works for everything else except for the thermostat. I would make an educated guess that the thermostat app code is the problem.
All I'm telling you is that your thermostat is not linked properly to the Nest structure based on the logs you posted.
You're saying that you have 3 Sensors and 4 Protects, all I see according to your post is 4 Protects and 2 sensors. So, clearly some log entries are missing.
IF you want me to help you, you need to send me the whole logs.
FYI, my code won't be able to
recognize your tstat and parse its attributes if there is no 'device.*' thermostat object linked to your Nest structure (contrary to many other Nest users including myself who have the thermostat linked correctly with a 'device.' entry).
There may be a thermostat, but it's not visible in the Nest structure to be parsed by my code. I need to be able to parse the whole thermostat object with all its attributes. I don't see any thermostat attributes in your logs such as 'can_heat', 'can_cold', 'target_temperature_high', 'target_temperature_low', etc..
Regards.
P.S. It happens sometimes that the Nest thermostat is not linked properly initially, and then by following the instructions below, and by resetting it with the WWN option, it appears correctly after. You have to add it to the Nest app after the reset. I understand that you may lose some of your custom settings, but it's the only workaround to make it appear in the Nest structure.
When you say it's "not linked properly" what exactly does that mean? If it says it's connected and I can remotely manage it from the Nest app, the Google Home app, and everything else can see it - doesn't that mean the app code here is at fault?
If there is a proper way and a non-proper way to link it, can you explain each to me?
Of course it doesn't show all the protects, I accidentally put the log in there because it mentioned the thermostat, but I didn't post it for us to debate or talk about the protects as they work fine. I purposefully excluded logs that had nothing to do with the thermostat.
I spent many hours looking through logs to find everything that would be related to the thermostat. There's not much because as you said, the app code is not seeing it, but it's there.
As far as 'custom settings', I don't really care about that as I've spent the last few days deleting it from the account. fully wiping the thermostat and connecting it back. Clearly it seems that Google no longer handles the thermostat's the way you think they do. It is possible Google changed something with new enrollments as I've tried everything you stated there and it's still not showing up in the structure array.
There are also 3 nest thermostat sensors that route through the thermostat and even they show up, just not the thermostat itself.
Ok after some research, it appears your code is using WWN to pull it's information.
Unfortunately, WWN has been deprecated. Even the original Nest app dropped WWN support and removed it as an option from the app.
Meaning even if you reset WWN on the thermostat (which I did already seven times), it will always relink via the Nest app but not via WWN anymore.
I'm not sure if I mentioned this previously, but I migrated my account from Nest to Google a few years ago.
Mentioned: "You may be able to reset your thermostat’s Works with Nest connection. This option is available for Nest thermostats in the US and Canada, and if you haven’t migrated to a Google Account."
My account had been migrated to Google for 3 years but my thermostat works perfectly fine with this integration. I set this integration up over the summer and had worked flawless since then. I only have a thermostat and 3 temp sensors.
Weird because I just talked to a Google engineer who specifically told me that the WWN server is entirely shut down and the Nest app which is in the AppStore on both iPhone and Android no longer use the old server names. Everything uses Google API or Google URI. No more WWN, it's been shut down since August 2021.
I can guarantee you that if you remove your thermostat, you will not be able to add it back in a way that this add-on app to Hubitat will work.
So, my code works for old Nest thermostats, maybe not the most recent ones with the latest firmware (up to about a month ago it was still working). You can imagine that I don't test my code
for every new batch of Nest thermostats (HW/firmware) that is released on the market...
As per another Nest user who just responded to your posts:
P. S. I do provide some support via email, and you don't always see the end results in the forum as most users don't post their logs for data confidentiality reasons.
With the announcement from Google that they are fully shutting down Works with Nest on Sept 30th, does this include logging in with our Nest account for your integration app? Just checking if I need to finally switch my Nest account to Google? Or is this only 3rd party integrations?
Hi @3rdStng, yes it looks like my integration will no longer work end of September.
What's annoying is that there is a lot retired Nest hardware as well including Nest Secure and Nest cams... I was quite happy with my Nest cams and I consider that's really planned obsolescence from Google again.
Oh. The entire integration will no longer work? I was thinking just the Nest account would stop. Are you saying the Google account integration will stop too?
My plan as well. But I'm not sure if this integration will completely go away. As I'm reading the FAQ's, the first step is to migrate your Nest account to a Google Home account. And seeing as MyNext Manager supports Google Accounts, I would tend to think it will still work. But I'm not the developer and if it still relies on the Nest API's, regardless of the account used for authentication, then I could see how it would go away.
I really hope that some work around or solution is found. I've loved this app and switching out 2 thermostats and 10 protects would be costly.
@yracine66, Can you clarify or educated guess whether your integrations will continue to work with thermostats if we have already migrated from Nest to Google account?
I have recently acquired some Keen smart vents which need some smart control over them. I’ve gotten rid of my Nest sensors, use a whole bunch of Zooz, Sonoff, and Aqara sensors around the house, and really only use the Nest thermostat to be controlled by Thermostat Controller and Thermostat Scheduler. Will the necessary apps you provide continue to work? Which apps package do you suggest?
