belias

I'm not 100% sure on order of operations, but I believe the program suggested by Rand needs parenthesis or else any time Motion 2 is switched on, the Scene 'Motion' will also be set to on. Try this: If From Sunset To Sunrise (next day) And ( Control 'Motion Sensor 1' is switched On Or Control 'Motion Sensor 2' is switched On ) Then Set Scene 'Motion' On Else - No Actions - (To add one, press 'Action')

Hi Darrell, Thanks for the fast reply - great support as always! - Brian

Hello, I have a few programs with "IF" statements that should only be evaluated when called by another program. This works perfectly when I set the programs to disabled, however it's a bit of an inconvenience keeping track of which programs should / should not be disabled. (I frequently disable programs for testing, etc.). So...as a more elegant solution, I figured I'd put all of these programs in a folder and set the folder condition to something that never evaluates as true. I assumed this would have the same effect as disabling the programs, however apparently not. The programs in this folder never run - even when explicitly called by another program. So here's the question - is this the way it's supposed to work? If so, it seems a bit counter-intuitive that enable/disable would function differently from a folder condition that evaluates to true/false...but maybe that's just me. In any case, if this is indeed how things are supposed to function, an option to disable an entire folder (or allow programs in a "false" folder to run when explicitly called) would be great! Thanks, - Brian

Hi Michel, Thanks for the quick reply. Is there a way to log the specific program that called the scene? Or to view _all_ program activations (not just the most recent)? Thanks again, - Brian

Hello, I've noticed a few times over the last week that my outside flood lights have been turned on for (what seems like) no reason. I viewed the logfile today in Excel, and I'm looking for a bit of help in how to interpret what caused the lights to come on. I think I've identified the section of the log file (the time is correct): Outside / Driveway - Sensor Status 0% Sun 2010/07/18 02:52:48 PM System Log 0 -14 Sun 2010/07/18 02:52:54 PM System -50001 Scene:Outside / Garage, Entry, Park Floods Off 0 Sun 2010/07/18 03:33:01 PM Program Log 1st Floor Common / Rear Entry Hall Lights [Gar] Status 100% Sun 2010/07/18 03:33:01 PM System Log 1st Floor Common / Rear Entry Hall Lights2 [Kit] Status 100% Sun 2010/07/18 03:33:01 PM System Log Scene:Outside / Garage, Entry, Park Floods On 255 Sun 2010/07/18 03:33:04 PM Program Log Garage / Garage Lights Status 100% Sun 2010/07/18 03:33:04 PM System Log Outside / Parking Flood Status 100% Sun 2010/07/18 03:33:04 PM System Log 1st Floor Common / Entry Hall KPL - Park Flood Status 100% Sun 2010/07/18 03:33:04 PM System Log 1st Floor Common / Entry Hall KPL - Garage Lts Status 100% Sun 2010/07/18 03:33:04 PM System Log Scene:KPL Button Scenes / All Outside Buttons Off 0 Sun 2010/07/18 03:33:05 PM Program Log Scene:Outside / Garage, Entry, Park Floods On 255 Sun 2010/07/18 03:35:49 PM Program Log 1st Floor Common / Rear Entry Hall Lights [Gar] Status 0% Sun 2010/07/18 03:35:50 PM System Log 1st Floor Common / Rear Entry Hall Lights2 [Kit] Status 0% Sun 2010/07/18 03:35:50 PM System Log It looks like the scene containing the flood lights (Outside / Garage, Entry, Park Floods) was turned on at 3:33:04pm - how can I tell what called this? Any help would be great... Thanks! -Brian

Hello, I'm trying to setup a situation where I can call a scene (either on or off) through MobiLinc and this would, in turn, call a program in the ISY. Specifically, turning the scene ON would call the "then" path, turning the scene off would call the "if" path. Ideally, if I had a dummy device (or a spare KPL button or something) this would be easy. Add the "Insteon ON" as a condition. But...I don't have either one of these so therefore my scene is empty - I only need it as a means of communication from MobiLinc to the ISY. You might ask..."Why not just add the program to MobiLinc"? Well, unfortunately my options are more limited here. I can't add it to the favorites the way I want, and "Run IF" or "Run THEN" is much more confusing than my custom names. Any ideas how to accomplish this? Thanks! - Brian

Hi Michel, Thanks for the explanation! -Brian

Hello, I was looking at my event viewer this morning during a query, and I noticed the following "unexpected ack" events. Just wondering if anyone can shed some lights on these - what do they mean? Just a curiosity at the moment... Thanks! -Brian ----EVENT VIEWER---- Sun 05/02/2010 07:24:40 AM : [iNST-ACK ] 02 62 14.73.02 0F 19 00 06 LTSREQ (LIGHT) Sun 05/02/2010 07:24:40 AM : [iNST-SRX ] 02 50 14.73.02 0F.9F.89 2B C0 00 (00) Sun 05/02/2010 07:24:40 AM : [standard-Direct Ack][14.73.02-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 05/02/2010 07:24:40 AM : [iNST-ACK ] 02 62 14.73.02 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Sun 05/02/2010 07:24:41 AM : [ 12 FA 3C 2] ST 0 Sun 05/02/2010 07:24:41 AM : [iNST-ACK ] 02 62 00.00.17 CF 13 00 06 LTOFFRR(00) Sun 05/02/2010 07:24:41 AM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sun 05/02/2010 07:24:41 AM : [iNST-SRX ] 02 50 14.73.02 0F.9F.89 2B 2E 00 (00) Sun 05/02/2010 07:24:41 AM : [standard-Direct Ack][14.73.02-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 05/02/2010 07:24:41 AM : [ 13 32 2D 1] ST 255 Sun 05/02/2010 07:24:41 AM : [iNST-ACK ] 02 62 00.00.1D CF 13 00 06 LTOFFRR(00) Sun 05/02/2010 07:24:41 AM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sun 05/02/2010 07:24:42 AM : [ 13 32 2D 2] ST 0 Sun 05/02/2010 07:24:42 AM : [iNST-ACK ] 02 62 00.00.17 CF 13 00 06 LTOFFRR(00) Sun 05/02/2010 07:24:42 AM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sun 05/02/2010 07:24:42 AM : [ 12 E3 B0 1] ST 0 Sun 05/02/2010 07:24:42 AM : [ 12 E3 B0 1] OL 255 Sun 05/02/2010 07:24:42 AM : [ 12 E3 B0 1] RR 28 Sun 05/02/2010 07:24:42 AM : [ 12 3C A5 1] ST 0 Sun 05/02/2010 07:24:42 AM : [ 12 3C A5 1] OL 255 Sun 05/02/2010 07:24:42 AM : [ 12 3C A5 1] RR 31 Sun 05/02/2010 07:24:42 AM : [ 13 45 7E 1] ST 0 Sun 05/02/2010 07:24:42 AM : [ 13 45 7E 1] OL 255 Sun 05/02/2010 07:24:42 AM : [ 13 45 7E 1] RR 28 Sun 05/02/2010 07:24:42 AM : [ 12 8B 19 1] ST 0 Sun 05/02/2010 07:24:42 AM : [ 12 8B 19 1] OL 255 Sun 05/02/2010 07:24:42 AM : [ 12 8B 19 1] RR 28 Sun 05/02/2010 07:24:42 AM : [ 14 73 2 1] ST 0 Sun 05/02/2010 07:24:42 AM : [ 14 73 2 1] OL 255 Sun 05/02/2010 07:24:42 AM : [ 14 73 2 1] RR 28 Sun 05/02/2010 07:24:43 AM : [iNST-ACK ] 02 62 00.00.1D CF 13 00 06 LTOFFRR(00) Sun 05/02/2010 07:24:43 AM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sun 05/02/2010 07:24:45 AM : [iNST-ACK ] 02 62 00.00.16 CF 13 00 06 LTOFFRR(00) Sun 05/02/2010 07:24:45 AM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13 Sun 05/02/2010 07:24:46 AM : [iNST-ACK ] 02 62 14.73.02 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 06 (00) Sun 05/02/2010 07:24:46 AM : [iNST-SRX ] 02 50 14.73.02 0F.9F.89 27 2E 00 (00) Sun 05/02/2010 07:24:46 AM : [standard-Direct Ack][14.73.02-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sun 05/02/2010 07:24:46 AM : [iNST-ERX ] 02 51 14 73 02 0F 9F 89 11 2E 00 01 01 00 11 20 20 1C FF 7F 31 00 00 00 00

When you send an ON or OFF command to a KPL sub-button, you're really only changing the status of the LED. The trick is, in order to call this change from a program, the KPL sub-button must be in a scene. Here are the basic steps: Create a new scene, let's call it 'KPL-Button B Scene'. Drag the 'KPL-Button B' into the scene as a responder (it should be the only thing in the scene). Now create a program: If Control 'KPL-Button B' is switched On (notice this is the device, not the scene) Then Wait 30 sec Set Scene 'KPL-Button B Scene' Off (notice this is the scene, not the device) That should do it. Good luck! -Brian

Hi Michel, Sure, here you go: 1. Start with a factory reset KPL (I'm using v.36, 8-button, dimmer). 2. Make sure the local load and all sub-buttons are off. 3. Tap the set button (clear button at bottom) once (KPL will beep) 3. Press and hold a sub-button for 10 seconds (KPL will beep) 4. Press and hold "A" (load) button for 10 seconds (KPL will beep) Now the local load will turn fully OFF any time the sub-button is turned ON. Hope this helps, -Brian

Hi Michel, My other v.36 KPL is also an 8-button (2486DWH8), I simply have it programmed to operate in 6-button mode. I have tried the steps to make sure it wasn't just a fluke, and it works on this 2nd KPL - but unfortunately I can't provide any useful information on how a "real" 6-button would operate. Perhaps someone else with a newer 6-button could give it a try? As far as the info. stored in the memory locations - perhaps it would be different if read from a KPL with this "feature" working. Is there a way for me to send you a full "device read" of my KPL with the local-off working? Is that useful? Thanks, -Brian

Hi Michel, Whew! OK...I think the missing link for me was that you're not able to reproduce it even with the manual steps - now I'm on the same page. I am using an 8-button dimmer V.36 KPL (2486DWH8 v. 5.2 on the label). I have a second KPL that's identical (but running in 6-button mode), and a V.2C and a V.2D...so I can't be much help in testing. Perhaps its a difference between the relay and the dimmer models? So, what happens when you assign a very low on-level to the local load when using a relay KPL (I've only used dimmers)? Does it switch the load and indicator off? Lastly...I'm wondering if this is a change that came about with the updated SH firmware allowing units to join a scene in the "OFF" mode. I think that's what I did using the steps from the previous post (but honestly I may have also just stumbled upon a sequence that worked). Just a thought... Thanks again Michel! -Brian

Hmm.....this suggests that programming via the ISY and programming via the KPL buttons should give the same results. But this isn't what I'm seeing. Using the steps from my 4/17 post, I can easily (and reproducibly) make a sub-button turn the load COMPLETELY off (i.e. load and KPL-A indicator completely off). Using the ISY, the closest I can achieve is the low on-level (with the KPL-A indicator still ON). I feel as though I'm missing something very basic here...like you realize that local programming achieves the desired result (local load fully off by sub-button), but at the moment it's just not possible to program this action using the ISY... If I missed that along the way, my apologies for drawing this out... Thanks yet again, -Brian

Hi Michel, Sorry for my confusion on this, let me make sure I'm on the same page as you. It sounds like this "local load off with sub-button" problem isn't an issue when the KPL is programmed locally (as I discovered and became momentarily excited...). The problem, then, lies in being able to replicate this programming via the ISY (or by Insteon commands in general)...correct? As far as your question on toggle state - I may have changed it somewhere along the way for testing, but when I realized that my "local load / sub-button" functionality was lost I made sure everything was set as it was orginally (local load toggle, scene sub-buttons set to non-toggle on). Still, the ISY behaves as you would expect, forcing the local load to 1% as the minimum value. Thanks again! -Brian

Well, after doing some work on various scene settings, etc. I somehow managed to break my miraculous settings that allowed my KPL load to be turned off when a sub-button is switched on. For whatever reason, my ISY now behaves as expected and insists that I program a level > 0% for the KPL load (from a sub-button). I'm not sure how I got it to work the first time from the ISY - I remember the dialog box popping up about "try using a low level instead", but when I dismissed the popup, the KPL-load level remained at zero and it worked. OK - now on to the useful part....I figured out how to replicate this action at the KPL itself (proving that at least I'm not completely crazy...). Here are the steps: 1. Start with a factory reset KPL (I'm using v.36, 8-button). The local load and all sub-buttons should be off. 2. Tap the set button once (KPL will beep) 3. Press and hold a sub-button for 10 seconds (KPL will beep) 4. Press and hold "A" (load) button for 10 seconds (KPL will beep) Now the local load will turn fully OFF any time the sub-button is turned ON. This is useful in my situation because the local load is ceiling lights, which I want to be completely off when I press "Button G" for the sleep scene. Hopefully this is helpful in the next step of (perhaps) getting the ISY to be able to program this action by simply setting the slider all the way to zero - at least for the newer KPL's. Also - if it would be useful - I'm happy to send along a backup that I made from a few days ago when this was setup and working through the ISY (i.e. I was able to set the slider to full zero). Again - no idea what changed between then and now. FW is still the same at 2.7.14RC1. -Brian

Michel: Yes - that's exactly the issue - summed up in far less words than my post! Somehow it's comforting to know that this has frustrated others as well Oberkc: I think it is possible to configure various devices on/off using a single "ON" command from a controller. For example, if you set up a scene with a RemoteLinc as the controller and a few different SwtichLincs as responders, you can then click on the RemoteLinc and adjust the sliders for the various scene devices to any level (including full off). Now press the RL "on" and some devices will turn off while others turn on. Regarding doing this same thing within the KPL, I think the ISY handles this differently. Using the ISY it's possible to create a scene as I described in my previous post where KPL Button-B "ON" can turn off KPL Button-C (they have to be in the same KPL). I think, however, that what the ISY is actually doing is setting mutually exclusive relationships (as you described), but I (as the end user) simple see it as a controller/responder link. I'm a relative newbie to Insteon, so if I got that wrong - please correct me. So far I've come up with a fairly small program set to correct the ISY buttons (using status checks, etc) when the scene is initiated from outside the KPL (i.e. we don't have the advantage of MA buttons). If I can get it working smoothly I'll post my general idea in the how-to section. God knows, I've benefited from enough of other people's work! Thanks, -Brian

Thanks for the replies! I didn't do a good job of explaining this one...my apologies... oberkc: You are right - this does work. However, in my situation that means a program would have to run to update each of the 8 KPL indicators every time I change a scene using MobiLinc, etc. The problem is that there's much more flexibility in implementing a scene (involving KPL buttons) when the scene is triggered by a KPL button-press. When the same scene is triggered by the ISY, some of that flexibility is lost and my KPL no longer represents device status correctly. In other words, if I create a scene with all 8 KPL buttons and a few SWL's; I'll set one of the KPL buttons (say Button C) as the controller. Now I can be quite flexible: Clicking on "Button C" in the scene, I can set the SWL's as desired and all 7 KPL buttons to either "On" or "Off" individually. So now when I walk up to the KPL and press "Button C", some KPL indicators turn on and others turn off as programmed, and the SWL's turn on/off as programmed. Beautiful! However, let's say I want to invoke this same scene either through an ISY program or through MobiLinc. Now I lose this control over the KPL buttons - I can either turn them all on or all off. So, now I have a mismatch between what's actually on and what the KPL shows is on. My goal is to figure out some clean way to manage this issue such that the KPL always correctly shows the scene / device status regardless of whether it's invoked by a button-press at the KPL or through an ISY program or by MobiLinc. By "clean" I mean that I'd prefer it to be an instantaneous update with minimal Insteon traffic (hey, I'm wishing here...). I think I have something figured out with a small collection of programs...but I thought I'd throw it out there in case someone else has already done the leg-work. Thanks! - Brian[/b]

I'm looking for some advice on controlling scenes from the ISY that involve KPL sub-buttons. Here goes... I have a KPL where a few of the sub-buttons are set up as a controller for other buttons on the same KPL (i.e. in a "scene" type configuration). In other words, I have scenes setup in the ISY with 1 KPL button as the controller, and the remaining 7 as responders. Clicking on the one controller (in red), I can set the status of the 7 remaining(blue) buttons. This works perfectly when standing at the KPL - all devices and sub-buttons work as programmed. The problem comes in with trying to execute this same scene directly from the ISY (either through a program or through MobiLinc, etc.). Given the limitation of not being able to directly control KPL sub-buttons from the top-level scene (i.e. clicking on the scene title next to the scene icon), I end up with the KPL indicators completely out of sync. I'm wondering if anyone has some suggestions for how to deal with this. One thought was to make a program that looked for the status of various lights, and when it matched up with a specified 'scene', then it would adjust the KPL indicators. However, this results in the KPL indicators turning on/off one-by-one as the program runs, and results in a lot of Insteon traffic for 8 buttons; it also runs unnecessarily when I use the KPL to set the scene. Is there some way that's a bit cleaner to accomplish this? Ideally, I'd like the scene as activated by the ISY to behave identically to the scene as activated by a KPL button-press (all indicators change immediately, etc.). P.S. Out of curiosity, why is it that the PLM (or the ISY?) isn't able to directly control KPL buttons? I ask because if I look at a scene with, say, 3 KPL's and 1 SWL, the 3 KPL's can control each other's sub-button status (i.e. on, off). Why can't the ISY simply mimic this action? Judging from previous posts, I realize this is a common issue and I think it's an Insteon limitation...just looking for a bit of clarification in my own understanding... Thank you! - Brian

Hi Rand, Thanks for the quick reply - I missed that the "last run" is specifying an exact time, and not a time range... I think I'll simply use the wait command with the "OHD Open" program to set a flag after 15 minutes. Then I can clear the flag with the "OHD Close" program. The folder can then simply evaluate whether this flag is true. I think this is what you're suggesting... Thanks! - Brian

Hello, I'm trying to come up with a program that enables my 'OHD Alert' folder under the following conditions: 1. One or more garage doors are open 2. The door(s) have been open for over 5 minutes 2. It's dark outside Here's what I have so far: OHD Alert Folder If Program 'OHD Open' is True And From Sunset To Sunrise (next day) And Time is Last Run Time for 'OHD Open' + 5 minutes Then Allow the programs in this folder to run. OHD Open (not located in a conditional folder) If Status 'Garage / OHD-1 Sensor' is Off Or Status 'Garage / OHD-2 Sensor' is Off Then Set Scene 'Garage / OHD Buttons (KPL Indicators)' On Else - No Actions - The 'OHD Open' program works perfectly - the KPL indicators are always on when 1+ door is open, and off when all doors are closed. The problem is that many times the 'OHD Alert' folder does not enable as expected. Last night was a good example and I grabbed screen shots of the Admin Console before playing around with the program. The first shows the program summary display - it shows the time is definitely between sunset and sunrise, the status of 'OHD Open' is true, and the last run time for 'OHD Open' is well over 5 minutes ago. Yet for some reason, the 'OHD Status' folder still evaluates to "False". The second is the screenshot of the 'OHD Alert' folder program (in case I'm missing something). Program Summary: http://dl.dropbox.com/u/2382226/1.png 'OHD Alert' Program: http://dl.dropbox.com/u/2382226/2.png Any thoughts would be great... Thanks! -Brian

I am sure...I'll send you a PM with a video. I'm amazed because it works perfectly...instantaneous response as you'd expect with a simple group command. And the setup is clean - since it's all managed from the ISY. Now, if I could get a KPL that lets me flash an indicator or repeatedly sound the "beep", I'll be truly happy -Brian

Just reading a bunch of posts this morning and I thought I'd throw in my two cents on the KPL local load / sub-button topic: I have a new (v.36) 8-button KPL that is able to turn off the local load completely from a sub-button (no programs, only a scene built from the ISY). I didn't think it was possible (given the previous posts and the warning in the ISY software), but sure enough it works great. Apologies if this has been described previously, but I didn't see it. Here's my setup... Button A: Local load, controls overhead lights Buttons B, C, D: Nothing special, each linked to a different SWL Buttons E, F, G: Controls various scenes that involve turning Button A (and the local load) on and off; the scenes ensure that only one of these three is on at a time Button H: Not used Buttons E,F,G set up as Toggle On. No local grouping on the KPL is used; no local programming on the KPL is required. In the ISY, I created 3 scenes (one each for button E,F,G). In each scene, all 8 buttons are present with one (E,F,G) being the controller. On the main screen for each controller, I set "KPL Button A" to 0 with a ramp rate of 0.1s (or set to the desired brightness). Then set the remaining KPL buttons to the desired state. Now hit button E,F,G and it works exactly as intended. The local load switches completely off (lights off, KPL indicator off) and it does it immediately without the delay associated with a program. Hit a different button and (depending on the scene settings for that controller), Button A and the local load turn on perfectly. I haven't tried this on my older KPL's (no need), and I would assume that it's not possible. Regardless, I was pleasantly surprised when I tried it on this one... -Brian

Hi Michel, I'm not sure what change, but after the upgrade to 2.7.14, the I/OLinc's are now correctly operating in "Momentary C" mode. When I send an "OFF" command, only I/OLinc's attached to the OPEN garage doors trigger. This is exactly what is supposed to happen. Previously, it had been operating the same as "Momentary A" - where an "OFF" command triggered the relay regardless of the door position. So...not sure what changed...but thanks! As far as the LED Brightness, the SWL I tested is v.38 and it did not work. It's not a huge concern for me, since it's easy to change locally - but I thought I'd mention it.... If I want to start from scratch from these KPL's - it is sufficient to perform a factory reset of the KPL, then do a "Restore Device" from the ISY? Not sure if it's still relevant - but here are a few answers to your questions regarding the I/OLinc in Momentary C: 1. Yes - sensor status is correct (and updates correctly). Query is also correct. Relay (as we know) does not report at the end of the momentary. 2. Yes - I/OLincs are responders, and the 3 KPL's (with the "Overhead Door Close" button) are controllers. Now working perfectly - KPL illuminates if any one of the 3 doors are open (by program) and any open door closes if the button is pressed (by scene linking). 3. Now working as described above. Thanks again for all the help and an awesome product! -Brian

upstatemike: Thank you - that's it! There must be an Insteon command for that, because I was able to do it remotely previously - but that's easy enough to apply at each KPL. Perfect! Michel: I tried updating to 2.7.14 RC1 and the LED brightness issue remains. I also tried adjusting the LED brightness on an SWL v.38 and it also doesn't work. All other settings (local ramp rate, local brightness, joining scenes, etc.) work flawlessly. Thanks!

Hi Michel, Certainly no need for apologies - as usual very impressive response times (on Easter Sunday, none the less!). 1. Regarding the 6-button KPL, the functionality I'm describing only effects the backlight. The ON/OFF buttons still work as a toggle, but when it's toggled OFF, the "OFF" backlight is dim. Looking through the documentation for the KPL, it doesn't seem to be mentioned anywhere...making me appear slightly crazy... 2. Regarding the "Momentary C" functionality - here's how I understand it: In this mode, the status of sensor determines if the I/OLinc relay will trigger. This is useful in my situation where I have a KPL button that I want to only close the garage doors which are currently open (I have 3 garage doors, each with its own I/OLinc). So...if I have all of them set to "Momentary C" and send an Insteon "ON" command - only those I/OLincs with an open door will trigger the relay. Those I/OLincs with a close door will ignore the "ON" command. This simplifies things in my setup because I don't need any ISY programming to get my KPL button to simply close any door that happens to be open. It's explained well in the I/OLinc Wiki here (about 1/2 way down in the "Momentary C" sectoin): http://wiki.smarthome.com/index.php?title=2450_Manual I'm fairly confident in this explanation, because I had it functioning correctly using Momentary C prior to switching to the ISY. In other words, my one KPL button sending an "OFF" command shut any of the open garage doors without any need for a separate home automation controller. As an alternative, I can simply use the Momentary A with a few ISY programs... P.S. My garage door uses a momentary trigger and this cycles the opener. Right now (annoyingly) I have the sensor wired to show "Sensor OFF" when the door is open. I need to switch that soon... 3. LED Brightness: My SWL's all show "On Level" only; my 4 KPL's (various revisions as specified before) all show "On Level" and "Off Level". I'll try the different link provided below, and also try upgrading FW to 2.7.14. Out of curiosity - what's the difference between using the URL you provided (www.universal-devices.com.....) vs. my internal link (IP address of the ISY)? Thanks again for the help! -Brian