Nest Thermostat "State" not updating?

I have set up the newly available Nest integration, which for the most part appears to be working. I have encountered one problem though - The “state” reported by Nest in smartthings never changes from “Idle”. I would like to create an automation that turns on an auxiliary fan when the heat is running in the evening. I’ve used a similar automation with the old NST Manager app and WebCore, which required a legacy Nest account. I was excited to finally update my Nest account and bring this automation into the official app, but now my only use for the Nest automation isn’t working! Has anyone else experienced the same problem, and have you found a fix?

3 Likes

I don’t have an answer for you but I’m having the same issue. Hopefully someone can explain why the state stays idle

1 Like

I don’t have a solution, but I have the same issue. Any support to solve it would be appreciated.

I am having the same issue. The “state” of nest is one of the most useful reasons to have a Nest thermostat integrated into SmartThings. My “state” is always idle. I want my ceiling fans to circulate the warm air while the heat is on. I have high ceilings and the warm air tends to stay near the ceiling.

I cannot express how disappointed I am that the ‘state’ is not updating. These thermostats have been the biggest waste of money. They are dumb…not smart. I’ve been hosed on this trigger every since Stringify went down.

Did any of you raise a support case for this? Im waiting feedback from support but you would hope this is a relatively easy fix…

Hi, there is a custom integration which takes advantage of the custom capabilities (and less issues):

Refer to

Regards.

I’ll take a look in the morning, if you can satisfy my use case I’m more than happy to contribute.

More features, more automation variables available, compatible with all dashboards (ActionTile, Sharptools) and no throttling…

What I am trying to do is get the state of the thermostat so I can hook up an additional device to turn on/ and off as if it were hooked into the thermostat itself.

If I have read your documentation correct the minimum poll interval is 1 Minute - is that correct?

As I will have only 1 Nest device is it possible to reduce this? I assume this is because there is a Limit on API calls?

Thanks

Hi, no it’s not possible to reduce the polling interval due to scheduling issue. This is a cloud-to-cloud integration, and a 1-min. interval is pretty good under SmartThings (few (local) z-wave and zigbee devices can have a 1-min polling interval btw)…

And, there is a smartapp called tstatStateTriggerHA for this use case:

Regards.

I’m not we’ll versed enough in these processes. No idea how to do that.

Thanks,

Matt

Ontheslopes Mark Freelance
March 6

I’ll take a look in the morning, if you can satisfy my use case I’m more than happy to contribute.