The downside to the SqueezeBox devices is that the quality comes at a price, one which is impossible to justify at the moment. However, it happened that the following year O2 were having a fire sale of their Joggler device. I snapped one up for the bargain amount of £50 with the intention of using it as a home automation controller.

Well, the automation dream also comes at an even less justifiable cost and so the Joggler has been sitting idle in a drawer waiting for a project to bring it back to life. Thanks to the UKHA mailing list it now has a purpose. My Joggler has been reborn as a budget SqueezePlayer having followed some really easy steps.

With it connected to my surround amp, I can now stream music from my existing SqueezeBox Server and even control it remotely with a web browser. One less bit of idle kit, one new feature, and at £100 less than it would otherwise cost.

The Joggler is a popular device for customising, and there are Ubuntu builds available for it (rather than the onboard O2 OS). If you want to play with one, they are no longer available for sale from O2, so you will need to look on eBay or similar.

Installation

The Interface

Project Planning

Scheduling

Hopefuly at some point I’ll find the time to update the Idea Cog website with these videos.

Foresight is a client-server based solution for agencies and any other businesses that have very variable needs for their individual projects. It provides tools for project management, document versioning, live recorded discussions and most importantly of all – advanced adaptive scheduling!

There are so many features in fact that it’s going to take me a while to document them all fully. At the moment, there’s an initial feature list as well as a ‘Quick Start’ video showing how to install and configure Foresight.

If you want to start using Foresight, you can get your hands on a free 5 resource license which you can use with the freely available downloads. Once you’ve fallen in love with my first commercial offering, you can purchase more licenses as you need.

So, please give it a whirl and leave your feedback below.

I am forming a new business, Idea Cog, which will have Foresight as the first of possibly many software products as it’s portfolio. I’ve just completed the single-page teaser site which is now live at ideacog.co.uk.

If you’re interested in learning more, please sign up to the newsletter via the form on the Idea Cog homepage.

The CurrentCost power monitor has become very popular amongst amateur home automators and those technically-savvy who want to keep an eye on how much electricity they are using (and ultimately how much they are going to have to pay in bills). A couple of months ago I purchased the CurrentCost device and a USB cable to connect it to a computer from eBay. Having just seen their eBay store, it looks like they’ve got a fantastic new model on the way, but this article is about the older version.

By itself the device works very well, providing an at-a-glance view of current power use and a history over several periods of time. There is a simple bar chart showing the relative amounts of power used in the previous day, split into day time, evening and night. However if you want a clearer understanding of how power use changes day-to-day or even over a decade, connecting the device to a computer will provide the ability to store every reading in a database and/or produce live graphs of usage.

Several people have written articles on how to do the logging, each using a slightly different method (and language) to do so. Most of them are for linux though, but any programmer should be able to port the ideas across to a different platform such as Windows or Mac OS. For my implementation, I followed this guide on jibble.org.

This is what my perl script turned out like:

#!/usr/bin/perl -w
# Reads data from a Current Cost device via serial port.

use strict;
use Device::SerialPort qw(  ARAM :STAT 0.07 );

my $PORT = "/dev/ttyUSB1";
my $ob = Device::SerialPort->new($PORT);

$ob->baudrate(9600);
$ob->write_settings;

open(SERIAL, "+>$PORT");
while (my $line = <SERIAL>) {
    if ($line =~ m!<ch1><watts>0*(\d+)</watts></ch1>.*<tmpr>([\d.]+)</tmpr>!) {
        my $watts = $1;
        my $temp = $2;
        print `/usr/bin/rrdtool update /var/scripts/currentcost/powertemp.rrd N:$watts:$temp`
    }
}

Note that because I’m connecting via a USB port, the serial port name is different. The baud is also 9600 rather than 2800. I have set this script to run at startup (detatched from the console) so that it is always running in the background.

I have also produced another simple script, which is run every minute as a cron job.  The script generates the graphs from the data stored in the RRD file, and uploads them to my web server via SSH.

#!/bin/sh

rrdtool graph /var/scripts/currentcost/power-10min.png --start end-10m --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null
rrdtool graph /var/scripts/currentcost/power-60min.png --start end-60m --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null
rrdtool graph /var/scripts/currentcost/power-day.png --start end-24h --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null
rrdtool graph /var/scripts/currentcost/power-week.png --start end-1weeks --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null
rrdtool graph /var/scripts/currentcost/power-month.png --start end-1months --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null
rrdtool graph /var/scripts/currentcost/power-year.png --start end-1years --width 323 --end now --slope-mode --no-legend --vertical-label Watts --lower-limit 0 --alt-autoscale-max DEF:Power=/var/scripts/currentcost/powertemp.rrd:Power:AVERAGE LINE1:Power#0000FF:"Average" > /dev/null

#Copy locally
cp /var/scripts/currentcost/*.png /var/www/currentcost/

#Upload to mars
/usr/bin/scp /var/scripts/currentcost/*.png root@192.168.2.3:/var/www/vhosts/currentcost.elemental.killswtch.net

You can see the result on the Power page of this site. The graphs at the moment are fairly basic. The Jibble article includes some extra data in the graphs, which I will probably add at some point. For the moment though it does the job very well.

The CC device is located downstairs, in the living room. Thanks to the serial output connector being an RJ45 socket, it was very easy to plug it into the exising CAT5 network (which I’m very glad I did) and run the signal to the cabinet in my room where it is then broken out through the RJ45 patch panel, through the RS232/USB cable and into the fileserver boron, which hosts the scripts.

Over a year after it began, the whole-house-audio project is complete. 4 rooms around the house can now be filled with the sound of any of (currently) 4 audio devices thanks to a mixture of hardware and software.

The project had a slightly rocky start, with a prototype not functioning at all and partly destroyed amplifier (which was thankfully fixable by replacing a couple of components). A software alternative was considered at one point, to avoid too much expensive hardware. The hardware solution proved to be less complex and more likely to work.

The living room, dining room, kitchen and master bedroom are host to a pair of speakers each, connected to matching 240W rack-mounted amplifiers housed in my home-made full-height 19″ rack cabinet. The cables that carry the audio signals to the speakers were installed along with 24 runs of CAT5 before moving into the house.

The audio is routed to the amplifiers via an 8×8 VAMS-0808 AV matrix switcher, which allows the 8 outputs to take their inputs from any of the 8 available sources. Only 4 of each are currently in use, so there’s plenty of room for expansion.

4 audio sources are connected via simple custom-altered CAT5 cables, which simply transmit line-level signals over the existing twisted pair infrastructure installed in the house. These sources are currently the DAB radio in the kitchen, the TV in the living room, the computer in the dining room (for playing CDs) and a second DAB radio in the master bedroom.

I’ve written the software to control it all using .Net (C# of course), running on mono on linux. There are four components to this:

1. To control the matrix switcher, I have written a library which communicates with the VAMS-0808 via an RS232 serial connection. The software can perform any of the operations that can be performed via the front panel of the device, apart from switching power on and off.
2. The amplifiers are connected to an APC AP9212 MasterSwitch Power Distribution Unit which was bought with this project in mind. Controlling this is slightly less straightforward and not quite as elegant. The library that I’ve written for this communicates through the telnet interface of the MasterSwitch to turn devices on and off.
3. Combining these two libraries is a simple web server which presents an equally simple XML-based web service. The service allows room inputs to be changed and switches the amplifiers on and off as necessary. This runs on a low-power disk-less computer running Ubuntu, hidden within the rack cabinet.
4. A touchscreen web interface acts as a front-end to the entire system. The simple menu system uses iUi for a clean touchscreen-friendly design. As with the web server this runs on a low-power machine, although this one has a small hard disk and runs Windows due to technical issues with the touchscreen.

There is currently just the one controller front-end, located in the dining room. To listen to the kitchen radio, for example, all that is necessary is to select the ‘Kitchen DAB Radio’ option from the main menu, then select which of the 4 rooms to play it through – or all of them if you are going to be wondering around most of the house.

Future extensions

Thanks to building the web interface with iUi, the system is compatible with the iPod Touch and iPhone, so they can instantly act as frontends for audio control. A second fixed controller may be added in the master bedroom in time, if there’s enough money available. Each front-end costs about £200 in hardware, depending on what bargains can be found on eBay.

The matrix switcher supports both audio and video. Only the audio channels are used at the moment, so there is the very real possibility of using the remaining 4 output zones to connect to TVs around the house and adding some AV sources. This way it’s instantly converted into a whole-house-AV system. The video signals can be carried over the twisted pair CAT5 cables like the audio, but will require a little more hardware to preserve quality. This hardware is relatively expensive, although savings can be made by building the equivalents by hand. Following the tradition of this project, that’s probably what I’ll do. I have done it before while I was at university and it works beautifully.

The audio system that I’m building requires 2 low-power computers: 1 for the touchscreen controller (not using an iPod Touch for the moment) and 1 to act as a webserver and serial-console server.

Once again eBay has come to the rescue, and by searching for ‘geode’ – a low-power processor for Thin Clients & Small Form Factor (SFF) PCs – I found the 2 machines that I needed. These are the specs:

magnesium (the black one)

• 800 MHz Geode
• 256 MB RAM
• 6 GB CF drive
• Onboard graphics, audio, serial, parallel, USB & 10/100 ethernet

£70 + P&P

potassium (the grey one)

• 300 MHz Geode
• 256 MB RAM
• 6 GB 2.5″ IDE drive
• Onboard graphics, audio, serial x2, parallel, USB & 10/100 ethernet

£35 + P&P

Magnesium is used as the client machine, and potassium runs a custom-made webserver and the control software for the VAMS-0808 Matrix Switcher.

Both came pre-installed with Puppy Linux, a lightweight distribution designed for low-power machines such as these. It runs surprisingly quickly, but to make it easier for me to maintain I decided to install Ubuntu.

On such slow computers it took many hours to get Ubuntu installed on magnesium alone. I initially installed to the CF drive that came with the machine. However I found it to be quite slow, so I followed a guide for running Ubuntu via network boot and removed the CF disk. I did the same for potassium. Both booted off of the fileserver, boron.

Unfortunately during installation, I found that the slower of the machines has a tendancy to overheat causing the machine to hang. To get Ubuntu installed I had to remove the case. This has now been rectified by installing a blower to get at least some air circulating. This is the only fan in either of the machines. Magnesium gets quite hot but has never crashed because of it. It also sits in a cooler environment, and is much better engineered.

Sadly I’ve been forced to install Windows XP on magnesium purely because I couldn’t get the touchscreen to work under linux despite spending more than a day trying to. While it was detected, and it detected touches, the calibration was completely off and there was no way to configure it. Rather than waste any more time I decided to switch to Windows and everything has worked beautifuly since then. To accomplish this I’ve had to reinstall the CF disk since as far as I know XP Pro can’t do diskless booting.

Shots of these computers in use and more information on their roles to come soon.

Yesterday I completed and successfully tested the control software for the audio system. The software works with the matrix switcher and the APC MasterSwitch remote control PDU to allow the audio output devices around the house (TV, radio, CD player etc.) to route their sound to any of the 4 audio zones.

I’m now waiting on some more purchases from eBay to arrive before I can finish the system off. On the way is a small touch-screen monitor and a low-power mini ITX computer to connect it to. This will function as the controller and will probably sit in the dining room at the centre of the house. I’ve not gone for an iPod just yet, since a small mobile device has the possibility of getting lost or damaged more readily than a fixed controller. I’m looking out for a cheap 2nd hand one on eBay though.

Although I had got the software working yesterday, I foolishly installed some updates for Ubuntu and now the serial ports have disappeared again. Rather than battle to get the ports to show up and behave I’ve gone a little more eBay crazy and bought a second thin-client-like low power PC which will run the matrix control software and possibly the web server for the front-end control interface.

The other remaining tasks include creating some more cables and positioning and attaching the speakers for zone 4, the master bedroom.

Full details of the setup, with a video, will hopefully be posted in the next few weeks.

Thanks to the chip manufacturer of the cheap serial port card, I’ve managed to get some extra serial ports working. If you can’t figure out how to get additional serial ports working, I recommend this guide [ZIP, 792KB] available from the Moschip driver download page. It should be valid for most models of serial cards, and explains how to add more than the standard 4 ports that most linux installs have.

Now that this problem is out of the way I can continue with writing the remote control software for the audio system.