To add to what Brian said, I have a shop that is on a sub-panel with a couple modules on it. I can control modules in the house from the shop and from the house to the shop. In order to do this reliably, I had to reduce noise/signal suckers and add a signal coupler/amplifier/repeater (XTB-IIR). You may not need to add the repeater depending on signal strengths and how clean you can make the rest of your setup.
I tried the XTB-IIR, worked great, only issue I had is what is cost and that is stopped working after about a year (burned out), so I now try to rely on the interface (previously the CM11, now the CM15).
Going back to the CM15, seems to be working fine with AHP with one exception. I have 2 codes (A-12 and A-15) that I have modules on. I have one older LM465 on code A-15 for my flag pole light and several LM465's (both older and newer versions) on code A-12 as well as a WS467 that turn on lights at dusk and turn off at 11:30PM. When I first got the CM15 recently, the WS467 seemed to work fine when I had the CM15 plugged into a specific outlet closest to the fuse panel. Point of clarification, I have 4 modules setup in the AHP DB, 1 for the older LM465 on code A-15, 1 for the older LM465 on code A-12, 1 for the newer LM465 on code A-12, and 1 for the WS467 on code A-12. This covers all the different codes and modules that are controlled thru the CM15 interface (also, CM15 in NOT connected to the PC, nor running AHP on a regular basis).
When I plug the CM15 into an outlet close to my PC so I can work with the DB in the CM15, I can control ALL the modules just fine. I have also tried putting the CM15 in that same outlet, again all the modules control (turn ON, turn OFF) except the WS467 when running standalone.
I am confused? Why would the CM15 work (turn on the WS467) when connected to the PC and control the WS467 just fine, but not when standalone? Output signal to the WS467 is the same, so this is what is confusing?