Messages

I'm happy to report, that in 810 the GC100 works as expected! I'm finally able to control my A/V equipment using IR ang GC100.
On the other hand, 810 is a bitch to make even the simple things working.

Did you by any chance try making the gc100 work in LMCE 8.10?

When I run :/usr/pluto/bin/MessageSend dcerouter 0 76 1 191 9 "0000 006f 0022 0002 0150 00ab 0016 0015 0016 0040 0016 0015 0016 0040 0016 0040 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0040 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0040 0016 05d4 0150 0055 0016 0e09", the receiver goes on perfectly.

But when running: "/usr/pluto/bin/MessageSend dcerouter 0 76 1 192" (Supposably the "On" command"), nothing happends. All I see in the DCERouter.log is:

08   03/09/09 22:18:54.705      Received Message from 0 (unknown / ) to 76 (RX-V650 / Living Room/Family Room), type 1 id 192 Command:On, retry none, parameters: <0x6fcb5b90>
05   03/09/09 22:18:54.756      Socket::ReceiveData 0x87d7c00 failed, bytes left 0 start: 1650000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 128 Incoming_Conn Socket 128 10.20.0.12 <0x6fcb5b90>
05   03/09/09 22:18:54.757      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 128 10.20.0.12 <0x6fcb5b90>
05   03/09/09 22:18:54.757      TCPIP: Closing connection to -1003 (Router Dev #0) 0x87d7c00 m_Socket: -1 <0x6fcb5b90>
05   03/09/09 22:18:54.757      Router::RemoveAndDeleteSocket 0x87d7c00 -1003 <0x6fcb5b90>

My guess is that somehow the "On" command is not bound to the right Pronto code of the reciever. Does anybody have any clue on how to approach this?

Bump!

Have you done test code on each code to see if it works?

-Thom

Yes, just like in rndinokc's case - test commands work, but the orbiter's remote doesn't. When in orbiter's "Media" I go to "Cable", a remote control appears, but none of it's controls work. Hitting the "Resend A/V codes" button brings a list of the devices that are involved in the current scenario, but none of them goes on even when directly clicked on. On the other hand, when I click the "Advanced" button near one the listed devices, and click the commends there I get a proper respons.

Bump!!! Pls....

I have a device template for each A/V device in my setup.

Any update there? I'm stuck with the same exact problem:

GC100 controling TV/Cable box/Receiver with IR (IR codes work in "A/V Advanced" for each device)
Media scenario is also created, but none of the controls in the "Remote control" works.......

Thanks.

Rebooting the core fixed the error messages, but I still don't have the PLM child devices showing up anywhere....

Any luck with your setup? I'm kinda stuck at the point were the "Insteon PLM" template is set and the "Insteon PLM" device is there, but it looks like no child devices are being recognized. "running the driver" is a one weird term indeed.....
Using the "plmtools" (http://sourceforge.net/projects/plmtools) I made sure that the PLM is fully functioning - I can turn my LampLincs on and off using the "insteon" script.

Well, now I've got to the point where I get the same type of messages you do: Cannot call class method: cmd_351 etc....

Weird... I did have a #141 ruby code(CD/DVD???), but not the 161. Removing the code from #141 got me an error free log, but I'm still struggling with getting PLM to work. It looks like the PLM is recognized, but it doesn't detect Insteon devices on the network. BTW, I've got the LampLinc starter kit just like you did.
Another thing I've noticed is that when I run: /usr/pluto/bin/TestSerialPort -p /dev/ttyUSB0 -P N81 -b 19200 -t "\02\60"  -i 1 -s "\03\05", I'm not always getting the same results which is weird. Here is some examples: "\02`\0fB\e8\03", "\02","\06"

As far as I understand this command suppose to return an identification string from PLM. Not sure what to think.

There is a little UPDATE in wiki:

...UPDATE I had to remove the ruby code from 141 & 161. The PLM wouldn't start due to errors from these two. 8/9/08 williammanda

Make sure you do that.