oberkc

Yes, unfortunate. I understand this to be a limitation of the keypad, itself.

The options might, in part, be based on the type of variable, integer or state? Mostly, I suspect you are having difficulty due to the fact that there is no way to send direct commands to keypad secondary buttons. Create a scene with the proper button (if necessary, a single-device scene), then use a program based upon the variable to adjust the newly-created scene.

I am still in the contemplative stage for the elk, and do not have one. I am interested in this as a learning experience for myself. As far as programming the ISY, I may be able to help, though I don't have any such programs. What I find interesting personally is turning wishes into logic steps and programs. What I don't have direct knowledge about is the access to your elk sensors and relays. Assuming relays and sensors appear to the ISY as simply another device, could it be as simple as something like: first program (disabled) if status elk garage door sensor is on then turn on KPL H button else turn off KPL H button a second program if control KPL H button is switched on then set ELK relay garage door trigger on (or whatever command tells the ELK to momentarily close) wait 10 seconds (to give garage door enough time to do its thing) run first program (then path) (to set proper status of KPL H) put KPL H into non-toggle ON so that each button press sends an ON command Perhaps I am totally off base here, so feel free to ignore.

Glad it is working. After continuing to ponder your problem, I have become concerned that I failed to suggest a viable solution to halting an on-going timer by turning ON one, or both, of the switches. Be sure to check for this scenario. Unfortunately, I have lost track of your exact programs, but I think the solution might be to modify (and re-enable) your timer program (whatever it is called) to something like: if control driveway is not switched on or control frontlawn is not switched on then turn lights on wait 45 seconds turn lights off Once modified, your other program would continue to call this program (then path). Adding these two conditions will send this program to the ELSE path (halting any ongoing wait period) any time one of the switches is turned on. Hopefully, that makes sense. Have a good Easter, yourself. Family is arriving. He has risen. All is good.

Also, this will have no effect on the variable condition. The now-two programs should (hopefully) set the variable correctly. The integer program should run based on the condition of that variable.

I don't believe that this will have any impact on how you should call out frontlightsmanual. Disabling the program will simply stop it from being triggered by its own conditions. When called by another program, it will continue to execute normally.

I must say that I am having trouble understanding why this does not work. Is it possible that your ISY is not seeing the OFF commands? If it is seeing the commands, I can only think to go ahead and break this into two programs.

did you ever put those additional parentheses in? I am not sure that this would cause any real problem, but it is at least worth trying. I will look over your program again to see if I can catch anything. Perhaps I did not get the logic correct to start. Worse case, create two programs: if control yard light is switched on or control driveway light is switch on then set integervariable to 1 else if control yard light is sitched off or control drivewaylight is switched off then set integervariable to 0 else

Of which program?

Are you certain that the ELK has relays, and not just sensors?

This could explain your problems. If the motion sensor turns on, then turns off in 0.5 seconds, responder devices would do the same.

If this is happening, check the program log to see if one of your programs is executing in such a way that would explain this. For example, if your "frontlightsinteger" status is FALSE, this would indicate that it ran the ELSE path, which would explain why the lights turned off.

continuing.... check the variable. Make sure it sets to 1 when you press EITHER of the switches ON, and sets to 0 when you press EITHER of the switches off. If you doubt one of the programs is correct, manually run the various parts (IF/THEN/ELSE) to see if they do what you want. Check the program log and verify that each program runs when you think it should. Watch the event viewer to be sure you are getting signals from the motion sensor. Things like that.

You might add a couple of parenthesees around your first to "OR" statements, see if this helps. Make it more like this: If ( Control 'Front Yard Lawn' is switched On Or Control 'Front Yard Driveway' is switched On ) And ( Control 'Front Yard Lawn' is not switched Off Or Control 'Front Yard Driveway' is not switched Off ) Then $Manual.Lights = 1 Else $Manual.Lights = 0 I assume this is the case, but make sure your motion sensor is not in a scene with your front lights. Take advantage of the tools available. Check each program and variable. Are they working as you expect? Check each program to

First, night mode for the motion sensor is not needed when you use the ISY to filter responses based upon time. I tend to like to keep motion sensors on regardless of darkness, and configured to send ON only. One never knows when one will want to keep track of motion around the house. I will offer a couple of ideas for your consideration. First, create an integer variable (does not trigger programs when used as a condition). This integer variable will be used to keep track of when one of your switches has been manually turned on or off. Then create a program to set the integer variable. This program will be true if one of your switches is MANUALLY switched on and false if one is manually switched off If ( Control lawn is switched on Or control driveway is switched on ) And ( Control lawn is not switched off Or control is not switched off ) Then Set integer variable = 1 Else Set integer variable = 0 Then create a program to trigger lights from motion If Time is from xxxx to yyyy And integer variable = 0 And control motion sensor is switched on Then Run frontlightsmotion (then path) Else Set frontyard off Set driveway off Remove the conditions from your frontlightsmotion program. Let me know how things work out for you.

Your programming was fine. My suggestion is to think out completely how you want your system to behave with regards to the motion and switch. My preferences for your consideration: - manual switch ON turns on lights and halt any ongoing timer / disable new timers and motion? - if lights off, and between certain time, motion triggers lights and timer. New motion restarts timer? - at sunrise + 6, any lights on turn off?

I suspect it will do what you stated, but I wonder if that is what you want. What do you want to happen if you manually turn on the lights while in a countdown timer (would you not want them halt the timer and stay on)? What if motion is sensed during the countdown (would you not want to reset the timer)?

http://www.universal-devices.com/mwiki/ ... =Main_Page

my first inclination would be to recheck connections. Make sure none are loose, and that it is bare conductor under the wire nuts. What are flickering? The fan lights? The switch LEDs? What are the lights? Incandescent?

Ah, yes. My fault. I always forget this problem. Secondary buttons cannot be controlled directly, unfortunately. They have to be put into a scene. If need be, create a scene with a single device: the KPL button. The program would then be: if status KPLD is on then set scene with KPLC on set scene with KPLB on wait 2 minutes set scene with KPLC off set scene with KPLD off else nothing sorry for my forgetfulness.

Rather than a marginal Keypadlinc, I suggest you consider the possibility that communication between the PLM and Keypad is somehow being disrupted...most likely by other electronic devices on the circuit powering the PLM. What other devices are on this circuit? Lots of computer stuff?

So, when someone turns on KPL D, you want it to turn off after two minutes, along with KPL C? OK. You did not state what you want to happen if KPL turns off during the two-minute timer, so I will make no assumptions. If Status KPL D is on then set KPL C on set KPL B on wait 2 minutes set KPL C off set KPL D off else nothing

Credit is due to PurdueGuy (though I would prefer it if it were OSUGuy). To re-enforce one point, in each scene, the secondary responder buttons ON level should be OFF (or zero)! The idea is to create a scene such that when you press the controller button for that scene to turn the scene ON, the responder keypad buttons will actually turn OFF.

I view this whole topic as a matter of degree and confidence. Insteon, and the ISY, can provide SOME level of security. Whether it is enough for any one person is up to them to decide. I don't have a security system (yet), but I believe that I am more secure with an ISY than without. Can it completely replace an ELK or other security system? Not with the same levels of confidence and, in some cases, capabilities. Not in my mind, at least.

Like PurdueGuy said, the syntax is not exact, but when you go into the dropdown box in the programming section, and select condition, it gives you the option to choose "control". Then choose the insteon device, the choose the desired command (ON, OFF, NOT ON, etc). The reference to remotelinc.D is, I am sure, button D on the remotelinc. Exact syntax would be generated by the ISY and would look more like: Control 'button D' is switched Off The only way to set a variable in response to a remotelinc button press is via a program, so I don't see how this solves your problem if you are having trouble initiating a program from that button press. Is is possible that you are not having a programming problem, but rather the ISY is not seeing the button presses?