You may have noticed there are some new graphs on the right sidebar of this blog. You can now get live updates on my home electricity use and my carbon footprint (well my electricity-related carbon footprint anyway). Things have clearly moved on since I first got my Current Cost device in November and became part of the Act on CO2 campaign. I’ve been steadily reporting back my energy use to the PR company employed to manage the campaign but realise that for the data to have any impact on my behaviour I should be forced to look at the data everyday.

Actually I think I’m losing the plot on the whole saving energy thing and have become way more interested in the data-mashing/amateur electronics end of things. In particular I’ve become interested in getting objects (in my case an energy meter) to blog/tweet on their own. My house needs to tweet to remind me to be a more careful user of energy – that’s where I want to end up.

We’re not quite at the stage of seeing @daveshouse on Twitter yet but we do have nice graphs. These come courtesy of Pachube: “a service that enables you to connect, tag and share real time sensor data from objects, devices, buildings and environments around the world”. Pachube are beta-testing at the moment so you’ll need an invite code to use their service (sign-up details here). On their applications page they have an app to connect the Current Cost meter to your computer. This allows your meter to output information to a feed. I’ve created another feed for my carbon footprint using another Pachube app and finally, the wonderfully titled Pachublogject (which is also still in beta – many thanks for allowing me to test) spat out some code for a widget.

And that’s the widegets you see in the sidebar. I could add another for temperature in my living room but will resist for now. It’s live energy use you are seeing and it changes, according to use, every 15 seconds or so. The carbon footprint bit recalculates based on the previous 24 hours energy use. Where the graph shows a flat line that isn’t always because there’s noone in the house – more likely it’s because the laptop the meter is plugged into is switched off. And that’s where the flaw is in this for me – I don’t have an always-on machine at home that the meter can feed into. So the next thing I need to do probably involves me connecting the meter to an Arduino and then direct to a port on my router. That will involve some programming or something like that – beyond my technical expertise currently although I’m learning stuff pretty rapidly on this project. From there we’re only a short step away from twitter. Bring it on!