I've installed this image:
LinuxMCE-8.10-23036-i386.iso
I had to upgrade the kernel to 2.6.34 to get my tv cards working
I've then followed this guide
http://wiki.linuxmce.org/index.php/CM11
So now, I've got in the web admin under devices tree:
Core - CM11A (Device Template:CM11A #48, Device data: /dev/ttyS0) - livingroomlamp (Device Template:Light Switch (on/off) #37, Port/Channel Number: A6)
When I click "send command to device" on livingroomlamp and choose "on" in the dropdown I get this output:
Message Sent succesfully.
/usr/pluto/bin/MessageSend localhost -r 0 37 1 192 97 "" 98 ""
Response was:
RESP: OK
The light does not turn on though. If I click on the different log links there are no entries there.
havard@dcerouter:~$ cat /var/log/pluto/33_CM11A.log
05 07/11/10 8:08:57.388 Going to rotate logs... <0xb6a4fb90>
Return code: 143
3 07/11/10 12:32:53 33 (spawning-device) Device died... count=10/50 dev=33
Sun Jul 11 12:32:53 CEST 2010 died
========== NEW LOG SECTION ==========
1 07/11/10 12:33:03 33 (spawning-device) Starting... 11
1 07/11/10 12:33:03 33 (spawning-device) Found /usr/pluto/bin/CM11A
05 07/11/10 12:33:03.366 Creating child 36 <0xb70fb6c0>
05 07/11/10 12:33:03.366 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb70fb6c0>
05 07/11/10 12:33:03.366 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb70fb6c0>
05 07/11/10 12:33:03.366 Creating child 37 <0xb70fb6c0>
05 07/11/10 12:33:03.366 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb70fb6c0>
05 07/11/10 12:33:03.366 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb70fb6c0>
Return code: 143
3 07/11/10 12:33:52 33 (spawning-device) Device died... count=11/50 dev=33
Sun Jul 11 12:33:52 CEST 2010 died
========== NEW LOG SECTION ==========
1 07/11/10 12:34:02 33 (spawning-device) Starting... 12
1 07/11/10 12:34:02 33 (spawning-device) Found /usr/pluto/bin/CM11A
05 07/11/10 12:34:02.289 Creating child 36 <0xb71416c0>
05 07/11/10 12:34:02.289 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb71416c0>
05 07/11/10 12:34:02.289 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb71416c0>
05 07/11/10 12:34:02.289 Creating child 37 <0xb71416c0>
05 07/11/10 12:34:02.289 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb71416c0>
05 07/11/10 12:34:02.289 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb71416c0>
01 07/11/10 13:13:59.027 Failed sending address. <0xb613eb90>
01 07/11/10 13:28:05.375 Failed sending address. <0xb613eb90>
01 07/11/10 13:29:20.878 Failed sending address. <0xb613eb90>
I'm a noob in the ubuntu and linuxmce world so I don't really know what to do next, anybody have any suggestions?
Kind of weird thing happened here. I installed heyu and that works but with 100% cpu usage. Did a reboot, now one of two configured x10 devices worked via linuxmce. Then I tried heyu, that worked with all devices. The one lamp in linuxmce x10 stopped working after heyu started. Even if I stop heyu it won't be controled by linuxmce anymore, so guess I need a reboot.
Is it possible to run any commands directly to the linuxmce X10 stuff in the terminal (like heyu)?
Any way to use heyu in linuxmce instead?
No. The system isn't designed around duct tape.
-Thom
The linuxmce x10 is working.
I have put up a simple motor (Add A Motor 80) with a appliance module (on/off) attached to it to open and close my curtain.
However I need to send on and then off after the motor has stopped so it is ready to be run again by a new on signal.
Is there a device template for this? or will I need to use a scenario?
Looked at the scenario bit but didn't find any way to have it sleep for a specified time before it sends the next command.
I could of course send first an Off command then an On command, but that would mean theres always electricity on the motors so I would like to avoid that.
I guess an appliance switch is not the right switch to control the motor. Try to find a "SW10 Wall Mounted Shutter Switch" and add it to the system as a drape switch. That will probably do the trick.
It wasn't there on my system.
This is what I tried:
I went to the web admin pages. "Show devices tree" - "Core" - "CM11A" - Create child device - pick device template.
then I browsed through "Device Template"
Quote from: blahbla on July 16, 2010, 01:25:10 PM
It wasn't there on my system.
This is what I tried:
I went to the web admin pages. "Show devices tree" - "Core" - "CM11A" - Create child device - pick device template.
then I browsed through "Device Template"
I might have been a bit unclear.
The DeviceTemplate to install would be the Drapes Switch. The hardware device you need to install is a SW10 or similar X10 device.
Sorry, I misunderstood then.
I don't think this will be a practical solution for me because I have no place to put it without major work in the apartment.
I have the behaviour I want working with heyu, just a simple shell script:
#!/bin/sh
heyu on A3
sleep 5s
heyu off A3
heyu isn't working all that well on linuxmce though as it uses 100% cpu. Also it seems whatever runs a x10 command first of linuxmce or heyu gets the serial port until next reboot.