Google gives up Power Meter, seems so – Google PowerMeter API deprecated…
The Google Power Meter API has been officially deprecated as of May 26, 2011 to reflect that it’s no longer undergoing active development and experimentation, which is the hallmark of APIs in the Code Labs program. However, we have no current plans to remove functionality for existing users.
Google stopped updating their Power meter blog last year (Aug 31, 2010). For the power geeks, you can read our long history with Google’s power metering efforts / competition here. We think it’s an excellent case study for someone out there and a cautionary tale of what happens when Google gets in your market.
Here’s what we predicted July of last year…
At this point, and just our opinion, we’re not really sure PowerMeter is a serious effort at Google and if it will continue, the manager (Ed Lu) recently left, the forums are pretty low volume on the Google site and if you review the Tweet-a-Watt time line it’s not that encouraging for folks wanting to use Google PowerMeter. The folks from Google have posted here before and we’re hoping they re-consider how they’re deploying PowerMeters and what the goal of the project really is…
We got our Tweet-a-watt to work with the Google Power meter API for kicks despite Google ignoring the requests for access from the open source / open hardware community, Google chose only to work with commercial partners and not the thousands of Tweet-a-watt makers out there. It was mostly a war of the press releases as Google didn’t really do much in this space, only making sure other companies in the power metering arena stayed scared of Google, it worked. Google does a lot of cool things, but sometimes they get “grabby” in markets, freak people out, buy a bunch of stuff/people and then just kill off stuff it seems. Happens to lots of companies, Google is working on self-driving cars now.
All that said, we’re excited by the recent developments with Anrdroid + Arduino, mostly because it’s all OSHW and it will continue no matter who or what happens. If you want to build open source power meters, we’ve got you covered, always 🙂
Tweet-a-Watt is a DIY wireless power monitoring system. The project uses an ‘off the shelf’ power monitor called the Kill-a-Watt and adds wireless reporting. Each plug transmits the power usage at that outlet to a central computer receiver. The receiver can then log, graph and report the data. This pack contains nearly everything* necessary to build a single outlet monitor and receiver. To monitor additional outlets, you will need an add-on transmitter pack. One outlet can monitor up to 1500 Watts.
The starter pack contains:
- 2 XBee modules (one for receiver, one for transmitter)
- 2 XBee adapter kits (ditto)
- 1 USB FTDI cable (for updating, configuring and receiving data from XBee)
- 1 bag of parts including 10,000uF capacitor, 220uF capacitor, 2 1% 10K resistors, 2 1% 4.7K resistors, 5mm green LED, 6″ rainbow ribbon cable, and 2 pieces of 1/8″ and 1/16″ heatshrink
I would recommend maybe having a look at smartenergygroups.com
The site has some API documentation available and a keen hacker might be able to port tweet-a-watt over to it.
Totaly agree with previous post , f Google , go smart energy ,easy and hackable
Thanks Luke and Hennie!
We love arduino at Smart Energy Groups, and welcome anyone who would like to point their gadgets at SEG and join us!
We have a whole bunch of open source arduino based things, OpenWRT and a dead easy api.
Drop by and have a look, and if you need to know more, let me know at sam dot sabey at smartenergygroups.com!
Sam,
@samotage
Darn it! I ordered the blueline energy sensor/gateway last week (still have not received it yet,btw), and now this?!
Although fortunately, I think Microsoft Hohm will work with it. Until of course Microsoft pulls the plug on that one too.
The wattvision team is excited to work with the tweet-a-watt. We have a pretty simple API.