Print

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

[ignis]

I have a macro that is triggered by a motion sensor on J5. It is supposed to trigger my chime module on K14 and then wait two minutes before being triggered again.

I've noticed the macro is very inconsistently working. However, if I manually kick-off the macro, it works fine.   

Thoughts?

[Puck]

ignis: Are you seeing that the Motion Sensor is always being received in the Activity Monitor, and that the Macro is being executed?

If all looks well, you could have a problem with the PLC signal not reaching the Chime reliably.

[TakeTheActive]

I have a macro that is triggered by a motion sensor on J5... ...I've noticed the macro is very inconsistently working. However, if I manually kick-off the macro, it works fine.   

• What do you have installed for receiving RF?
  .
• Have you mapped out all of your circuits?
  .
• Do you own an X10 Signal Strength Meter?
  .
• How long have you been using X10 products?
  .
• [/color]MAP / MEASURE / CORRECT
  

[/b]

[ignis]

I know it's not an RF receive problem, because I can see Active Home running the macro (The macro highlights in blue and Active Home actually appears to send the command to activate the chime module) each time there is actually motion. However, the chime module only sometimes actually triggers. But, if I manually click on the macro, it all works fine.

Yes, I have it all mapped out and am not overlapping anywhere.

I do not own a signal strength meter.

Been aware of X10 for years and am fairly educated on the topic, but just recently started to use the products in my own home.

[Puck]

Are you using any conditions?

Can you post a screen shot of your macro, or type what it contains? Macros can sometime do some strange things, so it's good to physically see what you are doing.

Also, it will help to state what version of AHP you are running, as well as what plug ins, and what OS you are running on.

[ignis]

I'm not very good with inserting images into these forums. Don't I need my picture hosted somewhere on the web 1st?

Anyways, I am using one condition. That is just to only allow the chime from 7:00 a.m. to 9:30 p.m. As I mentioned, I can see the macro light up and try to run when there is motion, but I just don't always here the chime. But, whenever I click on the macro myself, the chime works fine.

I'm using AHP 3.204 with Smart Macros on an XP machine.

I do appeciate all of your thoughts and suggestions.

[Puck]

OK, just in case your not aware of this, when you manually press the macro button it ignores the conditions and just runs it. So that's why it always works that way for you.

So the first thing to do is double check your condition. 

Is the macro saved in the CM15A or on the PC?

Does your macro contain anything other than just sending the ON signal to the Chime?

P.S. When you make a post, you can select "Additional Options..." to attach a picture, or reference it from a website.

[ignis]

Thanks! Here is the picture.

I didn't realize manually pressing the macro bypassed the conditions. That's a very useful thing to know!

[Puck]

Your macro looks fine. However, the 2 minute delay won't do anything.

You originally stated you want it to wait two minutes before being triggered again. As it is now, you could end up with multiple triggers. Maybe use a Flag to prevent it from retriggering until the two minutes are up. An example is below. If your not familiar with Flags, you can learn more here: how to use flags

Sometimes adding a small delay (even zero-seconds) before a command in a macro helps to. (But be careful when you have Elses  ).

[protv]

I have the same problem with a macro set to transmit a RF command to a TM751 transceiver. My macro includes just the trigger command (M8 ON) -> send RF D8 ON. Everything works if I execute the macro from the AHP GUI but not when I send a M8 ON command via a palm remote or even via a wired mini console. The log is showing receiving the M8 trigger but the macro doesn't "move". I can even see it flickering on the screen when a put the M8 ON command on the wire, but it is not executing.
What am I missing ?

[Puck]

Maybe try a small (1 or 2 second) delay prior to sending the RF command.

Because your are triggering the macro via an RF Receive signal, and the macro is to Transmit an RF signal, the CM15A may be having a difficult time doing it immediately.

I do believe the palm pad sends the signal 2 or 3 times with a single button press; so most likely it is still sending when the macro triggers, thus causing the macro to not be able to execute.

[protv]

I experience the same issue when sending from a wired desk controller. I think I might have missed downloading the macros into the interface. I thought this is done automatically when you check "store in the interface".

One additional question: If I use these RF transmitting macros to "bridge" to a TM751 via radio signals, can I leave the CM15A to transceive the original house code without creating a collision with the TM751 ?
My "scenario" is: Use house code M to trigger the macros and transceive via TM751 and CM15A to house code D that is programmed into my switches. Send trigger in the house code M from wired desk controllers and in the house code D from wireless controllers.

[Walt2]

... and transceive via TM751 and CM15A to house code D ...

So, you have your TM751 set to house code "D", and you have house code "D" enabled as a CM15A transceiver in the AHP hardware setup?  BTW, transceiver is different function than monitored house code.

[Puck]

Never have the same housecode transceived by more than one device.

Also, if you are not aware, a housecode does not have to be transceived to trigger a macro that is stored in the interface.

[-Bill- (of wgjohns.com)]

I experience the same issue when sending from a wired desk controller. I think I might have missed downloading the macros into the interface. I thought this is done automatically when you check "store in the interface".

No.  Checking store in interface does not actually download the macro to the interface.  It just tells AHP which macros should be stored in the interface then next time you "Download Timers and Macros" (under the "Tools" menu).  Also, before downloading to the interface, it is a good idea to "Clear Interface Memory" (also under the "Tools" menu).