fitzpatri8

No worries--I'm still pretty new at this too, but you get used to it. So here's the plan. A non-toggle OFF button on the KPL will only turn devices off. That's why you don't want to make it a controller for your scene that has some units turning off, others turning on. Instead, you want the KPL G to not be in any scenes. All you want is for it to trigger an ISY program that reads: If Control 'KeypadLinc G' is switched Off Then Set Scene 'Nighttime Scene' On Else - No Actions - (To add one, press 'Action') No signal conflicts this way, the KPL G sends just one device the KPL G Off signal. When ISY gets it, it sends out a single Nighttime Scene ON Group ON command, and the devices in the scene all start adjusting themselves to match the scene all at the same time.

I've pretty much come to the conclusion that, with the ISY, anything is possible. What I was suggesting is that you just add any devices that are in the All Off scene to the Nighttime Scene, using an "on" level of Off. Then when the keypad sends the OFF to the ISY, the power line would be free of competing control signals and the ISY would just need to execute a single scene to get all devices in their correct state.

Now remove the KeypadLinc button G as a controller of the scene, since you *don't* want to turn the scene off.

Not directly, since you cannot have an Off button directly tell another Insteon device to turn on. Instead, you'd have the off control trigger the program that ran the nighttime scene.

That's just making more work. You don't need to set any dim level on the lights in that scene controlled by KPL G, since you are never sending an ON code to adjust to that level. In non-toggle OFF mode you are always going to set devices in the scene to OFF. BTW, is there a reason you want all the lights to turn off for 5 seconds? If not, the alternative is to forget the second scene completely and just create one program and a single scene with all the lights in it adjusted as you want--the ones you want off, use a 0% dim level, and the ones you want on set to that.

The problem here is, as you've set up your system you have to press two different buttons to activate the scene you want. That's not convenience, that's just extra work. Have you considered swapping a KeypadLinc for the second SwitchLinc, so you have easy control of the main scene with the SL and flexibility on alternate scenes with the KPL? Any solution that tries to readjust after an intentional signal stomping is going to give inferior results. You would need an ISY program that looked for either button pressed at each station, then it would have to manually query both SwitchLincs at that station, then if the status didn't match the expected status you'd need the ISY to retransmit the group command. Because of the extra signal traffic and program processing time, there'd be a delay between the manual query and the new group command being sent, and in the process, those signals would be competing for bandwidth with any intended dim/bright commands you might be trying to send from the switch at the same time.

So you've got two scenes and one program. The first scene, All Lights, has that KeypadLinc button G as a controller, all other lights in the house as responders. The second scene, Night Scene, has all the lights you want to turn on. The program would say: If Control 'KeypadLinc G' is switched Off Then Wait 5 seconds Set Scene 'Night Scene' On Else - No Actions - (To add one, press 'Action')

The 6 button/5 scene mode on the KPL really isn't designed to handle that sort of behavior. What you could do, however, is program it to 8 button mode but leave the 6 button faceplate on, then cross-link buttons a and b, and cross-link buttons g and h. Your home program would trigger if either a or b turned on, would set the scene and turn off the scene with a,b,g and h as responders; your away program would trigger if either g or h turned on, would set the away scene, then would turn off the scene with a,b,g and h as responders.

As I understand it, when you change the battery or press the reset button on the DS10 security sensor, it picks one of a limited number (256?) wireless security codes at random. It will continue to use the same security code until the reset button is again pressed or the battery dies or is removed. Current model ISYs communicates with the outside world using an Insteon 2412S Power Line Modem (PLM) interface, capable of transmitting and receiving Insteon standard and extended messages and x10 standard power line signals. The PLM alone cannot receive wireless x10 or wireless 10 security signals, at least not without a little help. WGL Designs builds and sells one such solution. You can program their V572RF32 32 bit wireless tranceiver (http://www.wgldesigns.com/v572.html) to receive a wireless x10 or x10 security signal, then map that to and transmit a standard x10 power line signal. The ISY could then use the resulting x10 power line signal to trigger programs. Each time you did a battery change you'd need to reprogram the WGL interface to respond to the new, random code. It's certainly doable, but it isn't nearly as easy as using the wireless Insteon TriggerLinc or a plug-in IO Lincs.

The TriggerLinc's multi-scene mode is most valuable when used as described by folks who don't yet have an ISY, but you may well still want to use it even with this controller. The difference between using a TriggerLinc in Multi-Link mode and using the TriggerLinc to trigger two ISY programs is time. Devices that are linked directly to controllers respond immediately, vs. with programs the signal goes from the TL to the ISY, then the ISY finds and runs the appropriate program, then the PLM sends the second signal. Depending on what else is going on on your power line and with the ISY, there can be as much as a few seconds delay between trigger and response when you use a TL to ISY programs to responder setup.

If you want pressing a switch's Off button to do something other than turn linked devices off, you'll want to avoid linking those controllers directly to responder devices. Instead, create scenes and programs to define the different behaviors you have in mind, then use those controller buttons to trigger the programs and to run the appropriate scene. You can organize your scenes into different folders so the programs inside only run during certain time periods.

So you've created the new scene (click on the painter's pallet and give it a name), then you right-clicked a controller button (a ControLinc button) and added it to the scene as a controller. Next, you selected several other devices, right-clicked and added them to the scene as responders. Now you should click on the scene name (not the enrolled devices, the scene itself) to pull up scene details. Adjust the sliders here for each of the enrolled devices. Finally, click on the controller button within the scene and click on the button above the sliders that says "Copy Scene Attributes from [scene name]".

The motion sensor adds or removes 110 VAC to the sense wire of the ILL, then the ILL responds to the change in state. If it is a change in state from off to on, it turns on the attached load and sends an ON signal to all linked devices; if it is a change in state from on to off, it turns off the attached load and transmits an OFF to all linked devices. If you send it a FAST ON or FAST OFF, it will switch its load to that state and ignore any input from the sense wire until it is removed from this mode with a regular ON or OFF.

The InLineLinc that is part of the # 2494MSWH kit is designed to give a coordinated response--when voltage is sensed on its input, it turns on its load and sends an on to linked devices, when voltage is removed, it turns off its load and sends an off to linked devices.

Since the devices are all responding to a single transmission from the controller (Device xx.xx.xx Group y ON), devices will respond concurrently so long as your signals are good. If you have an unresolved noise or signal absorption problem and one or two devices don't 'hear' the original group message, then they will turn on slightly later when direct cleanup commands get through.

In that event, I'd create one "Lights Off" scene with all 47 devices in it, with the On level set to Off. That way, whether you send an On or an Off it'll still turn the devices off. Create a second 'All Lights Status' scene that has ONLY the keypad button as a member. Create a 'Check Status' program that says if status (light 1) is not off or status (light 2) is not off...status (light 47) is not off, then turn on 'All Lights Status' Scene else turn off 'All Lights Status' Scene. Create an All Off program that says if Control (your keypad button) turns on or if Control (your keypad button) turns off, then wait 10 seconds, run (if) 'Check Status'. That ought to do it.

What do you want to happen if the keypad light is off and you press the button again?

I've been seeing the problem for a few beta versions but just didn't have the time to pursue it.

That fixed it. Thanks!

When attempting to back up my ISY-26 for upgrade, I get the error: Could Not Retrieve File /CONF/18.PRP Could Not Create the Zip File The result is a 56 byte zip file without any device or program detail inside. What's the best way to rebuild or replace 18.PRP to allow a backup? Thanks, Tom

The simplest option would be to add to the Else portion of the Bath Motion program. "Else Set 'Bath: Guest Light' On" As best I can tell, adding door open/closed logic to adjust timers would require adding a couple of programs. We haven't even addressed the ambient light question--if this bathroom has a window, do you want the outside light level (as determined by the optional Weatherbug module, since the motion detector's dusk/dawn detector needs 3+ minutes to adjust to changing conditions) to influence whether motion turns on the light? This could get complicated!

I like it!

Fitz - will that allow me to do a fast off as a manual off for the fan? Yes, it should. That was just a typo on my part. Your code should be fine.

Bath Fan Manual Control would replace both your BR Fan On and BR Fan Off programs. By adding the "And Control 'Bathroom: Guest Light is not switched Fast Off" line we accomplish two things: if you turn the fan off, the timer aborts, so it won't accidentally turn the fan off early if you activate it again, and you eliminate one program. The Run Else Path jumps to the Else portion of the same program, so if we look at the program status from the ISY console we can see if the program timer is currently running or not. Almost. The ISY puts a timestamp on the program every time it runs. That's the key to the first line in the next program, Bath Light Timeout: "If From Last Run Time for 'Bath Motion' For 10 minutes." That's the hope--I'm still new at this myself, that's why I wanted you to tell me if it works! (The original post was wrong. I just edited it and corrected the logic.) Exactly. Let me know if it works as expected!

Let me know if this works for you: Bath Fan Manual Control If Control 'Bathroom: Guest Light' is switched Fast On And Control 'Bathroom: Guest Light is not switched Fast Off Then Set 'Bathroom: Guest Fan' On Wait 40 minutes Run Program 'Bath Fan Manual Control' (Else Path) Else Set 'Bathroom: Guest Fan' Off Bath Motion If Control 'Bathroom: Guest Motion' is On And Status 'Bathroom: Guest Light' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Bath Light Timeout If Time is Last Run Time for 'Bath Motion' + 10 minutes And Status 'Bathroom: Guest Light' is On Then Set 'Bathroom: Guest Light Off Else - No Actions - (To add one, press 'Action')