oberkc

I have always assumed that this is because of the design of the KPL button. In a world without the ISY and similar type controllers, the only purpose of a secondary button is to be in a scene, since they have no direct control of any load. Interesting. I find scenes one of the more powerful features of insteon.

First things first. When you press your nighttime button, does it go off after a couple of flashes? Do the bedroom and stairs lights go on? Do the rest of the lights go out? Have you solved your original problem?

Do you understand how to configure a keypad button as NON-TOGGLE-OFF?

First, the only way that I know to have a KPL backlight turn off every time you press it is to put it into NON-TOGGLE-OFF mode. My experience is that this works, but apparently there are those who's keypads don't work consistently, so you will have to check that yours perform in this manner. Second, given that you keypad will be sending OFF commands, the only way I know to have lights come on based on receipt of an OFF command is to use a program. If control keypad button is set off then do whatever Third, you have a couple of options to do whatever. You can send descrete commands to each device you want to respond (turn bedroom lights on, turn stairs lights on, turn every other light off) . Alternatively, you can create a scene that includes all the responder devices, and the ON levels at which you want them to respond, including zero (turning off). Then send a scene on command. I would probably opt for the second option.

I find the ISY user manual accurate in this case. It can be found here: http://www.universal-devices.com/docs/p ... 0%20a2.pdf From the user manual para 3.2.4: Folders. Feel free to create folders to help organize your Devices and Scenes. Folders can be created by either right clicking on the Network node (located on the left-hand pane) and choosing New Folder, or using the New Folder icon located on the Administrative Console’s top toolbar. Devices and Scenes can be dragged and dropped onto folders, or simply right-click a Device or Scene and choose Move To Folder and select the appropriate folder to move it to. Folders can also be moved within other Folders to create a nested hierarchy.

It sounds to me as if you have a lot of things going on here, including some of these newer keypads that apparently don't stay on or don't turn off when in non-toggle mode. If you want one keypad button to turn off in response to another button being turned on, the one button has to be a responder in a scene with the other button, having the ON levels set to zero. Are you familiar with how to set this up? The only way that I know for this to happen, other than having one of these "updated" keypads that don't stay on is by a program, but I understand that you have no such programs, so I can only conclude you have one of these types of keypads about which everyone has been talking. Have you included the ALL OUT OFF button in the scene with the ALL OUT ON button as controller, with an ON level of zero? Have you taken some other programming action to turn the ALL OUT OFF turns off in response to a command from the ALL OUT ON button? My questions continue to be along the same lines. Keypadlincs don't automatically turn off (or on) one keypad button in response to commands from another. These features have to be programmed (using either ISY scenes or programs) by the user. I remain unclear what method you have used for this and am having trouble offering specific advice on how to fix it. My recommendation is to focus on one set of related buttons and getting this working (or determining that your keypadlinc does not work for your application). For example, consider the all-out-on/all-out-off pair. Specify what you want to happen when you press each button, including what lights turn on or off, and what other buttons turn on or off. From there, I suspect the smart folks around here can offer a solution, or troubleshooting method.

I am sure that there is, but I have never had a sense that this is a real-world concern. Flash memory has a life, based on number of read-write cycles. My suspicion is that there are other things that will fail before this becomes an issue.

I am with shannong and kman on this. Variables are an unnecessary complication in this case, and STATUS is the correct condition. The suggested progrm will actually do more than you ask. In addition to sending a notice at 9 if the door is open, it will send a notice anytime between 9 and 630 if the door is open, or opened, during this period. This appears consistent with where you were you headed using variables.

This is the way I would do it. I suspect that this cannot be done by scene, alone, so programs are the way. Yes, this could probably be done with fewer programs, and purdueguy has one good suggestion. No, not based on what you state that you want to happen. The "adjust scene"command would be if you are trying to change ON levels of a scene for a given controller. If, for example, you wanted to have the KPL scene controller turn on the lights to 50% at certain times of the day, and 90% at other times of the day, then you would use the "adjust scene" command.

I, too, prefer the reliability of sunset/sunrise times, but I can see where there is value in making adjustments for cloudy days and mornings. It might be nice to have lights on earlier if it gets dark early due to cloud cover.

This program neither allows or prohibits anything. This program, by itself, will simply turn off a device called 'Great Room / GR Night KPL' when the condition is met. If you are asking whether one could create a program that would turn a KPL button off in response to all "downstairs" lights being off and all "stairs lights" being on, the answer is YES. Whether this specific program could do so, it is hard to tell because I see not way to make a distinction between downstairs lights and stairs lights. It appears to me that you may be struggling with understanding or explaining your requirements. You originally stated that you wanted to be able to press a KPL button and have some lights turn on and some lights turn off. If your intention for this button is simply to have this response EVERY time you press the button, then put it in non-toggle mode and create a program or scene that sets the light levels as you wish. Now you ask: This is a different question, in my mind. Are you asking whether you can manually turn OFF the KPL button, or whether a program can be set up to turn off the KPL button in response to a set of conditions? Is this the same KPL button that is the subject of your original question? Perhaps it would be a good idea to restate your entire set of requirements for this KPL button.

if they are in non-toggle OFF mode, they should blink a couple of times, then turn off. If in non-toggle ON mode, they should blink a couple of times, then stay on. Is this how they are behaving? Yes, this is not surprising. If you want some buttons to turn off in response to presses of other buttons, you would have to create additional scenes, or add buttons to existing scenes. Perhaps it best to summarize everything that you want to happen when you press the various keypad buttons.

If control switch is set on Or control switch is set fast on Then Wait set time Set lights off Else Yes, a running timer will reset if the switch is turned on again.

Are you on your home network (same network as ISY) or outside?

Is it possible that both have an x-10 address assigned?

Yes, it could be a bug in one of the newer versions of software for the ISY. i do not recall any earlier problems reported like this, but perhaps nobody has yet to notice any relationship between lost links and program changes. Can you demonstrate the problem consistently? Can you recreate the scenario that resulted in your missing links? I must admit that the idea that a program change would have an affect on link records is hard for me to imagine, but my knowledge of the detailed relationship between the ISY and PLM is conceptual at best, and based on assumptions and knowledge from others around here. My sense is that the folks at universal devices would be more than happy to investigate the possibility, but that this will be a little difficult without being able to reliably demonstrate a problem.

. Not if you configure a button as NON TOGGLE OFF or NON TOGGLE ON Right click on the desired button within the scene. Is there an option to delete from the scene?

This was how I would have guessed as well, but this would have also been fine for this application. Of course, there would have been a couple of extra (and unnecessary) OFF commands transmitted, but I suspect this would have been unnoticed.

Well...thanks to the input of apostolakisl ald test of larryllix, I would conclude that the codiotion of If time is from 0800 To sunrise (same day) Would be perfect for this application.

Have you tried the simple approach of: On Mon, Tue, Wed, Thu, Fri From 5:50:00AM To Sunrise (same day) Or On Sat, Sun From 8:00:00AM To Sunrise (same day) I must admit that I am unsure what happens with a program when the FROM time is after the TO time. Perhaps you could create a temprary program as an experiment to find out? From A couple of minutes from now To A minute from now Then Else Then watch the program status as the times pass. If the program stays FALSE, you are golden with the suggested simple approach.

It appears that one of the considerations on the wiki is to minimize communication traffic over the powerlines, so they try to avoid sending an ON command to devices and scenes that are already on. I have never seen the need to be overly concerned about this in my house. My programs and needs are relatively simple.

Oooh! Three-phase power concerns me. There is a recent thread somewhere talking about whether the RF relies on the voltage sine wave crossing points as a reference. If so, I cannot help but wonder if access points are effective on phases other than 180 degrees apart. I am unsure if this was resolved, but I think I would seek smarthome advice on this.

This makes me suspect that you have at least one motion sensor as controller in you scene. Please double check that this is not the case. WRT your program, I believe the best approach is even simpler: If Control MS1 is turned on Or control MS2 is turned on Or control MS3 is turned on Them Turn on scene Wait x minutes Turn off scene Else So nothing

Is this posted program named "motion detected"? Or is "motion detected" a different program. If the former, I see nothing in this program that would ever cause it to execute the ELSE path (and turn false). If the letter, please post it as well. I am still waiting for you response to earlier questions regarding scene members, including controllers and responders.

You have a lot of things going on here, and I can think of several possibilities. You have a program AND scenes? You may need to describe both. LeeGs suggestion to post the program is a good one. Also, as LeeG suggests, one of the problems may be in motion sensor configuration. Things that are going through my mind: Is your motion sensor sending ON only or does it send ON and OFF commands? Is your program based on STATUS or CONTROL conditions? Is your motion sensor a controller in your scenes that include the lamplincs? Do you have any unsaved changes to programs or motion sensor configuration? Is your PLM seeing the motion sensor commands? Answers to questions like that will be important to isolate this problem.