Sub-Routine

I didn't realize that was true with the KPL, I know a SwitchLinc doesn't send group commands unless it is linked to another device. Linking a SL to the PLM is enough, but of course there is only one group for a switch. What if you create a new scene with only the KPL button in it? If that works there may be a bug in the ISY. Rand

It sounds like the ISY isn't seeing the change. If you watch in the Administration Console do you see the state of the button change from Off to On?

There is a Random with the Wait Action. It is only + so set your schedule early then add a Wait and check the Random box. Rand

That program should work fine. When you use Switched you must physically press the button, it won't work if the button is turned on/off in any other way. For that you need to use Status. Rand

I remember those days. I'm hoping grandchildren will do that to me in the future. For now I can stay up all night if I want! We (most of the party) went to a gin mill for breakfast this new year morning

Are you saying you weren't up to witness it?? I was up, about 30 miles away though

You can use these options to 'reuse' a program with a different set of conditions. Though I confess that I don't find many uses for this feature it does have some value and others use it. It's a method to complicate the simple programming offered by the ISY Rand

You can right click on any program or program folder (including My Programs) and Export it to an XML file. Rand

Run If evaluates the conditions in the If routine, sets the program True or False, and runs the Then (True) or Else (False) procedure. Run Then ignores the If condition(s), sets the program to True, and runs the Then routine. Run Else ignores the If condition(s), sets the program to False, and runs the Else routine. Rand

Thanks Randy, armed with that piece of info I was able to get it down to 2 programs. So this effectively allows the 'disabled' program to run without the continual re-evaluating of the 'If' statement during execution. Perfect, now I can go and fix all the other inefficient programs I've written. Regards, Wayne Good Job! Rand

If the link was created previously and you are not interpreting the button press using a program the link should work with or without the ISY. Changing the firmware in the ISY would have no effect on established links. Rand

According to the Program Summary my program ran at midnight. Whoo Hoo!!! Happy New Year! Rand

I see it but I won't be home to see the lights flash. I figured I could bother the kids with it

The interface functions as expected on my Dell Axim X51V with WM5. Rand

It should take about 10 minutes to do. I only included one light in the scene to experiment with so I sort of snuck it around the wife until midnight tomorrow Just don't over-do it with hours of lights flashing and it should be good. Maybe include the bedroom lights beckoning 10 minutes later... Happy New Year! Rand

From what I have been reading on forums the Motion Sensors need substantial time (5 minutes?) between operations. Rand

Midnight If Time is 12:00:00AM on 2009/01/01 Then Run Program 'Flash Lights' (Then Path) Wait 5 seconds Stop program 'Flash Lights' Set Scene 'New Year Lights' On Else - No Actions - (To add one, press 'Action') Flash Lights If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 1 second Set Scene 'New Year Lights' Fast On Set Scene 'New Year Lights' Fast Off Set Scene 'New Year Lights' Fast On Set Scene 'New Year Lights' Fast Off Else - No Actions - (To add one, press 'Action') The New Year Lights scene was created just for this program. I included most of the common lights in our home. Checking the Apply Changes To All Devices box I set the ramp rate at 4.5 seconds. Then I unchecked that box and using the current levels displayed in the upper pane I set the On Level for each device (our Evening scenario) so when the program is done flashing the lights they are all returned to a normal value. When Variables are available it will be possible to read and store the current level of each lamp before the flashing begins, but for now, and with the devices I included in the scene, these defaults should work well for ending the show. Rand

At least you have that option now. I'm pretty sure there were earlier (pre final release) 2.6.13 drops that did not have the Advanced option yet. These were made available for testing, but were not yet official. Jim H. Well 2.6.13 is not "official" either. Several errors have already been discovered. The last official release is v.2.6 The last most stable beta was 2.6.7, IMHO. That said, Automatic is working well here. If you have a backup Restore ISY could help you get going again. Downgrading is always an option as well. Restore ISY should definitely be used when downgrading. I will post a Flash Lights program in the How-Tos, I like that idea! Edit: Here it is. Rand

You need to create new scenes that contain only the KPL buttons as responders instead of using the scenes the buttons control. Rand

Since Insteon is so slow to make these changes it is in your best interest to perform each group change manually and watch the results. Once the changes are complete the group commands are very quick. Rand

Sorry, now I see my 2440 RemoteLincs are displayed as Icon RemoteLincs. It must be a glitch in the new ISY firmware. Meanwhile the RemoteLincs continue to function properly. We will have to get Michel to add this to the bugs. Rand

You are right in that the 2440 is not in the drop down list when you cancel the first requester. But if you put the 2440 in link mode and click okay in the first requester (Link Management/Link RemoteLinc) it will add as a 2440. That may be why your program isn't working. Delete the device. Perform a factory reset on the RL and re-add it. Your program is not necessary. That's not to say it shouldn't work, it should. But the preferred method to achieve your goal would be to create a scene containing the Christmas Tree and the RemoteLinc button. The ISY will create the links between the devices and the ISY will not be involved in the execution. Rand

When using Direct Commands most devices use the last ramp rate called. This applies to using the ISY commands on devices, either directly or in programs. When scenes are called ramp rates programmed into the responder for that scene are used. Your best choice is to use nothing but scenes in your programs so you always control the ramp rate. When a direct command is used to change a level the device may use a long ramp rate and the level may not appear to be changing. A query will always return the target level. To test for this you can use a Bright or Dim command. The device will jump to it's target level before responding to the command. Rand

IIRC, it was digger who finally found he had SwitchLincs that were broadcasting noise. Perhaps you have one of these on the circuit with the problem. Pulling the set buttons on your switches will disable them. If things begin to work reactivate them one at a time. Just a thought. Rand

Simply add the new KPL button as a controller to the scene. Then select that button in the scene and use Copy Scene Attributes from ... The same way Rand