Author |
|
rmackay Groupie
Joined: December 15 2003 Location: United States
Online Status: Offline Posts: 28
|
Posted: February 26 2004 at 00:07 | IP Logged
|
|
|
I found your threads from a while back on this topic and the consensus was that you can not do it. I have found a way for it to work!
You hook both up (MR26A into the pass-through of the CM17A). Then, in PH, you set the MR26A as Controller 1 and the CM17A as Controller 2.
That did it! Works like a champ for me!
Robert
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: February 26 2004 at 10:03 | IP Logged
|
|
|
Robert,
Yes, the beta and the next release (1.03.2) support the passthru feature of the CM17A. As you've found out, all you have to do is make the CM17A a higher numbered controller.
The way it works is that IR controllers are loaded first in order followed by X-10 devices loaded in order. To use the passthru feature, just make sure that the CM17A is loaded after the controller that you're passing the port through to.
Dave.
|
Back to Top |
|
|
guerrand Senior Member
Joined: December 18 2005 Location: United States
Online Status: Offline Posts: 106
|
Posted: March 19 2006 at 23:58 | IP Logged
|
|
|
*picks up old topic* This one will do...
Anyway.. I had a massive system failure and had to reinstall powerhome, now I can't get both controllers working again. It recieves just fine but doesn't transmit.
*update*[nix that, just got it working, its only the socket prob now]*update*
On a possibly related note whenever I use the socketserver to send a command I get the error below.
An error occured while retrieving data from X10DEVICES AND X10TYPES tables
Thoughts?
Edited by guerrand
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: March 20 2006 at 01:28 | IP Logged
|
|
|
Guerrand,
Glad you got the controller issue worked out.
When you reloaded, did you load the same version of PowerHome you were using previously or are the versions different. Did this use to work before and is now broke since reloading?
If you can, please post the actual command you're using so I can reproduce it and I should be able to get it worked out pretty quickly.
Thanks,
Dave.
|
Back to Top |
|
|
guerrand Senior Member
Joined: December 18 2005 Location: United States
Online Status: Offline Posts: 106
|
Posted: March 20 2006 at 01:38 | IP Logged
|
|
|
it is the same version as before the *boom* It was working great before. I use a program called bluetooth lock to detect my phone and turn lights on/off appropriately.
The command structure I am using on my pc's end (seperate server for powerhome) is
c:\PHSSCMD\phsscmd.exe ph_x10btn('M1',3,0)
The command is going in but elicits the before mentioned error. I tested using
c:\PHSSCMD\phsscmd.exe ph_usermessage("Thiehroh")
and the test message appeared as it should.
I'm not sure what else to check. Everything seems in order.
also, I'm running windows 2k fully up to date.
Also after some more testing it seems that transmission works fine for the plampad mode but using the web interface doens't do much.
*sigh* had such a great setup goin, why'd windows have to take a header...
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: March 20 2006 at 02:15 | IP Logged
|
|
|
Guerrand,
Ive gotcha now. Since its the same version and you're sending the same command as before (it was the PowerHome PC that crashed, not the controlling PC), the only thing left is the PowerHome setup.
We know the Socket Server is working from the test message. I went ahead and ran a quick test and was able to reproduce your error by executing a ph_x10btn function to an X10 ID that didnt exist. You do have an X10 device defined with an ID of "M1" dont you ? The ph_x10btn functions first parameter is the ID of an X10 device which is different from it's house/unit code.
I think defining this device will take care of your problem.
What problem are you having with the web interface?
HTH,
Dave.
|
Back to Top |
|
|
guerrand Senior Member
Joined: December 18 2005 Location: United States
Online Status: Offline Posts: 106
|
Posted: March 20 2006 at 22:56 | IP Logged
|
|
|
The problem with the web interface is probably related to the socket server on. Basiclly it takes a long time to refresh the page and doesn't do anything.
I checked again and the device is configured in devices>x10>units
I have several units configured and all give the same result. Any other ideas?
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: March 21 2006 at 21:46 | IP Logged
|
|
|
Guerrand,
You may want to email your database to me. I should be able to figure it out pretty quickly then.
Dave.
|
Back to Top |
|
|