Print

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

[RichardS]

It seems that the macro designer only allows modules to be used as part of conditions if they belong to the same house code as the Monitored House Code. 

I have read other posts on this site which suggest using dummy modules for various purposes including using them as flags.  However, I am puzzled how using dummy modules would be that useful if they are restricted to the monitored house code.

Is there some other way to use a module status from another house code as a macro condition?


I have only been using AHP (with a CM15A) for a week or so, although I have previously used AH with a CM12 computer interface, so I am familiar with the basic concepts. I am just using X10 for lighting, and not attempting anything fancy with security or video.  I have 12 hardwired modules (10 dimmers, 2 relay) and a couple of plug-in and lamp modules, as well as 3 x MS13A sensors.

I have set up several macros including some with various conditions including flags, module status and time of day.  All macros are running in the CM15A as I want the system to function without a full-time PC.  The system is working pretty well overall, but if I add any new modules they will have to go under another house code as I have 16 active modules.

Thanks

RichardS
Perth, Western Australia

[dave w]

It seems that the macro designer only allows modules to be used as part of conditions if they belong to the same house code as the Monitored House Code. 

I have read other posts on this site which suggest using dummy modules for various purposes including using them as flags.  However, I am puzzled how using dummy modules would be that useful if they are restricted to the monitored house code.

First off I have not used AHP since 2007, so this explanation may not be correct any more, but is just a
"for what it's worth" explanation of CM15A/AHP limitations.

The problem is with the CM15A limited memory. The CM15A  only "remembers" the status of 16 modules (one house code). So it effects all your conditionals (IF A1 and A2 are ON then turn OFF B3, or IF A3 is ON and sunset, then turn on P16. AHP must know and remember the status of A1, A2, A3, for the macros to work). You can use other module address to trigger macros but the macro must run when the non monitored module address changes state. There can be no conditionals since the CM15A can't remember the status past the moment it sends the command.

You can also use flags to act as monitored module addresses giving you the effect of additional monitored address. Like the monitored house codes, the CM15A keeps track of Flag status. So Set or Reset the flag when a non monitored address changes state, then use the flag status in your conditionals. Certain flags are reserved so you can not use all 16. 

You may be able to monitor all house codes if you run AHP from 24/7 computer. A current AHP expert can fill in some of the gaps.

[RichardS]

Ok

Thanks for the explanation.  I will just have to work within that limitation.