x10 CM11A support is now fixed!

[golgoj4]

So that didnt go so smoothly, but then I should have asked:

-is this for the beta only? i'm on 0704

-i do have the i386 version installed

the two error messages i noticed were

'get orbiter status failed'
and
'orbiter generation failed!'

but, since i made the backups as per the instructions, i restored it and now the screen is back up. sans all my lights though.

anyone have any thoughts on this?

[cobradevil]

it is only for the 0710 beta sorry if i wasn't clear enough.

with kind regards,

William van de Velde

[nswint]

Still a no-go for me

1   03/03/08 21:54:03   42 (spawning-device)   Starting... 1
1   03/03/08 21:54:03   42 (spawning-device)   Found /usr/pluto/bin/CM11A
10   03/03/08 21:54:03.291      Device: 42 starting.  Connecting to: localhost <0xb790b6c0>
10   03/03/08 21:54:03.293      Setting timeout for socket 4 to 20 <0xb790b6c0>
10   03/03/08 21:54:03.377      Socket::SendMessage type 5 id 37 from 42 to -1000 <0xb790b6c0>
10   03/03/08 21:54:03.377      Requesthandler 0x806d7d8 (device: 42) runThread now running <0xb7109b90>
10   03/03/08 21:54:03.419      TranslateSerialUSB /dev/ttyS0 isn't serial usb <0xb790b6c0>
10   03/03/08 21:54:03.419      Using serial port: ttyS0. <0xb790b6c0>
10   03/03/08 21:54:03.419      Connect OK <0xb790b6c0>
05   03/03/08 21:54:03.419      Creating child 43 <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateEvent for unknown type 38. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateCommand for unknown type 38. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb790b6c0>
05   03/03/08 21:54:03.419      Creating child 45 <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateEvent for unknown type 37. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateCommand for unknown type 37. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb790b6c0>
05   03/03/08 21:54:03.419      Creating child 46 <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateEvent for unknown type 38. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateCommand for unknown type 38. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb790b6c0>
05   03/03/08 21:54:03.419      Creating child 47 <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateEvent for unknown type 37. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb790b6c0>
10   03/03/08 21:54:03.419      Got CreateCommand for unknown type 37. <0xb790b6c0>
05   03/03/08 21:54:03.419      Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb790b6c0>
10   03/03/08 21:54:03.419      Device Poll thread started. <0xb6908b90>
10   03/03/08 21:54:03.419      Child device: #43(I2)   Category:73 <0xb6908b90>
10   03/03/08 21:54:03.419      Child device: #45(I3)   Category:73 <0xb6908b90>
10   03/03/08 21:54:03.419      Child device: #46(K2)   Category:73 <0xb6908b90>
10   03/03/08 21:54:03.419      Child device: #47(K3)   Category:73 <0xb6908b90>
10   03/03/08 21:54:05.508      Receive string:  <0xb7109b90>
10   03/03/08 21:54:05.508      Received  0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:06.671      Receive string:  <0xb7109b90>
10   03/03/08 21:54:06.671      Received  0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:28.460      Receive string: MESSAGE 82             <0xb7109b90>
10   03/03/08 21:54:28.460      Received MESSAGE 82             0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:28.461      Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10   03/03/08 21:54:28.461      Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10   03/03/08 21:54:34.929      Receive string: MESSAGE 82             <0xb7109b90>
10   03/03/08 21:54:34.929      Received MESSAGE 82             0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:34.929      Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10   03/03/08 21:54:34.929      Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10   03/03/08 21:54:37.750      Receive string: MESSAGE 82             <0xb7109b90>
10   03/03/08 21:54:37.750      Received MESSAGE 82             0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:37.750      Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10   03/03/08 21:54:37.751      Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10   03/03/08 21:54:39.732      Receive string: MESSAGE 82             <0xb7109b90>
10   03/03/08 21:54:39.732      Received MESSAGE 82             0x806d7d8 device: 42 <0xb7109b90>
10   03/03/08 21:54:39.732      Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10   03/03/08 21:54:39.732      Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>

[cobradevil]

What is not working?

when i send commands from the web interface i have to select the device (dimmable light module) then from the top screen you can choose send command to the device

from there select the action you want!!

on
off
set level

always ask for delivery notification

When i try it on the main screen nothing happens with the buttons on/off/level 50

With kind regards

William van de Velde

[jondecker76]

nswint-

Are you using 0710 beta 4?

[nite_man]

Are you using 0710 beta 4?

Was that fix added to the Beta 4?

[jondecker76]

yes I believe so, It was put into SVN about 5 days ago (i'm just getting ready to instll beta 4 myself to see)

[nswint]

Beta3.  I downloaded your precompiled files.  I'm about to upgrade to Beta 4 as soon as the torrent speeds up.  I downloaded the DVD+R DL and it doesn't work 


What's not working is that it's not controlling x10 modules, it is not even sending out X10.

I have an x10 controller using Xtension on my mac and it picks up other x10 commands over the powerline so I know that it's not transmitting.

nswint-

Are you using 0710 beta 4?

[jondecker76]

nswint -

I didn't do the precompiled modules (I was involved in patching the source)
However, I did upgrade to beta 4 myself and the x10 support did make it in. If I were you, I'd go that route - the torrent actaully went pretty fast for me.

Also, as pointed out in this thread, there is a bug in the web admin where you can test the x10 devices. This has been filed in mantis.

[golgoj4]

nswint -

I didn't do the precompiled modules (I was involved in patching the source)
However, I did upgrade to beta 4 myself and the x10 support did make it in. If I were you, I'd go that route - the torrent actaully went pretty fast for me.

Also, as pointed out in this thread, there is a bug in the web admin where you can test the x10 devices. This has been filed in mantis.

I just installed the beta4 today, yet im still getting the checksum error. Any ideas?

[jondecker76]

can you post a log?

[nswint]

It looks as if the web interface is indeed broken.  I was able to turn on my x10 lights via the orbiter but not my x10 controlled ceiling fans. Non of this was logged  to the CM11A log though.  I'll play around with the templates but it currently looks like a non-dimmable light switch in the template refuses to be controlled via the CM11A.  I'm not 100% certain but I will be able to test this out more this evening.

nswint -

I didn't do the precompiled modules (I was involved in patching the source)
However, I did upgrade to beta 4 myself and the x10 support did make it in. If I were you, I'd go that route - the torrent actaully went pretty fast for me.

Also, as pointed out in this thread, there is a bug in the web admin where you can test the x10 devices. This has been filed in mantis.

[jondecker76]

nswint-
The web admin bug was fixed and committed to SVN today according to mantis.

As far as x10 on/off devices, i use dozens of them on a daiy basis without a problem. (I believe I used the Light(on/off) template, but I am at work right now...)
Have you tested this with an external remote? Can you describe your setup (House/Unit codes for your lights and ceiling fans, different hardware, device template numbers etc). Also, if you could, post a log.

thanks

Jon

[nite_man]

I have similar problem with CM11A. I use CM11A (without butteries) connected to USB and one TM13 Transceiver (code A1). Additionally I have MS13A wireless motion detector (disconnected now).

At the beginning CM11A and TM13 worked fine but after MS13A was added I stated getting error with wrong checksum. The problem still exists in my Beta 4. As I already said MS13A is disconnected. Here is a log:

Code:

10      03/06/08 13:30:40.013           Child device: #33(A1)   Category:73 <0x41802950>
10      03/06/08 13:34:00.090           Receive string: MESSAGE 80             <0x41001950>
10      03/06/08 13:34:00.090           Received MESSAGE 80             0x62afb0 device: 32 <0x41001950>
10      03/06/08 13:34:00.090           Received Message type 1 ID 192 from 20 to 33 (device: 32) resp 0 <0x41001950>
10      03/06/08 13:34:00.090           Child device 33 has channel A1. <0x41001950>
10      03/06/08 13:34:00.139           Sending address with HouseCode=6, DeviceCode=6. <0x41802950>
10      03/06/08 13:34:00.139           Sending packet with HighByte=4, LowByte=66. <0x41802950>
10      03/06/08 13:34:00.139           Sending header with Checksum: 6a. <0x41802950>
10      03/06/08 13:34:00.583           Got response: 5a from CM11A. <0x41802950>
01      03/06/08 13:34:00.583           Bad checksum received (send:6a, recieved:5a). <0x41802950>
10      03/06/08 13:34:00.683           Sending address with HouseCode=6, DeviceCode=6. <0x41802950>
10      03/06/08 13:34:00.683           Sending packet with HighByte=4, LowByte=66. <0x41802950>
10      03/06/08 13:34:00.683           Sending header with Checksum: 6a. <0x41802950>
10      03/06/08 13:34:02.591           Got response: 98 from CM11A. <0x41802950>
01      03/06/08 13:34:02.591           Bad checksum received (send:6a, recieved:98). <0x41802950>
10      03/06/08 13:34:02.691           Sending address with HouseCode=6, DeviceCode=6. <0x41802950>
10      03/06/08 13:34:02.691           Sending packet with HighByte=4, LowByte=66. <0x41802950>
10      03/06/08 13:34:02.691           Sending header with Checksum: 6a. <0x41802950>
10      03/06/08 13:34:02.699           Got response: e6 from CM11A. <0x41802950>
01      03/06/08 13:34:02.699           Bad checksum received (send:6a, recieved:e6). <0x41802950>
10      03/06/08 13:34:02.799           Sending address with HouseCode=6, DeviceCode=6. <0x41802950>
10      03/06/08 13:34:02.799           Sending packet with HighByte=4, LowByte=66. <0x41802950>
10      03/06/08 13:34:02.799           Sending header with Checksum: 6a. <0x41802950>

Any idea what I do wrong?

[jondecker76]

You are indeed right -

It looks to me that the new fixed CM11A code DID NOT make it into beta 4.. I wonder why??? The changes were committed to SVN well before beta 4 was released.