That's interesting. The only weakness of the message routing architecture that I can see is that it is hard to avoid a single point of failure.
To be honest, when I looked at LinuxMCE, the biggest quandry for me was "what do I use as the actual control bus/network?" Here are my conclusions:
Z-wave is great for retro-fit, and the mesh capabilities give it a fighting chance in real life situations (14" solid stone internal walls, that sort of thing). But it is relatively expensive to equip a whole house, and I worry that WiFi, Z-Wave, Bluetooth, Microwave ovens and so on all sharing the same space is likely to cause problems.
X10 is too slow for a whole house implementation these days. I'm surprised someone hasn't updated it with the HomePlug Ethernet-over-mains standard - I looked into it, and all the parts are there. Imagine just reaching out over the network to each auto-configured light fitting directly!
Knx/EIB is a powerful standard, but look at the price of a dimmer or a light switch. I didn't look any deeper for that reason.
Clipsal/CBus has most of the characteristics of Knx/EIB (including the price!). Nice kit, though.
DMX512 looks good as a lighting standard (fast, easy to run cables, low cost per lamp), but the whole house would depend on one PC if I used a USB or serial DMX controller on the Core. I could use Media Directors to spread the control a bit, but the DCErouter is still in the path to every lighting change.
1-Wire is capable and cheap, but sensors and controls are limited
I had been working with WebBrick Systems to try and build solution for my house, and they got a lot of things right before their unfortunate demise, but the engineer in me could see something better and more capable. That led me onto the Barionet, and MythTV led me onto LinuxMCE. I believe I have the skills to put the two together - let's see what comes out!
I just thought I'd explain this in case anyone is coming to the conclusion I'm just plain crazy (maybe it's too late