IndyMike

Chuck, You and I are doing very similar things (right down to using Keypad E for alloff/allon). While I don't see anything wrong with your "alloff LED trigger", I'm using inverted logic (or's) and things appear to be working (actually this is shameless plagiarism of an example from MikeB - thanks Mike) . The following is how your trigger would look with the logic inverted. if Status 'Basement Playroom Lights (loa' > Off or Status 'Dining Room - DECK' > Off or Status 'Dining Room - LIGHT (load)' > Off or Status 'Dining Room - YARD' > Off or Status 'Dining Room Ceiling Fan (load' > Off or Status 'Kitchen Ceiling Lights (load)' > Off or Status 'Kitchen Sink Light (load)' > 40% or Status 'Living Room Ceiling (load)' > Off or Status 'Living Room Lamp (load)' > Off or Status 'Office Ceiling Light (load)' > Off Then Wait 2 seconds Set Scene 'ALL OFF LED' off Else Wait 2 seconds Set Scene 'ALL OFF LED' on

evarsanyi, I've gotten around this in the past with another application (ActiveHomePro CM15a) by using user settable "flags" or X10 "dummy modules". This allows your second program to test the flag or dummy module state prior to executing. I'm a newbie with the ISY-26 (2 days), but from what I can see neither of these options exist. Possibly a suggestion for future releases? As upstatemike indicated, I believe you need a separate qualifier for your RF2 trigger.