Print

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

[Boiler]

Background - I've been using X10 devices for about 10 years.  Started with the CM11, upgraded to a CM15A in 2003.  In general, I've been happy.  Using the various forums I've learned the limitations of the CM15A and found workarounds.  My current configuration contains a mix of Insteon devices (used in X10 compatibility mode), Leviton X10 switches, X10 switches, X10 Outdoor motion sensor floods, and MS13A motion sensors.  I added Smart Macros around a year ago to allow me to track the lighting status in the house and turn on/of an various buttons on keypadlincs in the house (button indicates that there is at least one lamp on in a particular zone).

All was well until... I built a new computer a few weeks ago.  Installed AHP 3.204 (with smartmacros) and loaded MyHome configuration from a backup.  I was pleasantly surprised when everything appeared to work properly...

I recently noticed that my motion sensors were not firing the associated macros in AHP.  I have AHP configured with all transceived house codes off (I hate the activity that the motion sensors put on the power line).  Instead I use macros to monitor the received RF and turn on a lamp if it is not already on (Flag status).  I've checked the RF received status in activity monitor - the CM15A is receiving the signal from the motion sensor.  The macro is simply not executing.  In troubleshooting I removed all of the conditionals which left a macro that simply turned on switch A3 if Trigger A4 was executed - No Joy.  Below if a summary of the setup.

1) AHP setup - All transceived Houscodes Off.
2) Monitored Housecode B
3) Motion sensor address A4 (with dusk/dawn output on A5).
4) Hall switch address A3

Macro
  Trigger : A4 On
  Action : A3 On

The only way that I can get this simple macro to work is to turn on housecode "A" under transceived housecodes (which of course puts all of the motion sensor activity on the powerline).  I'm sure I didn't need the A housecode transceived before.  Just to check my sanity, I've read quite a few posts on this site - from what I've seen and what I remember, turning off the Transceived housecode should prevent it from being placed on the powerline.  I should still be able to trigger macros from the incoming RF signal.

The only thing that I can think of is that the AHP version I downloaded was differend that what I was using previously.  I wasn't smart enough to write down the version that I had on the old PC (cannibalized for the new unit).  I was hoping that someone on the forum could verify that my original configuration works on their setup and tell me what version of AHP they are running.

Thanks,
The Boiler

[Boiler]

OK, this is wild-

I've tried re-setting my CM15A multiple times (battery out procedure) - no luck.

Re-installed AHP and created a simple macro to trigger on My MS13a RF (A4) and turn on lamp A3 - no go.  With the housecode A Transceive turned off, AHP registers the RF input on A4 but does not fire the Macro.  If housecode A is set to transceive,  everything works but AHP is putting the X10 Activity on the powerline.

In utter frustration, I remembered I had a second CM15A stored away.  Loading things up and, you guessed it, everything works perfectly!  I couldn't believe it.  Just to verify, I put the original CM15A back in place and loaded the same macros - still no go.

I'm completely mystified.  What I had assumed  was a software "upgrade" problem now appears to be hardware.  What's even more strange is this was working a couple of months ago. 

Anyone have a clue what "hardware" in the CM15a could produce this.  Could the firmware have become corrupted?

Still Clueless
The Boiler

[Puck]

Boiler: Generally, as you have mentioned, an RF signal does not need to be set to transceive in order to trigger a macro. I have many motion detectors and remotes that are not set to transceive and all trigger their respective macros just fine.

However, in my recent process of setting up 2 CM15As to communicate and work together, I did find a scenario where I did need to transceive an RF signal because it would not trigger macros unless it got sent to the power lines first. That scenario is when the macro is stored and run from the PC and not from the interface. With my CM15As, this is repeatable.

With you trying 2 different CM15As, I'm not so sure this is the same case for you.
I'll keep thinking about this and if you discover anything else please continue to update us.

[Boiler]

Puck: Thanks for the reply.  As you indicated, I have been downloading the timers and macros to the CM15a.  I do not leave AHP active on the computer.  The CM15A interface runs in stand-alone mode most of the time.  In fact, it operated for over a week while I was re-building my PC.

I just cannot understand what could have changed in the interface to prevent the macro triggering.  It seems that if it can receive the RF input and transceive it, it should be able to trigger a macro with the transceive disabled.  The only thing I can come up with is corrupt firmware.  I'm just amazed that this seems to be the only function affected.

I am sure that I was not running previously with the Rf inputs transceived.  One of my MS13A units is in a high traffic area.  When I first installed the sensor I ran into the problem of the MS13A repeatedly putting X10 motion signals on the powerline which effectively locked up my system.  The only way I could operate with this sensor was to disable the treansceived Rf and filter the inputs with a macro.

Any insight you may have would be greatly appreciated.  I'd really like to understand this problem. 

Thanks again,
The Boiler

[Boiler]

Link to AHP revision history - nothing really jumps out here
http://www.x10.com/support/rev_ahp.htm

[Boiler]

Sorry, I screwed up.  The previous reply was in reference to a different post (too many tabs open at the same time).

Realized two things:
1) I had installed HomeSeer (trial version) on my new PC recently.  Didn't know if this might conflict with AHP.
2) I had a previous installation of AHP on my wifes laptop that I had used for troubleshooting.  There were two configuration files on this machine (.ahx files)  One file from 11/6/05 and one from 2/24/07.

Brought my two CM15a interfaces up and tried them on the laptop:
1) Interface 1 (old): With the transcieved house codes turned off (default in both files) the interface would not trigger my macros.
2) Interface 2 (newer): With the transcieved house codes turned off the interface triggered macros.

Other than a small round label on the back of the CM15a's (date code?) I can't see any difference between them.   
1) Interface 1: 04I38
2) Interface 2: 06L50

I'm still can't figure out why the "old" interface (which was apparently working as far back as 11/6/05) suddenly stopped.  I've never seen any documentation on the firmware for the CM15a.  Is there anyway of downloading (comparing) or performing a CheckSum on the firmware?

Thanks,
The Boiler