Comments on: LinuxMCE: adding CM11 interface

By: Michael Stepanov

Michael Stepanov — Tue, 23 Oct 2007 12:15:07 +0000

2 hadyos: I suspect that you have to add heyu X10 software controller as an interface, after that add CM11 and define heyu as parent device for it. The rest X10 devices - switches, sensors etc should be controlled via CM11.

Pluto or LMCE will route X10 command for switch, for example, to CM11 and then - to heuy where the command will be modified to solve the problem with interpretation X10 commands.

By the way, I setup yesterday CM11 and TM13U. They work perfectly without heyu wrapper.

By: hadyos

hadyos — Mon, 22 Oct 2007 17:24:01 +0000

I’ve tried Sam’s wrapper but I don’t understand where should I put this wrapper.
Is “heyu X10 software controller” is a top level device? What child devices should I add under it. ( The Lighting device are unaviliable under that device)
Could you be more clear on how use this “heyu X10 software controller” ?

By: Daniel Nadeau

Daniel Nadeau — Sat, 20 Oct 2007 21:09:46 +0000

I’ve tried for several days to get Sam’s wrapper up and running, but I need some extra help. I have an X10 system in my home with RF devices too. I’ve been able to get heyu to control lights from the command line, but I have never been able to get linuxmce to control the CM11a properly. Has there been any advancement on the bi-directional support? Also, could someone update the linuxmce Wiki with detailed instructions on how to get X10 working? Linux MCE is great, but for those of us that have large X10 implementations, it can be a nightmare.

By: Michael Stepanov

Michael Stepanov — Mon, 06 Aug 2007 09:21:04 +0000

Thanks for your replays, guys. I think it’ll be good to post your workarounds into LinuxMCE and Plutohome wiki to help people bring up x10 under LinuxMCE and Plutohome.

By: eloy

eloy — Sun, 05 Aug 2007 20:39:02 +0000

This is cool Sam, thanks for the information. I’m very familiar with bottlerocket so I’ll be giving the above a try. Thanks again!