I really don't know what Nest is doing...
My guess they have the API shutdown to any new connections....
Pretty sure the entire Works with Nest platform is down for good at this point.
how do we use Set Nest Eta? what does it do?
As near as I can tell nest has shut this part down, ie in my last test (few months ago), it does not work.
It use to be you set a time (in future) you plan to arrive, and it would use this data to decide when to start adjusting temperatures.
1 Like
Hello, I'm an old time NST Manager user is ST. I've got my Nest devices, including a thermostat, working fine in HE with Nest Integration. I want to move back to NST Manager, but I can't find my HE Nest ClientID and Secret. I can find them in the ST app, but of course, they are not valid. How can I get back my HE IDs to introduce them in NST Manager?
You can't, if you have a already working instance somewhere don't touch it. You can't renew anything any more until nest sort their stuff out. Until then only existing set-ups will work.
If that's wrong in anyway then someone else will be along soon to correct me, I'm sure.
I'm not sure of what I'm going to say, but I already have my HE linked with Nest and all my devices are visible to HE. All I need to do is to get my IDs, as I can do in ST, and I think that using them in NST Manager doen't have to renew anything, or make any new connections between them. It's just to use my current HE link with Nest, but with NST Manager instead of Nest Integration, or why not, both at the same time. Doesn't it works that way?
so you have the build it HE integration and the devices respond?
i don't believe if you loaded up NST manager you would be able to sign in, give i ago just don't delete you HE integration. I would disable the HE version if you manage to get NST manager to work.
Right, I did the integration more or less one year ago, and it has been working until today.
No, that's the problem. I can't sign in into NST Manager, but I think it's just because I don't know my Nest ClientID and Secret. I'm sure that knowing it, I would be able to do it. As I mentioned, in the ST environment I know those IDs, so the question was, where can I find those IDs in HE?
Of course I would not delete Nest Integration from HE, I will just disable it, as you suggest, but just when I manage to get NST Manager to work.
Can you use the values from SmartThings?
No you can't sign in because it would be a "new integration to nest" this has nothing to do with your client ID and secret that's like the middle man that nest signed off to allow X amount of integrations. Basically if your not already signed in you can't re sign in. If you upgrade your account to Google from nest it will sign you out and break the connection and then your also stuffed.
So basically if it's working somewhere IE ST leave it and use Hub connect to share the devices to HE (I don't even think you need the physical hub).
I can use them in ST, but not in HE.
I will try that option. I'm already using Hub connect between my hubs, so that's the other option, thank you.
Anyway, I'm not sure that you're right when you say it would be a "new integration to nest". I think it doesn't work that way. My HE hub is signed with Nest, not the Nest Integration App, so if I'm right, any app in my HE hub should be able to use that connection. I think that knowing the Client and Secret IDs used to sign in with my HE hub (in this case with the Nest Integration App), should be enough to sign in from the same HE hub with any App. But it's just a feeling. The only thing that makes me think that way is that ST shows me the Client and Secret IDs used to sign in with my ST hub.
I definitely know this isn't correct.
that's because originally when the developers created there account with nest it gave them one (essentially a key to nest API) but this was limited to X amounts of accounts. once this ran out they needed to find a way for others to use it. So they gave the option for each person to go to nest create their own developer key then put it in their own app. This key is NOT linked to your nest account its linked to the developer account you set up. Multiple people could use this key should you want to share it and sign in to their own account.
In HE im assuming this never needed to happen as there was not enough people using it at the time to go over the keys allowance. @nh.schottfam or @tonesto7 should be able to confirm either way.
This is correct for NST manager on HE.
I think Nest does not allow any new oauth handshakes to occur (to establish the oauth relationship).
Ok, this sounds crystal clear now. So while Google keeps it closed, unfortunatelly there's nothing we can do. Thank you all for letting me learn a little more.
Bad news. I was lucky and my Nest works still with SmartThings. So I'm looking at MQTT to act as a bridge to get the info from one to the other.
Perhaps you can try HubConnect.
Seeing as this has gone dark, and I’m sure there’s still a few people with nest products. I found this while searching for alternative ways to connect my next x Yale lock.
I haven’t installed it because Im not a HomeKit it advertises the ability to integrate the native nest app even if you’ve migrated to a google account.
Would it be possible to integrate this with nst manager?
Saw an update from roughtly a week ago.
nstAutomations gives me an error tho' when using schedules:
groovy.lang.MissingPropertyException: No such property: key for class: java.lang.String on line 5273 (schMotModePage)
Went back to the previous version of nstAutomations and the automations could be accessed (and altered) again and the error is gone.
