Off-The-Shelf Device Control

I had this great idea for cheap robotics. Much of open source code is shared. Why can't we just reuse devices that others make? I notice that my idea for simple control of devices align with three of Eric S. Raymond's rules.

Rule of Modularity
Most of the hacking that I see occurs inside the device. Though it is sometimes necessary to enhance a devices, inside hacking does little to help. Let the device do what it was created for. Adding to the device also complicates it.

Rule of Composition
I am not sure, but I think companies just don't like playing nice with each other. Why? Sure, they can get a bit more business by locking-in people to their products, but what about the people heading the Returns desk? They take your money. Basically, my idea would add event pipes to devices. Not necessarily for data. Others already have systems for data transfer. How about control transfer? One device would control another.

Rule of Simplicity
To trigger a switch you just have to close the circuit. You can even do it with a wire.

Examples
Arduino Microcontroller:(I/O lines)-->(time set buttons):Alarm Clock:(Alarm)-->(Record Button):VCR Remote
The Arduino would set the time of the alarm. When the alarm is set off, the record button is activated.

The Arduino board is about $40 and if the system was contained in a nice box, almost anyone could automate any device. Programming the Arduino is so simple. Basically, turn this port on and that port off and so on.

One problem I have is to turn off a switch that is permanently on, such as a light switch. Using a XOR gate would allow the local switch to be negated by turning the remote switch on. It may be even possible to get it down to one wire control.

Wireless is a big thing now, but at this point it is not so simple and this idea is not meant for data transfer, just control transfer. I will work on a drawing of a modified switch that can be installed to any device.