Archived Forum

Anybody?  If not I guess I'll try and work through it using the current cost monitor for a data source, for now.   Can always build up an open energy system eventually if I can get the Nest api details ironed out.   

I would be happy to assist with interfacing with emonhub, I do not have a "nest" available for development purposes nor a deep understanding of its functionality but looking at the API docs this morning I would say you are right it should be quite straight forward (alas it would not be the first time I've thought that and been wrong)

There is a similar thread for "Feeding Hive data to emoncms" which I've offered to help with too, and the same concept would work, just the API structure would be different I guess

Have you stumbled across any working examples at all?

 Paul

Excellent, thanks for the offer to help with this. Im going to start workimg with it and may reach out if I get stuck and will attempt to post updates on here as things move along.  

I'm building a small personal website now since Google seems to require that you have a website to register as a developer but I may start there and ask the Dev support team at google if they have a recommended best approach for implementing this.  

I have not seem a clear working example anywhere.  Some people were using an unofficial api and sending data to xively but most of that was before the google acquisition and release of the real api and developer program.  Initial emails with google were positive and they said once registered as a developer for the nest it would be possible to get support from their internal team etc so I figure it makes sense to start there.   

I did take a quick look at registering as a developer, but one of the items in a list of tick boxes to agrre before becoming a registered developer was something like "promise not to develop anything that will effect the call for heat" or something similar which I though was a bit limiting and decided I anted to read more before ageeing, which I haven't managed to do yet. Sounds very Apple'esque rather than a Google'ish type of limitation so maybe it will get lifted, who knows. I will take another look though.

I have started a emonhub modules "sandbox" thread about an easy fit experimental environment you may fancy looking in on.

Paul

Ok thanks.  Essentially it seems they don't want developers doing things that would change how the nest functions with respect to its core features.   So if you wanted to write a client that would call for heat when your client program is triggered by some event, that's probably not going to happen through the official api.  It seems they're fine with writing data objects to the platform if you play it by the book, which is what I'd like to do.   There are apparently already special built in tools and displays in nest for adding energy usage data, eg electricity and gas, and its in google's best interest to have this data anyways so they can better see directly the effects of tweaking nest thermostat behavior etc etc  

I just saw there is development ongoing for an emoncms android app and a nicely written tutorial to boot.   Perhaps the snippets of code required for pulling thermostat data and pushing energy data from and to the nest environment could be incorporated there.   

So many ways one could skin this particular cat and minimizing duplication of effort is always smart.   They (people with real computer science backgrounds) tell me that great coders reuse.

Emoncms already exists and seems like a good place for the energy monitor data to go first if it can be queried by an android app.

Ok, eyes are shot from reading the Nest and android developer documentation, time to sleep and hope some of it soaks in.