x10 CM11A support is now fixed!

[ladekribs]

Good work done, thank You guys!
I installed the fix on my system last night and it worked right away!
Good also tha William compiled the code (much easyer but nothing learned).
now naturally comes the next question, Now I can use my X10 remote to Control the x10 devices,
 but how can i make it send other commands to linuxmce for example play media etc?

another question: I have a Rokulab Soundbridge, powered by an old amplifier, that I have to power ON/OFF manually,
how can configure a x10 on/off switch to control the amplifier in the same way as a light can be
controlled by a surveillance camera?

[jondecker76]

ladekribs-
Glad it is working for you..
I am still adding new features to the code for future releases. One of those features is the ability to use an external X10 remote to control anything in LMCE (Of course you would need a CM11A and a receiver such as the TM751 for example). Unfortunately, for now, x10 remotes will only control x10 devices and communicate to LMCE the new status of the device.

I'm not sure how far out this new functionallity is, but I will get to it!

[chrisbirkinshaw]

Could someone provide amd64 binaries? Many thanks.

[nosilla99]

@jondecker76

This functionality already exists by using the respond to events function.

I have setup a range of dummy security devices in the range of E1-E16.  The devices are set to disbaled so they don't invoke security scenarios if triggered.  I have then used a palmpad remote on house code "E" and created events within linuxmce to send commands to my X10 devices on diifferent housecodes.  So for example pressing button 1 on the palmpad sends X10 event E1 ON, LMCE then responds to this command by sending L1 ON which is a light.

I also have an event E16 ON which changes the display on my Media Director to the Webcam in my living room etc

It is not great that I had to create dummy security devices but it does work well and from a programming point of view I have named the devices PalmPad_1, PalmPad_2 etc so the events are logical.  It would be better to create a device template called X10_Remote which is controlled by the CM11A, but what I have done works fine.

Hopefully catch up with you on IRC to discuss X10 roadmap

Best Wishes

NOS

[nite_man]

Could someone provide amd64 binaries? Many thanks.

Posted it in the wiki - http://wiki.linuxmce.org/index.php/KnownIssues_0710_Beta4

[chrisbirkinshaw]

Thanks!

w/r to adding dummy devices - why choose security devices? You can add an event to respond to any device being switched on/off. Does it not work?

Chris

[nosilla99]

Thanks!

w/r to adding dummy devices - why choose security devices? You can add an event to respond to any device being switched on/off. Does it not work?

Chris

Chris I used security devices as presently the CM11A code will only send events to DCErouter if the device category of the incomming X10 message is a security device.  It will be a simple task to change this in the code but we need to think about what is the best approach in terms of creating a new category.

Nos   

[chrisbirkinshaw]

Ok I see your point.

I've got the new code running.... BUT.... there is a 10-30 sec delay when sending an X10 command. Is anyone else seeing this?

[nite_man]

Ok I see your point.

I've got the new code running.... BUT.... there is a 10-30 sec delay when sending an X10 command. Is anyone else seeing this?

I have the same problem. But I thought that it's related with electric wires.

[nosilla99]

Hi guys,

When I send events they usually take approx 1 second so I would be interested to see some CM11A logs so I can try to figure out what is happening with your setups.

Make a note of the time that you issue a command and then post a log so we can try to identify if the problem is within the CM11A code or if it is something else which is causing the delay.

If you tail the CM11A log there should be no activity until you issue a command and these should be acted upon within 100ms, the slow X10 protocol adds quite a large delay hence the normal 1-2 second response.
 
Am I correct in assuming you are both running AMD64 bit versions ?

NOS

[chrisbirkinshaw]

Something weird's going on. I see very little log activity, the CM11A does not respond to powerline events, and I get occasional checksum errors:

Code: [Select]

========== NEW LOG SECTION ==========
1       04/10/08 21:35:34       89 (spawning-device)    Starting... 1
1       04/10/08 21:35:34       89 (spawning-device)    Found /usr/pluto/bin/CM11A
05      04/10/08 21:35:55.558           Creating child 71 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 72 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 73 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 79 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 80 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 81 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 82 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 83 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 84 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 85 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 90 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.559           Creating child 91 <0x2addeb73d940>
05      04/10/08 21:35:55.559           Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.560           Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.560           Creating child 92 <0x2addeb73d940>
05      04/10/08 21:35:55.560           Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.560           Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
05      04/10/08 21:35:55.560           Creating child 93 <0x2addeb73d940>
05      04/10/08 21:35:55.560           Note: Device manager has attached a device of type 54 that this has no custom event handler for.  It will not fire events. <0x2addeb73d940>
05      04/10/08 21:35:55.560           Note: Device manager has attached a device of type 54 that this has no custom handler for.  This is normal for IR. <0x2addeb73d940>
01      04/10/08 21:36:57.119           Bad checksum received (send:69, recieved:55). <0x41802950>
01      04/10/08 21:43:20.043           Bad checksum received (send:69, recieved:55). <0x41802950>
01      04/10/08 21:56:48.048           Bad checksum received (send:69, recieved:55). <0x41802950>
01      04/10/08 22:06:06.215           Bad checksum received (send:69, recieved:55). <0x41802950>

Basically it seems I am running the old version. However I have used the files from the archive file supplied (link on the wiki). If I compare the updated version of CM11A I have in /usr/pluto/bin to the one I backed up before installing there is definitely a difference as the new version reports "<version>" as the version number but the original one reports v.2.0.0.44.0802262200.

Can you send me your libSerial, Lighting_Plugin, and CM11A?

Regards,

Chris

[nosilla99]

Chris,

That is definitely not the modified CM11A code as Jon and myself added additional debugging messages.

I only have i386 binaries as that is what I am developing on.

Where did you get your binaries from ?

NOS

[chrisbirkinshaw]

Here:

http://www.mediafire.com/?yl1mozw0p9r

(from this page: http://wiki.linuxmce.org/index.php/KnownIssues_0710_Beta4)

[nite_man]

I built them using sources from revision 1600 (charonmedia.org).

BTW, uploaded updated version - http://www.mediafire.com/?lkzl4ddwniz. It should be ok.

[nosilla99]

@nite_man,

So are you still experiencing 30 second delays or has the rebuild fixed the issue ?

NOS