oberkc

1. You now have a spare 2. You can use the old one in a different application, making your system better Other than that (and the dimming and, I guess, sound), I am unaware of any major advantages.

Can you not manually dim the older KPLs? Perhaps this is not dim enough?

How is your exterior post light controlled? By the switchllinc? What does your switchlinc control directly, if anything? Perhaps I understand your question a little differently now. If your switch is off, you want your lamplinc to go off at sunrise and to 30% at sunset. You want this to happen continuously for as long as you switch remains off, not just at the moment your switch is turned off, based on the conditions at the time. If I understand correctly, there are a couple of ways that I would consider tackling this problem. One way would be to substitute status for control in my previously suggested two programs: if from sunrise to sunset same day and status of switch is off then set lamp to off The second program would look something like: if from sunset to sunrise next day and status of switch is off Alternatively, you may consider creating a program folder which is active when the status of the switch is off. In this folder, place a program: if from sunset to sunrise then set lamp to 30% else set lamp to off Of course, you will want to test these to confirm that they work as you intend.

It is possible that I misunderstood, but the two requests I see are for 30% and off. Did I miss something?

I would try this with two programs. The first would cover the period between sunrise and sunset: if from sunrise to sunset same day and control switch is set off then set lamp to off The second program would look something like: if from sunset to sunrise next day and control switch is set off then set lamp 30%

You can also check the log file. While I have not taken advantage of this, you can also set up a program to send you an EMail message.

ISY would see insteon traffic. However, part of the process with ISY is to add (link) devices to it. One sets the ISY into linking mode, then does the same for the device. This process identifies each device to the ISY.

I am wondering, like TS99, if your "keypad A-F2" is in a scene with your kitchen lights. I am also wondering if you would be better served if you use "control" for your condition, rather than "status". A remote (in my mind) possibility is communication problems. Though I don't think I have seen this, I wonder if some devices flash their load if experiencing comm problems. I know that the keypad lights do.

I checked and stand corrected. My memory is worn out. I created this program: If From 4:45:00PM To 7:45:00PM (same day) And Control 'SW LRW Livingroom Wall' is switched Off Then Set 'PM LRT Livingroom Table' On Else - No Actions - (To add one, press 'Action') this one kept turning the lights back on, after I switch them off. Changing the condition from 'control' to 'status' produced the same results.

Depends on the program. If you have a program something like: if from 5p -10p then set light on else Such a program would ensure the lights stay on during that period. If you turn them off, the program would execute the else statement, because the condition (between 5 and 10 pm) is still true. A program such as if time = 5p then set light on else This is a one-time good deal, where the condition is only true for a moment on any given day. At 501, the condition is no longer true. If you turn the light off, the program will not re-execute anything.

I also look forward to understanding the benefit to two programs, one for light, and one for sunset. My inclination is to run two programs, on and off. On would be based on light or sunset. It would have no "else" conditions: if light = 0 or time = sunset then set scene 'outside lights' on else if time = 900p then set scene 'outside light' off else I suspect part of your problems ealier was with the program re-evaluating itself every time the conditions change, then running the else statements. Another potential problem with your first attempt would be that the program may prevent you from manually turning the lights off before 900 if you choose. That would bother me. Of course, there are many ways of doing what you want. You could use folders, you could nest programs within programs. You could use multiple programs. Experiment around and have fun.

I am unfamiliar about light levels, but is it possible that they don't get ever to 0? If so, this program might not work for you. If light >0 and sunset, I expect this program to run the "then" statement, but immediately run the "else" statement when time is not sunset. One can copy programs and paste to the forum. I am having to go by memory, but I am thinking right click on a given program, and choose copy.

I assume that your line would first go to your panels. Does the same main line feed both panels? 240 and 120 outlets would have to be wired from a panel. I understand that there are hard-wired phase couplers. I think if I had the flexibility to design my wiring for insteon, this is what I would use. I would also include a couple of access points for remote links and additional coverage. I am not sure about the ability to transmit signals from panel to panel, but assume that if the same lines feeds both, you should be good. If not, then a couple of access points may work well for you. I have had good experience with a dedicated circuit for the PLM. Mine is run from the panel to the office, where the computer is located. Nothing else is on that circuit. I don't believe that there is a plug-in coupler advertised specifically for insteon, but I have heard that the one for x-10 may indeed work for insteon. Regardless, I can report that x-10 couplers can at least coexist without any apparent problem.

I suppose there could be some type of hardware failure. Short of that, is it possible that some device came on in your house which would cause a lot of noise? Furnace? Refrigerator? Is your X-10 still working?

I must confess to not being a user of the insteon motion sensor. All mine are X-10. I understand that the insteon sensor must reset itself before it can, again, sense motion. Can you not configure the sensor to reset itself without sending an off command? After enabling the off command, for how long did you set your time-out? What was the result of your experiment. There are A LOT of posts regarding motion sensors and programming. Some of the programming can get very creative. I can say, however, that your needs are nothing unusual. I think there is even a wiki article about this. It is worth searching and checking out.

I learned most of what I know by experimentation. Go ahead and enable the off command, and see if the new program will work. I was not sure if recieving the off command would force the program to re-evaluate itself before the 10 minute timer was complete, but assumed that it would. If this does not work, then change it back. If setting your off command breaks your program, then there are probably other options. It is sometimes good to check the simple solutions first. One possibility would be to create a program without "if" conditions, having only an else to turn on the light, wait ten minutes, then turn off the light. A second program would watch of motion sensor "on" commands, then run the first program's "then" statement. For example Program one: if then turn light on wait 10 minutes, turn light off else Program 2: If control motion sensor is turned on then run program 1 then path else I believe that program 1 else path would continue to run, regardless of the presence of a motion sensor off signal.

Have you checked your event view to ensure you are recieving the signal? I assume that this is not an issue. I understand that insteon motion sensors have jumpers that must be set, depending on your needs. Is your set to send an off signal when it reset? I assume that ISY status is based on recieving on and off signals, but that is just a guess. Are you motion lights set up as a scene controller with the study lights? In this case, I don't believe that would achieve the results you are looking for. Having asked all those questions, I suggest ensuring that your motion sensor is set so that it does NOT send an off signal. Then, write a program looking something like: If Control 'Study Motion-Sensor' is turned On Then Set Scene 'Study Lights' On Wait 10 minutes Set Scene 'Study Lights' Off Else I suspect you were getting into problems with the program re-evaluating itself mid execution, which is not good. I also recall a recent thread on this very same topic. Try searching for motion sensors. You will find much.

Thanks, Mark. I, too, have already created a program with this technique. It solves a problem I have not been able to address. Until now. Scenes, in my mind, are simply another way to link insteon devices, so that they respond to each other. It duplicates the manual linking process described in the manual of the various devices. Programs allow actions in response to conditions. Conditions may be time, sunset, darkness, motion, temperature, garage doors, or just about anything else one can imagine. Conditions may also be other insteon signals. Therefore, it is possible to duplicate scenes with programs, but I consider it better to use scenes where applicable. I don't think I would have remembered this, but I don't see keypad buttons (other than the primary) as a device which can be controlled by a program command. This surprised me...I thought that I had used this capability before. Perhaps it is one of those things available on certain versions of keypads and not on others. But you can put these buttons in a scene and then control the scene in a command. Go figure.

So, let's see if I have this right...you want the KPLA to control kitchen lights. So, you have set up a scene with KPLA as a controller of a scene with other devices (switches, I assume). Did you set up those devices as controllers also, or just responders? It sounds like they are just responders. I am not in a position to confirm at this point, but my recollection is that when the ISY turns on a controller of a scene (KPLA, in your case), the scene does NOT activate. But this sounds contrary to your experience. If my understanding is accurate, then a program: if kitchen island is turned on or kitchen lights are turned on or other kitchen lights are turned on then turn on KPLA would do the job. Maybe tomorrow, I can play around some more to check this out. Sorry I cannot be more help tonight.

Is this an 8-button KPL? KPLA is the controller of the load, right? If so, then turning it on turns on the load. I don't believe there is any getting around this. That is the design of the keypad. However, all other buttons are controllable in this way.

I would double check to confirm it is not set to non-toggle on, otherwise, I have no explanation within the realm of a functioning device. Though I have never tried it, is it possible that this keypad is part of a scene that has turned it on, or in response to a programmed command? I am not even sure that it is possible to turn on a keypad set into the non-toggle off mode, but it may be worth checking.

OK. So...everything is working like you hoped, but you just wanted a better understanding of the event log?

I have found nothing that I can do manually that I cannot do with the ISY, but many things with the ISY that I cannot do manually. I have also found no limitations that the ISY imparts upon devices. I may have misunderstood your problem, but I also have some 6-button dimming keypads, programmed through the ISY. I can still dim the hardwired light. Press and hold. Am I missing something here?

I would watch the event viewer while you press your remote buttons to make sure that the event is recieved and is consistent with the "if" condition of your program.

It sounds like your program executed exactly as intended. Is this correct? I assume you refer to the status as indicated by the admin panel? My guess is that, since motion sensors do not listen for insteon signals, nor respond to them, that the ISY does not recieve an acknowledgement back, so it assumes that is remains on. I am not sure that this will create a problem for you besides being a nuissance when you open the admin panel.