I noticed my Nest isn’t updating very frequently in HASS - seems to be long enough that sometimes HASS doesn’t know it went through a full heater off->on->off cycle. Specifically, I want to create an automation rule to turn a ceiling fan on to move air around whenever the Nest’s fan (and thus whenever heat or AC is on) is turned on - but with low polling rates, that is hard.
Best clue I can find is in a nest.py file:
class Nest(object):
def __init__(self, username=None, password=None, cache_ttl=270,
Does this mean that there is a 270 second (4.5 minute) delay between update checks on the Nest? I know there is some rate limiting that Nest enforces for developers - but could this be configured to be lower?
I too am having the same problem with delay in polling. Did you ever discover a fix for this? I have almost the exact same automation I set up but the delay in Nest update causes the same failure you have described.
A quick Google tells me that nest has a max update rate of every 60 seconds to their api and looking at the HA code there is a configurable scan_interval with a default of 60 seconds.
If the platform works like ecobee, it may just not be updating from the thermostat to their server. So polling faster wouldn’t solve anything.
Edit: I remember someone trying to do something similar with ecobee, I think they ended up putting a nodemcu on the fan control line to detect when it was high.
Thanks for the input.
The delay def seems to be between nest servers and HA - The iphone app and nest website seem to keep updated within 1-2 seconds E.g. change target temp on the thermostat and the ios app updates in 2 secs, but looking at HA app on the same iOS devuce I can see that the nest component does not update either instantly, or within 60 seconds for the polling period.
Maybe data is delayed by Nest for external product APIs that HA uses?
I’d love a 60 second polling delay. It has been consistently in the 5-10+ minutes range, typically long enough for HA to not even know the AC or heat kicked on and then back off - just thinks it was off the entire time. Agree with hijinx, the app is updated very quickly; it is HA that is not updating.
You are lucky with 5-10 mins
If you see the graph I posted here, you can see that I didnt get an update from nest for 5.5 hours between 2300 and 0430 (orange plot).
The Nest API can definitely handle a shorter polling interval. I’ve been collecting my Nest data for a about a year with a little PHP script I wrote that polls at 1 min intervals. I’m starting to use HA, but for my use case, this will be a show stopper.
@dcnoren Did you ever play around with the cache_ttl? Did it seem to have any effect?
Seems there was a change that made the Nest component cloud push from Nest, so it’s not even polling now? This is right at the fuzzy limit of my understanding so if anyone else can look at this and confirm I would appreciate it.
Now that I look at the actual events, I see that I’m not missing anything. I’m used to seeing lots of data in between the event state changes. Thanks for the responding to this necrothread.
