IndyMike

MikeB, Maybe I missed something very basic here. I have 3 Keypadlincs. All were linked to the PLM/ISY via tap linking. The KPL in question is the only unit where the primary button is connected to a load (not a scene controller). I've never been able to monitor the status of this button, until I added it as a controller of a scene for the dummy AppliaceLinc. Did my KPL simply loose the link to PLM (sometime very early on in my playing).

Hello, After reading numerous posts on the subject, I arrived at the understanding that a Load connected KPL button could not be monitored unless it was also a controller of a scene. My KPL is direct connected to my family room wall lamps. I have no other scenes that I wanted it to control. I just wanted to monitor it's status. I run a trigger on the status of all of my first floor lamps. If any member of my 1st floor scene is on (including the KPL Load) I want to light a secondary button on the KPL. It really frustrated me that I couldn't do this (monitor) with the KPL load button. My work around was to grab an ApplianceLinc that I wasn't using, plug it in with no load, and create a scene with my KPL load button. Not the most efficient use of hardware but it works. Life is good. Last night I came up short on Appliance Modules for Christmas lighting. I was forced to remove my Appliancelinc from the KPL Load scene and move it elsewhere. Here's the rub - The ISY can still monitor the status of my KPL Load button. It's no longer the controller of a scene, but the ISY still hears it. Life is good, but I don't understand why! Here's my synopsis - 1) A KPL load button does not transmit unless it's the controller of a scene. As a result, the ISY can't normally monitor it's status because it doesn't transmit a local on/off. 2) By adding the dummy ApplianceLinc scene (with the KPL Load button as a controller), I forced a link that the ISY could monitor. 3) When I deleted the above scene, the KPL Load button should have reverted back to being "mute" when I activate it locally. How can the ISY still monitor it? Feature, KPL Bug or other? Thanks, IndyMike

After starting to play a bit with X10 commands I was astounded to see options for "Extended Codes" and "Extended Data". However, I can't seem to find a method for specifying the code or data sent. I have a number of Leviton switches (HCM06 and similar) that I would dearly love to use "extended code dim" commands with. Is this a option for future releases or am I missing something in the command structure? Thanks, 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.