Sub-Routine

The ISY can control X-10 modules but I would suggest using an Insteon I/O Linc for higher reliability and two way communication. Rand

The double-blink mode is unlinking mode. When using the ISY to write links to the motion sensor it does not matter which mode the MS is in. I added some info to the Motion Sensor Wiki page. Rand

Good news! Rand

In my experience that setting has nothing to do with how long the inactivity period is. I will experiment; I am leaning towards it being a factor of 8 seconds. Rand

Two heads are better than one. Good examples Mike.

The motion sensor will send an On after a period of inactivity. It will not send another On until after a period of inactivity. I'm not sure how long it is, seems like 10-15 seconds, but I have not timed it. Since it's Status is always On (in your case) you should remove that line from your Conditions. Rand

Yes, that is how scenes are configured in the ISY. The 'base' scene is the one used by the ISY, either by direct control or in programs. Every other controller in the scene can have different levels and rates for the devices in the scene. If you want the other controller to use the same levels and rates as the ISY you can select that controller in the scene and use "Copy Scene Attributes from Scene Name". Rand

You can use an I/O Linc with the ISY now for a single garage door: I/O with garage door I think raccoons are destructive, I can't imagine a bear Rand

The motion sensors need at least 5 minutes after inserting the battery before they function reliably. If you haven't changed any jumpers or settings they should definitely show Off after one minute without motion. Pressing the set button should toggle the On/Off. If those signals don't appear to the ISY then there is a communication issue. Bring the MS and the Access Point close to the PLM (plug an Access Point into the PLM). If that doesn't help you should remove the MS from ISY, perform a factory reset on the MS and re-add it to the ISY. BTW, because the motion sensors are battery operated they will not respond to queries unless in linking mode. Rand

Updated the Create a Program page. Rand

Those contacts should be fine, I wanted to point out that either NO or NC contacts can be used. I like the non-toggle idea. Otherwise one would need a program to poll the IOLinc after a close/open command is sent. Good thought! Thank you, Rand

Hi Gary, I spent some time with the I/OLinc this morning and have created a page in the Wiki that outlines the Options available. I/OLinc. I found a couple of things that may improve your use. A normally open sensor can be used by setting the Trigger Off bit. You don't need to set the button to non-toggle if you select Momentary A and Momentary Both. Rand

The How-To Guide has been updated. Rand

I added a page for the I/OLinc. Rand

Good deal Gary! I am adding this to the Wiki, thank you. Rand

It must be, I read it somewhere I added it to the Wiki How-To as well. The programmers are adding features faster than I can keep up! Rand

The motion sensors cannot be linked in Auto Discover mode. Menu - Link Management/New INSTEON device Enter the address. Select the Motion Sensor from the drop down list. It's the 2nd from last device. Follow the instructions to put it in linking mode. Rand

Gary, I think I have this figured out. Highlight the scene in the Administrative Console Slide the relay level to 100% Click on the keypad button in the scene Slide the relay level to 100% Rand

Yes, that works Mike. Here I have added a flash for a warning. If Control 'Motion Sensor' is switched Off And Control 'Motion Sensor' is not switched On Then Wait 30 seconds Set Scene 'Lights' Fast On Set Scene 'Lights' On Wait 30 seconds Set Scene 'Lights' Off Else No Actions Rand

Hello Gary, I just got an IOLinc myself so I cannot answer all your questions. I do know that if the relay is on and the KPL button is off when you link them the action will be as you described. Both should be on or off when you create the link. For the garage door button press you will want to set Momentary: A. This seems to only activate the relay when an Off is sent. If you also check Momentary: Both the relay will then be momentarily closed with each press of the button. 2 seconds should be a good timeout. Rand

The first program you list contradicts the fourth program, and the second program contradicts the third. I think what you want to do would use Control instead of Status: If Control 'Living Room KPL 4' is switched On And Status 'Living Room KPL 5' is Off Then Set Scene 'Button 5' On Else - No Actions - (To add one, press 'Action') But if you put both buttons, as controllers, into one scene then they should follow each other and you won't need any programs. Rand

Great tip Wayne! I set this up to use in our kitchen today (three-way setup) I disabled the Off and set the Delay to 30 seconds. I still have the MS linked to the lights so they snap on with no program delay. I removed the line that checks the light status so whenever movement is detected it restarts the countdown timer. Then my timeout only needs to be >30 seconds. I only check for an On press, but I may change that. When home and awake we like to keep the lights on low, thus the Kitchen Low On. I have different schedules on folders to sort this out. Here are the evening programs. KMotion On Evening If Control 'Kitchen Motion Sensor 1-Senso' is switched On Then Run Program 'KMotion Off Evening' (If) Else - No Actions - (To add one, press 'Action') KMotion Off Evening If Control 'Kitchen Ceiling Light' is not switched On And Control 'Kitchen South' is not switched On Then Wait 1 minute Set Scene 'Kitchen Low' On Else - No Actions - (To add one, press 'Action') Thanks again! Rand

Program: Weather Warm If Module 'Climate' Temperature >= 32 °F And Program 'Temperature Warm' is False Then Run Program 'Temperature Warm' (Then Path) Run Program 'Temperature Cold' (Else Path) Else - No Actions - (To add one, press 'Action') When it warms Only runs if it was cold during last check You can download the programs from here: Temperature.2009-02-06.10.53.39.zip. Unzip the file and Import it to your ISY Programs folder. Rand

Program: Weather Cold If Module 'Climate' Temperature < 32 °F And Program 'Temperature Cold' is False Then Run Program 'Temperature Cold' (Then Path) Run Program 'Temperature Warm' (Else Path) Else - No Actions - (To add one, press 'Action') When the temperature falls Only runs if it was warm during last check

This is better. One program sends an email when the temperature falls below the target, and stays below, for 5 minutes, the other sends an email when the temperature rises above the target with the same 5 minute buffer. One email is titled Temperature Cold and the other Temperature Warm. Change the target temperatures if you like. I can't seem to place more than two Code boxes in a post so I created several posts. Program: Temperature Cold If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 5 minutes Send Notification to All Else - No Actions - (To add one, press 'Action') Cold = True Warm = False Program: Temperature Warm If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 5 minutes Send Notification to All Else - No Actions - (To add one, press 'Action') Warm = True Cold = False