Please login or register.

Login with username, password and session length
Advanced search  


The Buster PiX10Hub is here! Created by the Community, for the Community.:)% #:)

Author Topic: Advice - Reduce traffic via FLAGS & Conditions  (Read 2908 times)


  • Hero Member
  • *****
  • Helpful Post Rating: 32
  • Posts: 522
Advice - Reduce traffic via FLAGS & Conditions
« on: June 29, 2008, 01:22:57 PM »

Sometimes when other commands are executing, a sensor state may get missed by the CM15A - I'm finding that if a macro is firing, I sometimes don't get an OFF from a motion sensor. 

e.g. I have 2 DS10a's in the garage which set a "DOOR OPEN" flag and turn on a light when a door is opened.  I had them test that both doors were closed before turning OFF the light - So each time either sent its CLOSED heartbeat, they'd run a macro to turn off the light.  If it was on, it went off, if it was already OFF, I figured what the heck, another off command won't hurt.  Same thing when opening either door - send the ON command even if it's already on. WRONG - when the OFF macro was running today at exactly the moment my MS14 was sending an RF OFF, the RF OFF never made it to the CM15a.

Since I was using a flag to indicate a garage door open anyway, I just added that condition to the "Closed" and "Triggered" macros - now they only execute when the flag is SET (or not).  4 - to- 6 commands NOT sent every hour or when a door is opened if the light is already on.:)%

Just a piece of advice...
Win-7 - Dell XPS -Automation
VA12a on a dedicated desktop - Video
XTB-IIR & V572RF32

Remote via LogMeIn (FREE) and Ignition | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 All rights reserved.