Hi Andy,

Thanks for the hint. I'm definitely always open for challenges. But building my own home automaton is already the 'challenge of all challenges' for me, since it invokes not only writing a little (maybe much???) software, but also developing the hardware, drawing the schematics, drawing the PCB's for that and last but not least, foresee the necessary hardware (wires) in our new house!

That, and the fact that I'm doing it whole on my own (not to forget the help I get from you guys!), makes it a 'double day task' (next to my normal profession).

The fact that I'm using I2c, is simply because I'm using it for my daily tasks. I'm part of a development team at Philips Brugge, Belgium, that makes HD HighEnd LCD televisions worldwide, and the protocol used is still mainly I2c (although the more empowered versions of it, meaning higher speeds).

Of course, CAN says something to me too. I discussed already about that protocol with one of my colleagues who, just like you, loves it very much.

But I don't know enough yet of the protocol, so I won't take that extra burden on my shoulders. In this case, not the sky, but my capabilities are the limit!!! ;-)

And who knows, I might maybe rewrite my software to use CAN for this in the future. I've forseen everywhere UTP Cat5E cable for my communication lines, so with the necessary software (and hardware?) adaptations, it might be a target for the future.

Thanks anyhow for the suggestion,

Best rgds,

Geert