Articles | Forums | About | Contact | X10.com
November 22, 2009, 11:07:44 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: We want to know how you use your X10 system! Share your story in the Product Review Board.
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Single Trigger Macro Using a Status Flag  (Read 7578 times)
Puck
Community Organizer
Hero Member
**

Helpful Post Rating: 162
Posts: 1782


« on: March 10, 2008, 05:09:10 AM »

Narrative:
AHP 3.206

Runs from the interface or PC (users choice).

Many new users to AHP ask for help on preventing a macro from re-triggering for a period of time. Presented here are two methods of performing this task using a Status Flag. The status flag can be set/cleared and used as a condition for a macro to execute.

The examples shown are to allow a chime to occur just once during motion detection. This is to prevent a chime occurring every few seconds during continuous motion detection.

Motion Detector's Address: A2 Frontdoor Motion


1) For using the Motion Detector's ON & OFF signals, create the following 2 Macros:

     Macro Name:
      MotionStart

     Trigger:
      A2 ON

     Conditions:
      Flag [2] Clear

     Action(s):
      Set Flags [2]
      Chime ON


     Macro Name:
      MotionStop

     Trigger:
      A2 OFF

     Conditions:
      (none)

     Action(s):
      Clear Flags [2]


2) For using just the Motion Detector's ON signal and a fixed delay, create the following Macro:

     Macro Name:
      FrondoorMotion

     Trigger:
      A2 ON

     Conditions:
      Flag [2] Clear

     Action(s):
      Set Flags [2]
      Chime ON
      Delay 60 seconds  (this value can be any delay required)
      Clear Flags [2]
Logged
PrimeGuild
Full Member
***

Helpful Post Rating: 0
Posts: 44



WWW
« Reply #1 on: March 11, 2008, 12:32:31 PM »

Thanks Puck. This is useful stuff. I was really annoyed when my chime kept chiming while the pizza delivery boy just waited for @ my front door.
Logged
PrimeGuild
Full Member
***

Helpful Post Rating: 0
Posts: 44



WWW
« Reply #2 on: March 31, 2008, 08:36:04 AM »

On second thought, I implemented this logic, and it did appear to work initially, but then later on it just stopped working. My door bell now never gets triggered. I tried all combinations, and finally I took out the Flags and then it started working, but then I am not able to delay the door bell.
Logged
Puck
Community Organizer
Hero Member
**

Helpful Post Rating: 162
Posts: 1782


« Reply #3 on: March 31, 2008, 08:48:03 AM »

On second thought, I implemented this logic, and it did appear to work initially, but then later on it just stopped working. My door bell now never gets triggered.

This could only happen if the flag didn't get cleared from an A2 OFF signal. Did you check your Activity Monitor to verify that A2 OFF was received?


Update:

Having read your other posts today, in one you stated using multiple transceivers. Multiple transceivers along with the CM15A/AHP can cause a system to be unreliable, so it may not be Flags that are the cause of your problems.
« Last Edit: March 31, 2008, 09:29:01 AM by Puck » Logged
IPS
Jr. Member
**

Helpful Post Rating: 0
Posts: 16


« Reply #4 on: October 14, 2009, 03:44:50 PM »

I tried this macro. My results were the same as those of Primeguild. I removed the first part of the first macro and it works ok. first part cancells the macros so nothing happens.
Logged
Pages: [1]
  Print  
 
Jump to:  

X10.com | About X10 | Careers at X10 | Privacy Policy | Affiliate Program
X10 Sentinel | ActiveHomePro.com | X10VideoSender.com | iPartyMini.com | X10Wiredhome.com
X10WirelessHome.com | Google Video Remote Control | Google Pack Remote Control
X10 Contractor Program | X10 Security Systems | X10 Mini Timer
© Copyright 2006 X10.com All rights reserved.
Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!