CM15a keeps executing two totally unrelated macros at the same time...

[hatespants]

So I have a macro that turns an overhead light and some shelf lights on when an eagle eye detects motion. I also have a macro which toggles my window fan on and off with the push of a single button. Now within the last 24 hours, without me changing anything, my window fan is turning on along with the lights for some reason and it's driving me crazy!

I checked the activity monitor and the damn thing even acknowledges that it's firing both macros at the same time upon receiving the on command from the eagle eye. I've been wracking my brain over this, I can't find any relation between my fan macro and my lighting macro. They're not even near each other in the code spectrum.

Has anyone else experienced something like this?

[Brian H]

Can you post the macros contents so we can look at them?
Hard to guess why a macro is not activating correctly when we don't have a clue what it says.

[Tuicemen]

Have you emptied the AHP recyle bin?
AHP has been known to fire deleted macro/modules left in the recyle bin.

[dave w]

Also remember that it is easy for the motion sensor to default to "A1" if batteries are low, or have a bad connection. Your fan macro isn't using A1 as a trigger, is it?

[hatespants]

Thanks for the responses all! I emptied the bin (didn't know that was there!). I cleared and re-flashed the memory...problems persisted.

The macros in question are simple: eagle eye is B10. "B10 on" fires a macro which turns lights A16 and A14 on. Window fan turns on when "A9 on" is received, a flag is set. When "A9 on" is received again, the fan turns off and the flag is cleared. I've narrowed things down a bit more because my space heater has now also started coming on along with the lights sometimes. My heater toggle just happens to be triggered by "A9 off", so I now know something is sending on/off signals specifically on A9. 

Is it possible the eagle eye is sending stuff on A9, even though its address is B10?

[Tuicemen]

Is it possible the eagle eye is sending stuff on A9, even though its address is B10?

Yes, when batteries start to fail I've seen them go all over the place they usualy go to A1 with failing (weak) batteries but not always.

[Noam]

Do you have any motion sensors on A8? Some of the motion sensors have a built-in dusk/dawn feature, and will send an "off" code one unit higher when they sense light, and an "on" code when it becomes dark.
For example, a motion sensor on A8would trigger "A9 Off" when a light nearby comes on, and "A9 on" when the light goes off.

[hatespants]

No motion or photo sensors on A8/A9 unfortunately. Batteries are new. I've created a workaround by just letting the eagle eye directly control the lights since I'm not doing anything fancy like I used to. It's been extremely reliable this way, so far...

Just wish I could figure out what the heck was going on. Maybe my CM15a is losing its (already fragile) mind?

Thanks for the help gang!

[dave w]

Just wish I could figure out what the heck was going on. Maybe my CM15a is losing its (already fragile) mind?

Just as a side comment to all on this.

If you follow the forum, it seems there are a number of "My CM15A used to work, now it doesn't..." type of comments popping up, that can't be chalked up to noise/signal sucker problems. I wonder if CM15A age has anything to do with these comments.

Could the CM15A design/quality of components/build quality,  give it old age Alzheimer's problem?