MikeB

To expand on that further, you could get the black tabletop enclosure to help cut out the light. I don't have one myself, but my understanding is that the black KPL buttons DO NOT let light shine through like the white buttons do, so it might be more appropriate in your bedroom. http://www.smarthome.com/2486pbk.html

As far as I know, later PLM firmware versions have only shown improvements. As for replacing a problematic PLM, I would contact SmartHome and politely explain the issue you are having (lockups during heavy use, etc..).

Check out this thread: http://forum.universal-devices.com/view ... highlight=

I'd use the PLM with the latest firmware, so 61.

Hey Frank - I normally add devices by address. However, with my v1.5 KPLs, it does not work - the ISY gives a 'Request Failed' error. Adding the KPL by the 'Start Linking' command works fine. The v1.6 KPLs, however, don't seem to work at all. At least some of them.

Check the device in the ISY. If it shows as a "LampLinc', then that's your issue. Apparently some v1.6 KPLs are being incorrectly identified as LampLincs. I have one here doing the same.

YES

I believe your problem is that your STATUS OFF program should have ANDs and not ORs. Your STATUS ON program is turning the LED on, but then since one of your devices is probably off the status light gets turned back off.

That's right.... with a separate AC adapter, I bet you could go quite a distance.

It's not any kind of safety issue. Low voltage, no worse than POE. I'm not sure at what distance the voltage drop would be too much. If someone knows the power output of the PLM and the power requirements of the ISY-99, this page should help figure it out: http://www.demarctech.com/techsupport/poecalculate.htm Keep in mind you could always get an RF IR extender as well, and relocate your ISY to a more reliable location. I just saw one at my local Best Buy for $45. Or, if you're going to run a Cat5 anyway, you could use a hardwired IR repeater.

Well thanks for the suggestion. We're all learning here, and I'll often change my programs 3 or 4 times based on other people's ideas and optimizations. That's why I like posting what I'm using for programs. These threads benefit everyone!

Maybe.. but my head is spinning and my programs are working well, so I think I'm going to leave them as-is for now. I'm going to go through mine today as well.

Thanks! That's a good suggestion. Do we know for certain that the order of the conditions matters? Does the ISY evaluate the entire IF no matter what, or does it process the conditions line by line and stop if a line makes it false? I'm all for it.

Maybe I'm missing something, but I don't think that's the case. This code: If ( Status 'KitchenBar1' is not 90% Or Status 'KitchenMain1' is not 50% Or Status 'KitchenTable1' is not Off ) And Status 'KitchenControls1G' is not Off ..will only run the THEN if my status light is on, AND one of the scene contained lights is adjusted. If it's adjusted, the status light will go off and not run again unless the scene is re-activated. So ISY traffic is minimized. This code: If Status 'KitchenBar1' is 90% And Status 'KitchenMain1' is 50% And Status 'KitchenTable1' is Off ..is false any time any of those lights are adjusted. This code: If Status 'KitchenBar1' is 90% And Status 'KitchenMain1' is 50% And Status 'KitchenTable1' is Off And Status 'KitchenControls1G' is On ..is also false any time any of those lights are adjusted. Adding an additional conditional doesn't make it any less likely to be false. Unless I'm not grasping what you're suggesting? Which is possible, because I'm pretty tired.

No, because I'm also checking to see if the KPL button is on. If it's not on, then the progam won't run.

I believe that would work, but the ISY would process this program any time a light contained in that scene was adjusted.

You must use a PLM with either ISY.

Thanks for the reply Jeff. What you say makes sense, but unless I'm missing something there's no way to for me to do that without creating some redundant powerline traffic (which I'm always trying to avoid). The basic premise is that the only way my scene is set is if the appropriate KPL button is pressed. If that button is pressed, then it is already on. That's why I focus on turning that button off rather than turning it on. I believe the code you have here would work OK: If Status 'KitchenBar1' is 90% and Status 'KitchenMain1' is 50% and Status 'KitchenTable1' is Off Then Wait 2 seconds Set Scene 'KitchenBreakfastStatus' On Else Wait 2 seconds Set Scene 'KitchenBreakfastStatus' Off The only thing I don't like is that if this scene is set, then I've pressed the KPL button and it s already on. Your code above would then, 2 seconds later, send a 2nd on command to it. I could add a check to see if the button is on already, like this: If Status 'KitchenBar1' is 90% and Status 'KitchenMain1' is 50% and Status 'KitchenTable1' is Off and Status 'KitchenControls1G' is not On Then Wait 2 seconds Set Scene 'KitchenBreakfastStatus' On Else Wait 2 seconds Set Scene 'KitchenBreakfastStatus' Off ..but then the program would loop and my status light would keep turning on and off. I do see what you're saying though.

Funny... I have that same problem here at home.

My KPL Dimmer v1.5s show as v.2A as well. Michel once told me the version # that the ISY shows is what the device reports when its firmware is queried. Not sure why SmartHome maintains 2 separate version #s, but it does make it a bit confusing.

Just a quick followup. I've combined my scene on and scene off programs into one. Here is an example: If Control 'KitchenControls1G' is switched On And Control 'KitchenControls1G' is not switched Off Then Set Scene 'KitchenBreakfast' On Else Set Scene 'KitchenBreakfast' Off I still have my status program which keeps the LED accurate: If ( Status 'KitchenBar1' is not 90% Or Status 'KitchenMain1' is not 50% Or Status 'KitchenTable1' is not Off ) And Status 'KitchenControls1G' is not Off Then Wait 2 seconds Set Scene 'KitchenBreakfastStatus' Off Else - No Actions - (To add one, press 'Action')

Thanks for this code Jeff! I was currently doing my fast on/off triggers with 2 separate programs. Didn't realize I could do it with 1.

Hey Rand - That's what I had thought too, but it's not the case. I run the following code for my front door lights: If From Sunset + 20 minutes To 9:30:00PM (same day) Then Set Scene 'FrontDoor' On Else Set Scene 'FrontDoor' Off I can turn them on any time of the day, and they will stay on. I believe the conditions are evaluated only twice (at the start time, and at the end time) - not continuously.

...or, something like this: If From Sunset + 20 minutes To 9:30:00PM (same day) Then Set Scene 'FrontDoor' On Else Set Scene 'FrontDoor' Off This might be easier if you're using sunset or sunrise as a start/end point, and a fixed time as the other point.

I confirmed that this seems to be correct. I can set it to run, and it will run and stay running (since the THEN statements are continuous). But, if the ISY is rebooted it needs to be started manually. Setting the program to 'run at reboot' causes the ISY to re-start the program when the ISY is rebooted, and it works like I hoped. Thanks for the suggestion Frank! This feels like a 'cleaner' solution than putting a time value under IF since I want the program to always run.