Print

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

[PaulBennett]

Talked with the guru's yesterday.  They are aware of the problem because of this forum.  They are working on a solution and the fellow said we are likely to have the solution posted here before they know about it in the main office.  We'll see.

My Situation:
Sensor on A2, Light on K11.  Macros works when no conditions are used.  Introduce any condition and it quits working.  When looking at the main program, the sensor green concnetric circles do indicate the rf it being sent.  Blue lights on the Macro icon button indicate the macro is triggered.  But no rf is sent to the lamp.  However if I mouse/click the blue Macro button, the lamp comes on. 

Latest software upgrade - latest products.  Awaiting system expansion if this ever works.  THIS SHOULD BE #1 PRORITY

Meanwhile, I won't order more product until this gets solved. 

[dra_rich]

Hey Paul,

I'm having the same problem, only mine seems to occur whether or not I have conditions set for the macro (merely having Smart Macros installed seems to do it).  Same story: the sensor shows activity, the RUN MACRO button flashes, but no RF is sent.  Very frustrating.  The activity log for both the macro and the sensor show the signals being received and sent, but no go.

--Dave

[MacGyvr]

Same situation...simple macro to turn on a light as a test.  Can trigger it from the software by clicking the blue button, works fine.  Click the trigger on a remote and the blue square flashes, but nothing happens.  When is this going to be fixed?

[mrmikeman]

I had the same problem when I installed my software today but found a work-around.  Just select "Run from PC" at the bottom of the macro.  Then it will work always.

Obviously the PC has to be on and controlling...

Mike

[bud]

I have found that many macro problems can be solved by inserting a 1 second delay at the start of the macro.
Also, having the batteries in creates additional problems.  If you don't need timers, leave the batteries out, solves many problems!

One difficulty, my CM15 is plugged in away from my computer, when I move it to change programming, I lose the flags (the batteries back them up), but this is a minor problem for me.

[JMac]

The 1 second delay worked for me too!

[robandcathy]

I think i have the same problem, light is set to a12 trigger is set to d1 with time conditions and can not get it to work for the life of me, also tech support only works with email which sucks a**

[-Bill- (of wgjohns.com)]

Check under "Hardware Configuration" for "Transceived House Code(s)" and make sure the house code the RF device (sensor or remote) is set to is checked.  I have a RF remote set to house code B.  I find that if I uncheck B under "Transceived House Code(s)" the macros set to trigger on "B1 ON", "B1 OFF", "B2 ON", "B2 OFF", etc. don't fire.  Interestingly, the blue macro buttons for "B1 ON" and "B1 OFF" both flash when I press the "B1 ON" remote button, but nothing happens.  When I press the "B1 OFF" remote button, the blue macro buttons don't even flash.

As I have posted elsewhere, I prefer to have all "Transceived House Code(s)" checked unless it obviously causes problems.

[yvanmarl]

"1 second runaround" and "Run from PC" are both fix that work well for me.

As my PC stay on all the time, it does not bother me. Except for one thing: I'm new to home automation since last week. I thought that this "old"  technology was a lot more debugged then that. I'm not a rocket scientist, but if 1 Go / sec can made it over a hair thin optic fiber, what it is so difficult to send some bytes over no 14 gauge wire?

Just joking...

Martin

[DeltaNu1142]

"1 second runaround" and "Run from PC" are both fix that work well for me.

I was getting aggravated with this same problem...  until I saw this thread.  I'm still aggravated that this doesn't work as I assume it's intended to.  I put in the 1-second delay & am now running the macro from my PC, and it works, but what a bother!!  Any news on a fix for this?!?

[DeltaNu1142]

Summary/update:

I'm able to trigger my macros with RF IFF:
1) I insert a 1-second delay as the first step in the macro, AND
2) the macro is running from the PC

The good news is, AHP doesn't have to be running; in fact, I was able to trigger the macro when I was logged off of the PC (WinXP).  It'd be nice if I could run everything from the CM15A though.

[ArtClark]

This will sound strange, but, I am sure you are hitting the "OverRun" problem in the CM15.  IT is VERY easy to ask it to send more commands than can be sent.  The 1 second delay can help, but try pushing it to 2 where needed.  The PC interface is so slow (Why, I couldn't say...) that it has much less trouble with this.  If you set a simple macro to send "Off" to several modules, and watch the activity monitor, it Will SAY that it sent the command.  It actually didn't.

This is a little confusing, but I have tested this and it's true.

I.E.  Send via Macro in Interface   A1 off, A2 Off.    You'll see  A1, A2, A off.  You will usually get the result of only the A2 and A off.  A1 will still be on.  PC based Macro will work,  Interface macro won't.  Add a delay before and after the A1 off and you will get  A1, A off, A2, A off and all works.   

I'm sure that this is the CM15 processor is a little too fast for the PLC interface inside the CM15.  Stay aware of the required delays and all works great.