So the state is what the thermostat is telling the HVAC system to do at the current time and the user selected mode (heat, cool, heat/cool ) becomes a property of the object.
Looks like the Nest plugin is creating a new connection to the Nest cloud without disconnecting the old connection. If the plugin is left running for an extended time, I get pages and pages of connections that can be seen in TCPView
I just got a new NEST thermostat and I'm trying to get the NEST plugin to work.
I have it installed, but I'm only getting to this point
Code: Select all
No pin provided. Please visit https://home.nest.com/login/oauth2?client_id=ff5f73fb-2fd9-472f-ba3d-73cb236a1808&state=STATE to get a pin code. Update PIN property on Nest Plugin object and run method Get Access Token.
I got most of this figured out.
For starters, the default version of NewtonSoft.JSON that is used is version 18.104.22.168
The Nest plugin requires version 22.214.171.124 + to work., So you need to upgrade or copy the version from the plugin to your main OSA folder.
Secondly, @Fivehellions put some "Hard-Coded" information in the plugin.
It is apparent that he is no longer keeping up with his plugins, nor his account on the Nest developers site.
So, Once I signed up for my own Nest Developer account and created my own OAuth2 Nest Client, I was able to get the plugin back up and running!!
This plugin has already been upgraded for 4.9. So I think I might work on an update for it, and make it so it is not dependent on any other users information.