Page 2 of 4

Re: Nest Thermostat Driver

Posted: Mon Dec 09, 2013 2:56 pm
by erikhimber
Dave,

Maybe it's just me, but the a majority of the variables are not updating.

Mode seems to be the only one that is accurate.

Am i missing something ???

Re: Nest Thermostat Driver

Posted: Mon Dec 09, 2013 6:15 pm
by CinemarDave
Nest changed their home portal web site and for all intents and purposes the Nest driver is not working. We're waiting until January when Nest releases their public api and then the driver will be updated.

Re: Nest Thermostat Driver

Posted: Mon Dec 09, 2013 6:34 pm
by erikhimber
That explains alot.

Wonder why the mode would still update ???

Re: Nest Thermostat Driver

Posted: Mon Jan 06, 2014 10:27 am
by erikhimber
Hi Dave,

Any word from Nest on when they will release the api ????

Would like to make this work with ML.

Re: Nest Thermostat Driver

Posted: Mon Jan 06, 2014 1:34 pm
by CinemarDave
Still waiting for Nest to release their API. I have signed up to be notified. Perhaps they will release it after CES?

Re: Nest Thermostat Driver

Posted: Mon Jan 13, 2014 8:23 pm
by Oronomus
World domination tour continues:

"Google's reach expands into your home more via $3.2 billion Nest acquisition"

http://www.zdnet.com/googles-reach-expa ... 000025109/

Re: Nest Thermostat Driver

Posted: Mon Jan 13, 2014 9:33 pm
by rileydog
Kind-of glad I didn't go with Nest - Google bought SageTV in 2010 and shut them down - I still use SageTV for PVR and love it but you can't buy it (except used on ebay)...

Re: Nest Thermostat Driver

Posted: Tue Jan 14, 2014 8:01 am
by Oronomus
Nest’s Tony Fadell on Why He Sold to Google: “Best of Both Worlds”

http://recode.net/2014/01/13/nest-tony- ... th-worlds/

"What about the privacy issues related to Google?"

There’s perception and there’s reality, and the reality of the situation is that the Nest data will stay with Nest. Our SLA will not change, our Terms of Service will not change. Nest data will be used to improve Nest data, that’s all.

Re: Nest Thermostat Driver

Posted: Wed Jan 15, 2014 9:55 pm
by ronsatter
Hmmm ... won't be long before the unsolicited email offers for new HVAC systems start pouring in. [-X

Ron

Re: Nest Thermostat Driver

Posted: Wed Jan 15, 2014 11:32 pm
by DaveB
....Not only that....Google will now know when you leave and arrive; when you sleep; How much energy you use; How many times you walk past your thermostat and probably many things I am not thinking of. It will get interesting now that they own that technology; and who knows what technology was in the pipeline that they also assumed.

Re: Nest Thermostat Driver

Posted: Sat Jan 25, 2014 9:54 am
by rondepping
Any word on the nest driver?

Re: Nest Thermostat Driver

Posted: Sat Jan 25, 2014 11:26 am
by CinemarDave
Nest has a developer page where you can sign up to be notified when they release the protocol. I've signed up 3 times so far and never once have I heard any response from them. Chances that we'll every hear from them are probably slimmer now that Google corporate is in the mix. It is also interesting to note that on that developer page they mention that their api will be able to give you "near real-time" control of the thermostat. I read that as meaning that any control we will have will be by talking to Nest servers in the cloud who will in then talk to the thermostat. They will not allow direct communication with the thermostat. Speculation, we won't really know until the protocol is available.

Re: Nest Thermostat Driver

Posted: Tue Jun 24, 2014 2:18 am
by greyt
Looks like they have finally released the API. Fingers crossed Dave is sitting with his feet up waiting for some work to come in :-)

Re: Nest Thermostat Driver

Posted: Tue Jun 24, 2014 8:25 am
by shakey
I like Dave have signed up a few times for my work I do on RTI drivers, I also have received the black hole treatment and have nothing in my inbox from them. Hopefully something will change.

Edit- They sent me an email today.

Re: Nest Thermostat Driver

Posted: Tue Jun 24, 2014 11:37 am
by CinemarDave
Yes, the Nest API was made public to anyone who wants to access the Nest devices on the 23rd of June. I, and anyone who signs up, gets full access to the API. No more begging. In order to write an application for Nest you must have access to a Nest thermostat or smoke detector. Makes sense but since I do not own Nest products I'll need to test against someones thermostat. Also, the API does not talk directly to the Nest devices. Instead it makes calls to the Nest servers in the cloud. There is an option in the API to subscribe to events to get what Google calls "near real-time" updates without having to poll. This is a nice feature.

Now for the downsides. The API is a JavaScript / Java API. They expect everyone to be developing applications for phones and tablets I guess. So this adds a little more complexity into the mix. As time allows I will be working on the Nest driver.