IndyMike

Has, I ran a quick test on the ISY Dim command. It does work, but it's probably a bit different from what you're accustomed to. The standard X10 Dim sequence is a mess (I'd like to use a more descriptive word but it would probably be bad form). It consists of an House/address code followed by a stream of bright/dim commands (ex: A1, bright,bright,bright,bright). The bright/dim commands are repeated continuously (no gaps) until the correct level is achieved. This command sequence is very hard on repeaters and prone to noise problems. The ISY output does not concatenate the "bright/dim" commands. It treats each as separate command with it's own House/unit code (see the example below). This sequence is far easier for receivers/repeaters to interpret. The down side is it takes a LONG TIME to transmit. The following is a test that I ran to check the X10 communication. The ISY triggers on a X10 A12 ON received from my CM15a. The ISY then turns on my lamp (100%) and executes 15 Dim commands (75%). From the log below, this took roughly 31 seconds to transmit. A standard X10 Dim sequence would take on the order of 4-5 seconds. I suppose we could ask the ISY folks to implement a DIM*n command, but to be honest, I avoid them because of the problems they can cause. I would much prefer the ability to execute an extended code direct dim. Hope this helps. IM ISY Trigger and Dim Sequence If X10 'A12/On (3)' is Received Then Send X10 'I1/On (3)' Wait 1 second Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Send X10 'I1/Dim (15)' Else - No Actions - (To add one, press 'Action') X10 Transmit sequence received by my CM15a 1007 12/21/2007 11:30:37 pm Receive I1 1008 12/21/2007 11:30:38 pm Receive I On 1009 12/21/2007 11:30:39 pm Receive I1 1010 12/21/2007 11:30:40 pm Receive I Dim 5 1011 12/21/2007 11:30:41 pm Receive I1 1012 12/21/2007 11:30:42 pm Receive I Dim 5 1013 12/21/2007 11:30:43 pm Receive I1 1014 12/21/2007 11:30:44 pm Receive I Dim 5 1015 12/21/2007 11:30:45 pm Receive I1 1016 12/21/2007 11:30:46 pm Receive I Dim 5 1017 12/21/2007 11:30:47 pm Receive I1 1018 12/21/2007 11:30:48 pm Receive I Dim 5 1019 12/21/2007 11:30:49 pm Receive I1 1020 12/21/2007 11:30:50 pm Receive I Dim 5 1021 12/21/2007 11:30:51 pm Receive I1 1022 12/21/2007 11:30:52 pm Receive I Dim 5 1023 12/21/2007 11:30:53 pm Receive I1 1024 12/21/2007 11:30:54 pm Receive I Dim 5 1025 12/21/2007 11:30:55 pm Receive I1 1026 12/21/2007 11:30:56 pm Receive I Dim 5 1027 12/21/2007 11:30:57 pm Receive I1 1028 12/21/2007 11:30:58 pm Receive I Dim 5 1029 12/21/2007 11:30:59 pm Receive I1 1030 12/21/2007 11:31:00 pm Receive I Dim 5 1031 12/21/2007 11:31:01 pm Receive I1 1032 12/21/2007 11:31:02 pm Receive I Dim 5 1033 12/21/2007 11:31:03 pm Receive I1 1034 12/21/2007 11:31:04 pm Receive I Dim 5 1035 12/21/2007 11:31:05 pm Receive I1 1036 12/21/2007 11:31:06 pm Receive I Dim 5 1037 12/21/2007 11:31:07 pm Receive I1 1038 12/21/2007 11:31:08 pm Receive I Dim 5

Thank you Chris! That's a handy time saver. Is this a recent development (V 2.5 or 2.6) or did I just miss it during the Beta releases?

MikeB, I've been using your example for some time now. Thank you, it's been working nicely. After playing with things the other night, it occurred to me that the trigger would be re-evaluated on each status change. The result is multiple on commands to the keypadlinc status button when it's already on. Being an old X10'er I have a mindset regarding excess traffic on the powerline. I've added the following qualifiers to prevent re-triggering of a scene that is already on. Thought I'd pass it along FWIW. 1st Floor status off trigger 1st Floor status On Trigger

OK, I'm wiping some serious egg of my face right now. I just pulled a 4th KPL out of it's box, wired it to a power cord and Tap linked it to the ISY/PLM. No problems-all button changes are recognized by the ISY. Presumably my other KPL dumped it's link table at some point and lost the link to the PLM. Instead of trying a "restore device", I assumed the KPL was different and went for the workaround. Thanks for getting me back on the path.

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.