fitzpatri8

A program that triggered with: "If Control 'Garage InLineLinc w Sense' is switched On" would only evaluate as true if the sensor attached to the ILL turned on. A program that triggered with: "If Status 'Garage InLineLinc w Sense' is On" would evaluate as true if *either* the sensor turned on *or* another Insteon device, linked as a controller with the ILL as responder, turned the ILL on. In that way, you could turn on the light using another sensor (another motion on the other side of the house, for instance) and still see when the attached motion triggered. If the motion sensor tells the ILL to turn on, it turns on, so if you wanted to sense motion during the day you'd need to disable the dusk sensor and the ILL would switch on whenever the motion detector saw motion. If you wanted to detect motion during the day but only operate the light at night, you'd need to disable the motion sensor's dusk/dawn sensor and add another dusk sensor between the ILL load output and the actual light.

That's correct.

You shouldn't need to clip anything. Both the TriggerLinc and the DS-10 have screw terminals to connect external sensors.

I can answer that. The ILL Relay with Sense is a single controller. The sense signal turns the ILL on or off and sends a controller signal from the ILL to turn on any devices linked as responders. Any status requests will simply show the current status of that ILL, whether or not the ILL was turned on via a remote command or via sense. That said, you can distinguish events by choosing whether a program is triggered by Control 'Ill' or Status 'Ill', since Control will only trigger if the Sense/front panel button is triggered, whereas the Status will simply reflect whether the device is on or off regardless of which linked device turned it on.

You can change the placement of the magnet, change the placement of the receiver, or discard the included magnet and instead wire up your own set of contacts, whichever you prefer.

Putting bathroom lighting on a timer isn't usually a good idea unless you have motion sensors to override the program. People don't like being left in the dark in the bathroom. I'd take the lightswitch out of that third program. You have several options for how to deal with the light. You could write a program that automatically dims the light instead of turning it all the way off, or if the room has natural light you could turn it off if during daylight hours, but I'd be reluctant to just turn it off when people are in the house.

No, the v572a does not support security devices like the ds10. For that, you'd need to use the V572RF32.

The v572 requires a x10 PSC05 interface to transmit x10 signals via a power line carrier signal. Your program could be as simple as: Program Content for 'Front Room Motion' If X10 'A1/ON (3)' is Received Then No Actions Else No Actions * When the motion sensor transmitted A1 ON, the v572 would receive the wireless signal and broadcast it via the PSC05 as a power line signal. * The Insteon PLM would hear the power line signal and trigger the ISY program. * The ISY would update the Programs's Last Run Time to the current date & time. (Log into the ISY, but instead of going to the Admin Console click on Programs to see the 'Last Run Time' of all your programs.) You could also send an email notification, but then you have to add a notification limit. Those x10 motion sensors can send out a new ON signal every few seconds while they continue to see motion, so having it email you as the housekeeper vacuums can easily fill your mailbox and run through your cell phone's allotment of text messages!

What condition are you using to decide between 1, 2 or 3 cycles?

What you want to do is have that x10 code trigger a program. Even if the program has no actions, it will update the timestamp in the ISY's Programs list so you can see when it was last activated (so you can see when the housekeeper was there, for instance). If you also have that program send a notification, that program's name will be included in the subject line of the email or text message. If you name a program Living Room Motion, the subject line of the notification email in that program will be Living Room Motion: Alert.

Do you really want to triple the wear and tear on those electric valves by cycling them that much? Seems like you'd be better off to run separate programs based on the conditions so that you'd just leave each on longer to allow the water a chance to soak in. Also, using a simple x2 or x3 multiplier might also work better for some plants than others--overwatering can damage plants, too.

The ISY multi-tasks, so a WAIT command doesn't pay attention to any other processes the program starts. I think you can get the effect you want just by using the REPEAT command in the second program, and removing the WAIT and second program call in the first program. See REPEAT details here: http://www.universal-devices.com/mwiki/ ... EON:Action.

'Local Control' is one of those features that people either love or hate. It is included on ApplianceLincs, LampLincs, Icon Dimmer and On/Off modules as well as OutletLincs. The module design intentionally allows a trickle of current to pass through when turned off so it can determine if you toggle the attached device's on/off switch, then uses that signal to turn the device on without need for another controller. As you've discovered, this trickle current is enough to cause flickering on some CFL bulbs and LED lighting. So far as I know, turning off the Local Control option in the module disables it from turning on, but does not stop that small sense current. As an alternative, you can add a cube tap and add another load--an incandescent night light or a small wall wart power supply--to absorb this current, or you can use an InLineLinc instead. Neither the InLineLinc nor the SwitchLinc products have the Local Control feature.

.1 ramp rate? Why? I only use faston and .1 ramp rates for exterior security lighting, where the intent is to shock. Indoors, a slower rate sets a more relaxed mood and also seems to make the bulbs last longer. Programs won't be as fast as scenes, since there's both processing time and at least 2x as many messages being passed back & forth.

Yes, but you'd need to reverse the logic. Go back to the MAIN tab, select 0E.3A.00.1/SDB in the device list and set its On Level (Applied Locally) to 40%. Now go to the device and pull out the set button to remove power. Count to 30. Now push the set button back in flush (don't push in, just flush with the faceplate). Test the button--pressing it once should now turn the light on to 40%. Now change your program: If From 5:00:00AM To 11:00:00PM (same day) And Control '0E.3A.00.1/SDB' is switched On Then Set '0E.3A.00.1/SDB' 100% Else - No Actions - (To add one, press 'Action') You can also still adjust the lamp no matter what the time of day. At night, you can still double-tap to turn on to 100%, and you can always press and hold to brighten or dim.

But if he wants the status to determine whether or not the program runs (and whether or not the device turns back off in 10 minutes), then he'd need to take a different approach. I still have to think that process through each time... So instead of putting the on/wait/off commands as the Then (which stops executing because the commands make the original trigger false), he'd want to have a third program that read: If No Conditions Then Turn Kitchen Light On Wait 10 minutes Turn Kitchen Light Off Else No actions and in his first program, he'd replace the Then with Then Run Program (3rd program) Then Path

Sounds like: If Control 'rear deck motion sensor' is switched On And From Sunrise To Sunset (Same Day) And Status 'Kitchen Light' is Off Then Set 'Kitchen Light' On Wait 10 minutes Set 'Kitchen Light' Off If Control 'rear deck motion sensor' is switched On And From Sunset To Sunrise (next day) And Status 'Kitchen Light' is Off Then Set 'Kitchen Light' On Set 'Outside Light 1' On Set 'Outside Light 2' On Set 'Outside Light 3' On (Or Set Scene 'Outdoor Lights' On) Wait 10 minutes Set Set 'Kitchen Light' On Set 'Outside Light 1' Off Set 'Outside Light 2' Off Set 'Outside Light 3' Off

Sounds like you've set it up incorrectly. Mine works almost instantly, though it can take a second if the ISY or HL2 has a bunch of traffic on the powerline at the time. If you use a program, then the TriggerLinc messages the ISY, then the ISY runs the program, then the program has to send the command to turn on the light. Instead, for the quickest response, you should set up the TriggerLinc in multi controller mode (IIRC you just remove a jumper and power cycle), then link group 1 directly to the light you want to command. That way, the light comes on immediately without any ISY programming. Meanwhile you can use the same Group 1 On command to run your program, wait 7 minutes, then turn the light off. This works in Multi mode because the Triggerlinc sends a Group 2 On instead of a Group 1 Off when the door closes, so closing the door won't immediately turn off the light.

Depends how you count. The RemoteLinc has six on/off pair, which you can actually use to toggle 12 different scenes on and off with a little programming in the ISY. The trick is to link the RL only to the ISY, then let the ISY determine whether the scene is currently on or off then send out the appropriate, opposite signal. If you need to control more than 12 scenes with one controller, you might want to investigate options like the new iPod Touch/ISY application or Mike's InterfaceGO application on a Nokia.

Any chance a communications issue is causing the delay? Have you looked at the log to see how many hops commands are taking when communicating with the members of that program? Also, have you set it up so that the program executes a scene vs. commands each member device individually?