Author Topic: X10 problems making me tear my hair out...  (Read 817 times)

asplodzor

  • Regular Poster
  • **
  • Posts: 17
    • View Profile
X10 problems making me tear my hair out...
« on: August 15, 2008, 09:56:48 am »
Hey guys, I've been trying to install a CM11a X10 interface into my core for over a week now to no avail. I have it plugged into a Prolific PL2303 USB to Serial adapter and it's working fine with heyu (http://heyu.tanj.com/), a command line-based X10 control program.

I've gone through the steps in 'Setup', 'Adding Lights', and 'Troubleshooting' here: http://wiki.linuxmce.org/index.php/CM11 and ran the configuration videos. I've also tried tweaking settings in the CM11a's page and the individual lights' pages, and even deleted them and re-run the configuration multiple times. At one point I thought it might have been a capitalization or numerical issue, so I tried all four ways (i.e. A1, A01, a1, a01) for all devices in the room, and even tried moving everything to the default housecode (I don't normally use A).

I'm stuck now with full functionality through heyu, but never once have I gotten linuxmce to change the state of any of my X10 devices.

Any ideas?

asplodzor

  • Regular Poster
  • **
  • Posts: 17
    • View Profile
Re: X10 problems making me tear my hair out...
« Reply #1 on: August 15, 2008, 10:52:32 am »
Two more things I should add... I've been puzzling over what on earth the crossed-out 'F' symbol is on the floorplan page. I doesn't appear to do anything other than display a larger 'F' not crossed-out which toggles with the first one:


http://img84.imageshack.us/img84/653/screenshotab0.jpg

Also, here's a dump of my log for the most recent time I've tried installing and testing all four X10 devices in the room. From what I can tell, it looks like light switch templates don't know how to talk to the CM11a's template for some reason:

Code: [Select]
== ATTEMPT FRESH START ==
1 08/15/08 00:29:05 /usr/pluto/bin/Spawn_Device.sh 69 (spawning-device) 23647 Dev: 69; Already Running list: 15,16,17,18,28,29,20,24,32,22,25,21,63,
== FRESH START ==
1 08/15/08 00:29:05 /usr/pluto/bin/Spawn_Device.sh 69 (spawning-device) device: 69 ip: localhost cmd_line: CM11A
0 08/15/08 00:29:05 69 (spawning-device) Entering 69
========== NEW LOG SECTION ==========
1 08/15/08 00:29:05 69 (spawning-device) Starting... 1
1 08/15/08 00:29:05 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:29:05.272 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 69 last error 2 <0x2ae7d68d5940>
05 08/15/08 0:29:05.272 The router must be reloaded before this device is fully functional <0x2ae7d68d5940>
05 08/15/08 0:29:05.274 void ClientSocket::Disconnect() on this socket: 0x62e9d0 (m_Socket: 5) <0x2ae7d68d5940>
05 08/15/08 0:29:05.284 Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 69 last error 2 <0x2ae7d68d5940>
05 08/15/08 0:33:07.405 Got a reload command from 0  <0x41001950>
05 08/15/08 0:33:07.679 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2ae7d68d5940>
Return code: 2
2 08/15/08 00:33:07 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 00:33:07 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 00:33:15 69 (spawning-device) Starting... 1
1 08/15/08 00:33:15 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:33:16.084 Creating child 70 <0x2b1eeef45940>
05 08/15/08 0:33:16.084 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.084 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Creating child 71 <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Creating child 72 <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b1eeef45940>
05 08/15/08 0:33:16.085 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b1eeef45940>
05 08/15/08 0:37:42.313 Got a reload command from 0  <0x41001950>
05 08/15/08 0:37:42.710 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2b1eeef45940>
Return code: 2
2 08/15/08 00:37:42 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 00:37:42 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 00:37:50 69 (spawning-device) Starting... 1
1 08/15/08 00:37:50 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 0:37:51.308 Creating child 71 <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Creating child 72 <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.308 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Creating child 73 <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Creating child 75 <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2b59849e4940>
05 08/15/08 0:37:51.309 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2b59849e4940>
01 08/15/08 0:40:55.268 Failed sending address. <0x41802950>
01 08/15/08 0:41:40.509 No response from CM11A device. <0x41802950>
01 08/15/08 0:42:10.823 Failed sending address. <0x41802950>
01 08/15/08 0:42:56.059 No response from CM11A device. <0x41802950>
01 08/15/08 0:43:26.365 Failed sending address. <0x41802950>
01 08/15/08 0:44:41.888 Failed sending address. <0x41802950>
01 08/15/08 0:45:12.018 No response from CM11A device. <0x41802950>
01 08/15/08 0:46:12.918 No response from CM11A device. <0x41802950>
01 08/15/08 0:46:58.335 Failed sending function. <0x41802950>
01 08/15/08 0:48:13.773 No response from CM11A device. <0x41802950>
01 08/15/08 0:48:13.873 Failed sending address. <0x41802950>
01 08/15/08 0:49:29.404 Failed sending address. <0x41802950>
01 08/15/08 0:50:30.684 No response from CM11A device. <0x41802950>
01 08/15/08 0:51:00.994 Failed sending address. <0x41802950>
01 08/15/08 0:52:16.520 Failed sending address. <0x41802950>
01 08/15/08 0:52:47.126 No response from CM11A device. <0x41802950>
01 08/15/08 0:53:47.642 Failed sending function. <0x41802950>
01 08/15/08 0:55:04.917 No response from CM11A device. <0x41802950>
01 08/15/08 0:55:20.040 No response from CM11A device. <0x41802950>
01 08/15/08 0:56:05.452 Failed sending address. <0x41802950>
01 08/15/08 0:57:20.979 Failed sending address. <0x41802950>
01 08/15/08 0:57:51.113 No response from CM11A device. <0x41802950>
01 08/15/08 0:59:22.303 Failed sending function. <0x41802950>
01 08/15/08 1:00:37.745 No response from CM11A device. <0x41802950>
01 08/15/08 1:00:37.845 Failed sending address. <0x41802950>
01 08/15/08 1:01:53.364 Failed sending address. <0x41802950>
01 08/15/08 1:03:08.887 Failed sending address. <0x41802950>
01 08/15/08 1:04:09.223 No response from CM11A device. <0x41802950>
01 08/15/08 1:04:24.346 No response from CM11A device. <0x41802950>
01 08/15/08 1:04:24.458 Failed sending address. <0x41802950>
01 08/15/08 1:05:25.265 No response from CM11A device. <0x41802950>
01 08/15/08 1:06:10.602 No response from CM11A device. <0x41802950>
01 08/15/08 1:07:30.293 No response from CM11A device. <0x41802950>
01 08/15/08 1:07:30.393 Failed sending address. <0x41802950>
01 08/15/08 1:08:13.422 No response from CM11A device. <0x41802950>
01 08/15/08 1:08:43.739 Failed sending address. <0x41802950>
01 08/15/08 1:09:59.626 No response from CM11A device. <0x41802950>
01 08/15/08 1:11:19.289 No response from CM11A device. <0x41802950>
01 08/15/08 1:11:49.982 No response from CM11A device. <0x41802950>
01 08/15/08 1:12:35.395 Failed sending function. <0x41802950>
01 08/15/08 1:13:50.930 Failed sending address. <0x41802950>
01 08/15/08 1:14:21.068 No response from CM11A device. <0x41802950>
01 08/15/08 1:15:06.481 Failed sending address. <0x41802950>
01 08/15/08 1:16:22.011 Failed sending address. <0x41802950>
01 08/15/08 1:17:38.010 Failed sending function. <0x41802950>
01 08/15/08 1:17:53.497 No response from CM11A device. <0x41802950>
01 08/15/08 1:18:54.017 Failed sending function. <0x41802950>
01 08/15/08 1:19:39.257 No response from CM11A device. <0x41802950>
01 08/15/08 1:20:09.563 Failed sending address. <0x41802950>
01 08/15/08 1:21:25.086 Failed sending address. <0x41802950>
01 08/15/08 1:22:40.626 Failed sending address. <0x41802950>
01 08/15/08 1:23:10.751 No response from CM11A device. <0x41802950>
01 08/15/08 1:23:56.171 Failed sending address. <0x41802950>
01 08/15/08 1:25:11.690 Failed sending address. <0x41802950>
01 08/15/08 1:25:41.828 No response from CM11A device. <0x41802950>
01 08/15/08 1:27:13.022 Failed sending function. <0x41802950>
01 08/15/08 1:28:28.560 Failed sending address. <0x41802950>
01 08/15/08 1:30:29.864 Failed sending function. <0x41802950>
01 08/15/08 1:30:59.998 No response from CM11A device. <0x41802950>
01 08/15/08 1:31:15.122 No response from CM11A device. <0x41802950>
01 08/15/08 1:31:45.426 Failed sending address. <0x41802950>
05 08/15/08 1:32:50.321 Got a reload command from 0  <0x41001950>
01 08/15/08 1:33:03.153 No response from CM11A device. <0x41802950>
05 08/15/08 1:33:03.158 void ClientSocket::Disconnect() on this socket: 0x62eeb0 (m_Socket: 6) <0x2b59849e4940>
Return code: 2
2 08/15/08 01:33:03 69 (spawning-device) Device requests restart... count=1/50 dev=69
Fri Aug 15 01:33:03 PDT 2008 Restart
========== NEW LOG SECTION ==========
1 08/15/08 01:33:11 69 (spawning-device) Starting... 1
1 08/15/08 01:33:11 69 (spawning-device) Found /usr/pluto/bin/CM11A
05 08/15/08 1:33:11.462 Creating child 71 <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.462 Creating child 72 <0x2af8436bb940>
05 08/15/08 1:33:11.462 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Creating child 73 <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Creating child 75 <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2af8436bb940>
05 08/15/08 1:33:11.463 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2af8436bb940>

jondecker76

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 763
    • View Profile
Re: X10 problems making me tear my hair out...
« Reply #2 on: August 15, 2008, 11:37:54 am »
For your CM11A interface device, is your serial port set correctly?
Webadmin->Devices->Interfaces
You should have options such as /dev/ttys0, /dev/ttys1, and if you have USB serial adapters, you should have also something like pci0000:00/0000.........
Make sure the correct one is selected.
Also while on this page, look at your controlled by field.. It should be an actual Core or MD device (mine is Core)

Now lets make sure your lights are correct webadmin->devices->Lights
1-Make sure the Controlled By field is set to CM11A
2-IN the Port/Address field is where to put the X10 House/Unit code in the format of A1,C2,D11, etc

Also, if you unplug your CM11A for 15 seconds from both the wall and the computer, it will reset the interface incase it is locked up

asplodzor

  • Regular Poster
  • **
  • Posts: 17
    • View Profile
Re: X10 problems making me tear my hair out...
« Reply #3 on: August 15, 2008, 12:16:45 pm »
Here's my config page. My system doesn't have any dedicated serial ports so I'm using a USB dongle and have the only option in the drop-down selected.


http://img204.imageshack.us/img204/157/screenshot3rg5.jpg

I was just screwing around a couple of minutes ago and decided to change 'Comm Method' in the CM11a's Device Template from RS232 to USB... suddenly it started working ... kinda. It's currently transposing most of my commands to different housecodes (o7 to m7 for instance), attempting to brighten non-dimmable modules, and absolutely no media-initiated scene starts. Oh, and occasionally it'll send commands to the wrong unit codes as well. (I test a lighting scenario that is only supposed to turn on o7 and it tries to brighten m8).


http://img204.imageshack.us/img204/9997/screenshot2rw3.jpg

I'm using a Testerlink 4819 (sorta like this guy but much less complex: http://www.smarthome.com/2200att.html) to see the gibberish on the line, otherwise I would have never known it was sending commands at all.

jondecker76

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 763
    • View Profile
Re: X10 problems making me tear my hair out...
« Reply #4 on: August 15, 2008, 01:36:31 pm »
very strange. You shouldn't have to change the comm method to USB, as its the USB->Serial adaptor's job to present a serial interface to the OS.

Do you possibly have another USB->Serial adaptor that you could try? The CM11A will only try to send the commands it receives out to the powerline, and it appears to be getting scrambled before actually reaching the device.

What version of LMCE are you running? Pre-0710 releases had broken CM11A functionallity...