Posted: November 08 2002 at 21:44 | IP Logged

Terry,

The first problem you'll have is that PowerHome only allows a single controller per COM port.  This means that the pass thru port on the CM17A cannot be used.  This is in a large part due to the Microsoft COM control being used does not allow the same COM port to be used across multiple instances of the control.  At this point, Im assuming this will create problems for you as you probably only have two COM ports and the mouse is plugged into COM1. 

Working around the first problem...The next problem is that the MR26A will pick up and respond to any commands that are sent by the CM17A.  This will most likely produce results which are not desired as PowerHome cannot differentiate between RF commands sent by the CM17A and commands sent by a palm pad.  You can work around this problem by defining different housecodes for sending via the firecracker and sending via some other type of remote such as a palm pad.  The good news...the next version of PowerHome will include an option to have the MR26A not respond to commands recently sent via a CM17A.

The MR26A will update X-10 status of any device which is flagged as a status-only device in the X-10 types screen.  This is useful for showing the status of devices such as motion sensors.  The MR26A can also have any received commands automatically echoed for housecodes of your choice.  In your particular situation though, this will not work as any commands sent via the CM17A will be picked up by the MR26A and then echoed out the CM17A and picked up by the MR26A....etc.  You'll get your finest level of control by using triggers with the MR26A.  With triggers you can respond to only the MR26A commands that you are interested in.  Within a trigger, you can directly update X-10 status to reflect whatever you like, play a macro, etc.  The triggers really arent that difficult.  The MR26A responds to X-10 RF In trigger types.  Using this technique, you could have the MR26A not respond to any commands sent via the CM17A (just don't declare a trigger for it).  Commands that you define a trigger for with the MR26A, could immediately be echoed out using the CM17A and a different housecode.

A simple way to see what MR26A sees would be to just open the event log.  Any received commands will appear there if you are logging Incoming X-10.

The next version will be ready soon and although it wont help you with multiple controllers per COM port problem, it should solve the problem of you using the MR26A echo function.  Play with triggers and let me know if you have any problems or questions as this is where you'll get the most power.

Dave.

PS...thanks for registering.

Posted: November 10 2002 at 17:30 | IP Logged

Terry,

Macros can be exported from within the PowerHome explorer and the resulting SQL posted within a message.  Ive done it a few times on the board myself.  I encourage anyone who is willing to post any macros, scripts, etc to the board for others to use and learn.  As far as other boards or groups, this is the only one that I know of .

Now for your problem...It could probably be solved several different ways but I'll outline what Im currently thinking of.

You probably have the motion sensor to only trigger when dark.  The motion sensor is directly tied to the light by placing them on the same house and unit code.  You've programmed in some amount of delay.  The light that the motion sensor controls directly effects the light/dark sensor of the motion detector getting the behaviour you describe.

The way I would fix it would be to first place the motions sensors house/unit address to something completely different from the light.  Program the motion sensor to work all the time, not just when it's dark.  Set the timeout delay for the amount of time you would like for the light to turn off after there is no motion.  With that done, program PowerHome to have a trigger when motion is detected on the sensor.  If the motion sensor is set to A1, then create an X-10 RF In trigger for A1 On.  In the action, check the X-10 status of the A2 (the light/dark sensor) and if it's dark, then send an X-10 command and turn the light on.  As long as there is motion being detected, the motion sensor will send the A1 On command.  Your trigger will process but will not turn on the light because it's no longer dark (it would not matter if it did...sending an on to a light that is already on makes no difference).  When motion is no longer detected and the timeout delay expires, you will get an A1 Off command.  Create a trigger for it and turn the light off.

The only problem with the above technique is that you might notice a slight delay in the light coming on.  This is the way I control all my lights and the delay is not noticeable to me.

Let me know if you need help with the above and I can put it together for you.

Dave.

Posted: November 13 2002 at 10:14 | IP Logged

Actually the SQL output isn't bad at all.  It's all clear readable text and is easily cut and paste postable to the message board.  You can see an actual posting in the GetWeather macro in the following post:

http://www.myx10.com/forum/display_topic_threads.asp?ForumID=1&TopicID=69&SearchPagePosition=1&search=weather&searchMode=allwords&searchIn=Thread&forum=0&searchSort=dateDESC&ReturnPage=Search

Dave.