I was testing a configuration where I have Indigo controlling a radiant heater by having it turned on when Indigo senses that my Nest thermostat is calling for heat and then turning off when it is no longer calling for heat.
Recently, I noticed the radiant heat was on and it was making that part of the house uncomfortably warm. When I examined the situation, I found that Indigo was not correctly tracking the state of my Nest Thermostat -- Indigo said the thermostat was calling for heat and the temp was 67; looking at the actual Nest device on the wall said heat was off and temp was 71. I selected the Nest thermostat in Indigo and clicked the "Send status request" button and it immediately seemed to start tracking again.
I'm not sure how long the "outage" lasted, but I suspect multiple hours. Actually grep'ing indigo logs indicates there were no updates in the last two days! While poking at the logs, I noticed there is what I guess is the Nest Home-specific log "NESTHomeErrors.log", but it simply says the log was reset a few minutes ago, so if it ever had any info about the problem, it seems to be lost now.
I'm wondering if anyone else has seen this problem - specifically Indigo not updating the state of Nest Home devices (for long periods)?
I had the feeling Nest Home has been working well for me (for a few years now), but up until recently, I mostly used it for adjusting set points, ether manually or via schedules/triggers. Thus, I wasn't really paying attention to whether Indigo was tracking Nest status accurately, so perhaps I've been having this problem all along and just not really noticing it.
Anyone have experience with this? Might there be a condition I can trigger on to detect a problem (such as "last update time" is more than 5 minutes ago or something)? If so, I would try to have NestHome reconnect or resync or whatever, and if it still doesn't update, then send me an error message.