Messages

31

Users / Re: Installing insteon and X10

« on: September 11, 2008, 04:16:45 am »

JQE,
After some pain I have it working. Please paste your logs to see if I can give you a hand.

Cesar

Do you have any clue what I can do to solve my problem?
Thanks

05   09/10/08 22:15:13.654      GSDMessageTranslator isCmdImplemented = false <0x42003950>
05   09/10/08 22:15:13.655      #### Pre-Process Queue = 1 <0x42003950>
05   09/10/08 22:15:13.666      _QueueProc Pre - 193 : 0 <0x40800950>
05   09/10/08 22:15:13.666      GSD-Sleep Pre 193 : 0 <0x40800950>
05   09/10/08 22:15:13.666      Process Queue = 1 <0x40800950>
(***):------dce--- cmdID:193, cmdFrom:0, cmdTo:41, cmdType:1, Priority:1
(***):------dce--- X10 DEVICE!!!
(***):DeviceID=A2
(***):X10 Byte1:6E
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:10
(***):From:41
(***):current State:100
(***):Wanted State:0
(***):ReportStatus: device:41 Status:0
05   09/10/08 22:15:13.855      GSD-Sleep Post 193 : 0 <0x40800950>
05   09/10/08 22:15:13.855      _QueueProc Post - 193 : 0 <0x40800950>
05   09/10/08 22:15:13.856      GSDMessageTranslator isCmdImplemented = false <0x42003950>
05   09/10/08 22:15:13.857      #### Pre-Process Queue = 1 <0x42003950>
05   09/10/08 22:15:13.914      _QueueProc Pre - 193 : 0 <0x40800950>
05   09/10/08 22:15:13.914      GSD-Sleep Pre 193 : 0 <0x40800950>
05   09/10/08 22:15:13.914      Process Queue = 1 <0x40800950>
(***):------dce--- cmdID:193, cmdFrom:41, cmdTo:41, cmdType:1, Priority:1
(***):Detected Command sent to Self!
05   09/10/08 22:15:14.074      GSD-Sleep Post 193 : 0 <0x40800950>
05   09/10/08 22:15:14.074      _QueueProc Post - 193 : 0 <0x40800950>
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3

32

Users / Installing insteon and X10

« on: August 05, 2008, 05:26:45 am »

I started on installing my insteon / X10 installation using the 2412S PLM and varying insteon / X10 devices. First I used ddamron's tutorial and had to make judgement call:

 Adding a Code Group

        * Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)

            * In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
            * click 'Create new group'

b4 is broken have to run sql manually to add new group close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and note Device_Category and Manufacturer you will need to set them in sql code below

INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES (Device_Category,Manufacturer,"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'

            * If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
            * Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
            * Check 'Ruby Internal Commands'
            * click Update

Well the "Insteon PLM" did show up correctly, so I didn't have to do the sql change. I'm not sure if this has any effect on the installation.

Then I continued on with the tutorial and tried out the 2412S PLM interface, using the follow log. I got three errors, two of which were from 141 & 161, which according to tschak shouldn't be used used with the interface (the interface wouldn't start). I decided to remove the code for both entries and I got what I think is a working system. See below:

/var/log/pluto/80_Generic_Serial_Device.log

(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):in RemoveCurrentCommand
(***):Current Command:{"Parameter1"=>"40", "Command"=>"SetCfg"}
01   08/04/08 23:11:48.248      Error while calling method: Cannot call class method: cmd_351
error: can't convert nil into String, line: 1457
backtrace:
   in: (eval): 1457
   from (eval):1457:in `+'
   from (eval):1457:in `removecurrentcommand'
   from (eval):41:in `cmd_351'
   from (eval):1457
 <0x42804950>
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Third attempt, Failing Command!
(***):in RemoveCurrentCommand
(***):Current Command:{"Parameter1"=>"40", "Command"=>"SetCfg"}
01   08/04/08 23:12:07.295      Error while calling method: Cannot call class method: cmd_351
error: can't convert nil into String, line: 1457
backtrace:
   in: (eval): 1457
   from (eval):1457:in `+'
   from (eval):1457:in `removecurrentcommand'
   from (eval):41:in `cmd_351'
   from (eval):1457
 <0x42804950>

The system seems to be sending out three requests for feedback then timing out (I only have a X10 WS467 light switch connected).

So I decided to test the system further, setup a X10 switch to turn off / on. I used the lights and setup a light switch manually for the X10 switch. Refer to the picture:

file:///home/linuxmce/Desktop/3.png

This doesn't seem to work, everytime I select off, I get this in the follow log:

/var/log/pluto/80_Generic_Serial_Device.log

   from (eval):41:in `cmd_351'
   from (eval):1457
 <0x42804950>
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:10
(***):out:02 6B 40 Length:3
05   08/04/08 23:22:36.373      GSDMessageTranslator isCmdImplemented = false <0x42003950>
05   08/04/08 23:22:36.373      #### Pre-Process Queue = 1 <0x42003950>
05   08/04/08 23:22:36.412      _QueueProc Pre - 193 : 0 <0x40800950>
05   08/04/08 23:22:36.412      GSD-Sleep Pre 193 : 0 <0x40800950>
05   08/04/08 23:22:36.412      Process Queue = 1 <0x40800950>
(***):------dce--- cmdID:193, cmdFrom:0, cmdTo:101, cmdType:1, Priority:1
(***):------dce--- X10 DEVICE!!!
(***):DeviceID=A2
(***):X10 Byte1:6E
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:12
(***):From:101
(***):current State:0
(***):Wanted State:0
(***):ReportStatus: device:101 Status:0
05   08/04/08 23:22:36.547      GSD-Sleep Post 193 : 0 <0x40800950>
05   08/04/08 23:22:36.547      _QueueProc Post - 193 : 0 <0x40800950>
(***):receive timeout=1
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:12
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:12
(***):out:02 6B 40 Length:3
(***):receive timeout=1

It shows that it is sending out a command to turn off A2 but it doesn't. So at this point I'm stuck. Not sure what to do next. Any feed back would apprecaited.
Thanks

33

Users / Re: LinuxMCE buttons don't work on the Gyration mouse

« on: August 05, 2008, 04:55:21 am »

Use this webpage posted by Seth

http://wiki.linuxmce.org/index.php/Using_the_Gyration_Remote_GYR3101US_%28Non-Fiire_Chief%29

This should make the remote usable but not like the fiire remote.

34

Users / Re: Insteon thermostat question

« on: August 04, 2008, 12:23:59 am »

I got look at the ruby code by ddamron and it looks like it does support the HVAC device.

35

Installation issues / Re: "UPDATED" Nvidia Driver install on MD (My Solution)

« on: July 29, 2008, 03:19:50 am »

Zaerc is right...I believe you just invoked that command on your core.

36

Users / Re: Confirmed "out-of-box" graphics cards

« on: July 29, 2008, 02:41:46 am »

I use the following cards:
7300 GT
7300 LE
9600 GT
All have 512MB ram. I use the alpha blend and I get some tearing but it is worth it to me.
Thanks

37

Users / Re: Insteon thermostat question

« on: July 19, 2008, 10:32:33 pm »

Bump

38

Users / Re: Insteon thermostat question

« on: July 17, 2008, 05:18:52 pm »

Bump!

39

Users / Re: Insteon thermostat question

« on: July 16, 2008, 02:45:57 am »

Bump!

40

Users / Re: Insteon thermostat question

« on: July 15, 2008, 04:37:57 am »

Ddamron if you could reply that would be great!

41

Users / Insteon thermostat question

« on: July 13, 2008, 09:11:40 pm »

Will these thermostats work with insteon on linuxmce:

http://www.smarthome.com/2491t1.html

http://www.smarthome.com/2491T7.html

If the one day will work can different scenarios be used to create daily temperture adjustments?

Thanks

42

Developers / Re: sqlCVS web admin is now fixed!

« on: July 13, 2008, 04:51:55 pm »

I'm not real sure how to update? Could you be more specific? Do I need this update?
Thanks

43

Users / Re: SOLVED 9600 GT problem

« on: July 12, 2008, 11:52:17 pm »

Ok it's working now. I found out the 169.12 didn't support the 9600 GT. I went through the exercise of using grub and the Xorg.0.log (using 169.12). 169.12 didn't recognize the 9600 GT. I decided to load up the 177 beta driver and everything works. What does this driver change due to linuxmce when it updates?
Thanks for your help!

44

Users / Re: Zwave or Insteon

« on: July 11, 2008, 01:51:26 am »

Will the Insteon setup in Linuxmce control the insteon HVAC unit?

45

Users / Re: 9600 GT problem

« on: July 11, 2008, 01:41:35 am »

Any other suggestions? Re-cap: During the installation of 7.10 linuxmce via DVD the video card works for text then the screen goes blank right before the "kubuntu" screen starts. Nothing else happens after that (I leave it on up to an hour).
Thanks