Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roadking]

I've read dozens of posts looking for some help with this problem, but found none.

Background:
- AHP v3.204, CM15A, Vista OS, MS14A Sensor, several various x10 devices to control lighting and appliances.

I have cleared the interface memory and downloaded macros and timers.

Problem:
MS14A sends "on" signal to cm15a which activates a macro (N5) to turn on a light (C6) and then off again after a delay.
For some reason, I also get "macro" signals to turn on other lights that are on another house code (D4 and D5).   Macro N5 has no reference to D4 or D5.

How can I find what is triggering D4 and D5 "on"?


Here is the log;

         02/01/2008 8:51:10 am    Transmit    N5 (Basement landing sensor)
1    02/01/2008 8:51:11 am    Transmit    N On (Basement landing sensor)
2    02/01/2008 8:51:12 am    Macro    C6 (Stairs light)
3    02/01/2008 8:51:12 am    Macro    C On (Stairs light)
4    02/01/2008 8:51:16 am    Transmit    N5 (Basement landing sensor)
5    02/01/2008 8:51:16 am    Macro    D4 (Driveway Lights)
6    02/01/2008 8:51:16 am    Macro    D On (Driveway Lights)
7    02/01/2008 8:51:16 am    Transmit    N Off (Basement landing sensor)
8    02/01/2008 8:51:17 am    Macro    D5 (Island lights)
9    02/01/2008 8:51:17 am    Macro    D On (Island lights)
10    02/01/2008 8:51:31 am    Macro    C6 (Stairs light)
11    02/01/2008 8:51:31 am    Macro    C Off (Stairs light)

[PajamaGuy]

Can I assume you've looked at File>Reports>Macros  ?

[roadking]

Yes.  and the N5 Macro does not turn on lights D4 or D5.

However, I do have other macros and one of them (M1 On) turns on lights D4, D5 and D6.  But what would make Macro N5 trigger Macro M1?

Is it possible to add a picture of my Macro report to this post?

[Tuicemen]

Is it possible to add a picture of my Macro report to this post?

Yes capture to your clipboard then create a pic with window paint save and upload
Hint: Option to send is under "additional options" when your the creating a post screen.
Check you batteries in the motion sensor!
Usually they reset to A1 when they fail but I had one go to a different house code and unit number!
The strange thing about this is, it still worked on the programed setting as well(although not always)
Remove the sensors batteries and trigger the macro with a remote (palm pad) and see if the same things happen!
Since you have cleared the interface (and presuming purged delayed macros) and reloaded the interface,
Check your macros (it is easy to over look an old macro when ones system gets large), also delete any thing that is in AHPs waste basket!

[GerryFR]

I was having similar problems with a phantom macro.  I looked under "Find Other Computers" and discovered a macro listed that did not show up anywhere in my AHP windows.  I went through all my macros and though I found some items that need correcting, none should have had any effect on this phantom macro.  The information window that comes up when you put your mouse over the phantom macro said that it was triggered by a security sensor macro.  However, the same window indicated that the macro was being triggered by a sensor which did not exist in my system.  I know that in the past I had used this security sensor for controlling an appliance module.  I had cleared the memory on my AHP unit and had removed the batteries to reset the unit.  I even changed the address on the module being programmed and found the problem followed it to the new address.  To further confuse the situation, I found that the module was not really being controlled, it was just being show as such in the AHP window.

I finally decided to remove any macro that (at any time) was related to this problem and the problem went away.  I can only assume the problem is in the computer program that downloads the code to the AHP module.  It seems to have a memory for old devices and programming that can only be removed by deleting any macro that was related to the deleted macro. 

I would suggest that if you are done with old macros, do not modify them for new uses as you may end up with my problem.  Delete old macros entirely before generating any new macros that use the old macro's modules.