Hi, I’ve just noticed that I am unable to send commands via the Nest plug-in successfully, and that the current temperature that’s being reported differs from the Nest-provided web and app interfaces. I don’t have access to my Vera logs from here at the moment, so I’m hoping another Nest plug-in user could check their own functionality and let me know if they see issues, and if so, if I could get Vera logs to help me diagnose it. I am out of position to do this diagnosis myself from here as I don’t have access to my Vera logs. (If there is a Vera Control Ltd support person who could help me with that, I would appreciate it, otherwise it will be difficult for me to make any plugin changes.)
I’m glad it’s still working for some users. I decided to change my password to force a new login, and now it won’t connect again, and I still have no visibility to my own logs to see what’s happening. Either there is an isolated outage, an isolated difference in the web interface, my IP was blacklisted, or Nest has instituted an API threshold that I’ve exceeded. Perhaps there are other possibilities.
If anyone else sees problems with the Nest plugin and can share some (sanitized) logs that show the errors, please share.
Glad it’s working for you, but I’m doubtful that the issue relates to the thermostat connecting to the mothership (nest.com), since I can still see and interact with it fine from the native web interface. It seems to do with the connection between the plug-in to nest.com. I have no signs of connectivity issues at the location where the thermostat and Vera are.
Is there a way that users can make use of Vera’s Account → Tech Support → Remote Access connection to my unit, or is that strictly for Vera support people?
Thanks. I will ask Vera support to get me the logs, but it’s understandable if they won’t do that (privacy, outside of support functions). In the meantime I’ve had to set my user name and password blank in the main plugin device to keep the plugin from repeatedly failing to communicate. Hopefully the logs, if I can get them, will shed some light.
Thanks, if you have continued access to your logs, could you press the Set button next to your user name or password in the main Nest device, and then report what unusual Nest-related log lines you can see for a few minutes thereafter? (Making sure to obscure any user names, passwords or other identifying information that might appear in your log).
Thanks, @egoh. That is normal so far, but some seconds or minutes later it ought to show attempts to login and retain the session information, and then attempt to get status. If you have further log lines, please let me know. Thanks for your help.
It’s interesting that, based on the transport URL nest.com returned, it appears that your and my Veras may be in the same geographical area, but that may be wrong or insignificant. While the login seems to be permitted, it falls apart at some point thereafter. I hope this is an operational issue, not an API change, but I would need more to go on. Thanks very much for your log information. If anything else appears that might be interesting, please pass it on.
Otherwise, blank out your user name or password in the main Nest device to keep the plugin from repeatedly trying and failing.
My polling is set to the default 120 seconds. To my knowledge, there is no published answer to that question yet. I imagine/hope that the forthcoming official API will be explicit in how much API usage is permitted over time.