CPrince

Follow up. I spent an hour trying to clear the communications error. Finally got up out of my chair and over to the KeypadLinc and pressed some buttons. I went back to my desk and I cleared the communications error instantly. The KeypadLinc must have locked up or something. I added a 5 second delays in both programs. As far as the LED's turning on at night for no reason, I am thinking it is a HouseLinc issue. HouseLinc runs a maintenance routine at 1 AM. HouseLinc is no longer running. Now I just have to wait an see. Thanks again.

Guy's thanks! Okay I am migrating from HouseLinc to ISY. These were the last 2 programs to be migrated from HouseLink to ISY out of about 75. I actually migrated them to ISY but started having issues with both. So I disabled on ISY and renabled on HouseLinc. They were not running concurrently on both ISY and HouseLinc. Both PLMs were plugged into the same extension cord and not a surge protector or UPS. They were not piggie backed. Both switches are dual band and the keypadlinc is Keypad with Dimmer[2334-232]. The PLMs are current version. I just pulled the PLM for HouseLinc and re enabled the programs on ISY. I will see what it does. Hey my luck day. Routine just ran with HouseLinc PLM removed and we are still failing. Tabletop Box.1,A,B,C and D are the LeypadLinc. II will try adding "wait"s to the program. Attached are the 2 programs Thanks for your help.

I have a SwitchLinc dimmer, SwitchLinc on/off and KeypadLinc 5 button, mounted in a box that sits by my bed. The SwithLinc on/off turns most of the lights in the house off or on by a program that catches the on or off pressed on the switch by ISY. This seems to work pretty well. I had to insert some "waits" to increase reliability. The SwithLink dimmers is directly linked to my bedroom lights, it doesn't need ISY to function. This works well too. The KeypadLinc is using 4 scenes to set the fan high, med, low and off. I copied this out of the ISY Cookbook. This works well too. So my problem is the LED's on the 3 switches. I have 2 simple programs. On sunrise +2 set the SwitchLinks LED's to 20% and the KeypadLinc to on 6/ off 1. Then I have another program that at Sunset +2, turn the SwitchLinc LED's to 0% and KeypadLinc to on 0/ off 0. This is so hit and miss it is driving me crazy. The the LED's on the SwitchLinks turn on in the wee hours of the morning, sometimes. This is usually followed by a red exclamation mark in the devices list. It takes forever to clear the exclamation mark. I get a communication error. I have to query and do write updates many times to reset the KeypadLinc. I have had this running on my HouseLinc with no issues for over a year. The HouseLink PLM is plugged into the same outlet as the ISY PLM. This is the only program left running in HousLinc. Obviously I am not running the same routine on both devices at the same time.

I am about 99% complete as far as moving all my HouseLinc programs and devices to an ISY944i. I have been on HouseLinc maybe 10 years. In the process of moving my devices using the spider method with keep all links, I have acquired about 7 scenes that I don't have a clue what they are. I have 2 scenes with all responders and 1 scene with the old HouseLinc PLM. Then I have some crazy scenes like the washing machine appliance module controlling the front porch light. I assume I can safely delete these? Now the smoke detector controlling the bedroom light I would keep. While I am working on scenes (I am old school X10/Insteon 35/10 years) I would write a program like bedroom off, living room off, dinning room off, kitchen off, etc., etc. for a bed time routine. I am seeing iISY is hit and miss in this area. Isy might miss the kitchen light and leave it on. I don't know if it is because HouseLinc is USB and ISY serial. So I have added a wait 1 between each off. This seems to be more reliable. Would a better solution be creating a scene?

@gzaharYour explanation was spot on. I read the first three words and it instantly made sense. @MrBilland @apostolakislYou guys really drove it home with your in-depth explanations. Thanks so much

Mr Bill, My brain is fried. The second example worked fine. At first I thought it didn't. Review of the security cameras proved that it did. I am at a lose with the "for" argument. I did a lot of reading on it and am no better off. I am reading the 700 page ISY Automation Cookbook. What does the 6 represent? I changed it to 2 as I thought it was going shut the lights off in 2 hours. Wrong.

MrBill, sorry I did not see you full response to the second part. let me review,

MrBill, thanks for the fast response. You first solution is spot on. I had to poke around to find the settings. It was a great learning experience. The second example makes some sense, but is not clicking. I may be a bit slow. Sorry. So it has to be sunrise -30 (4:45 currently) and 5:30. to hold off turning the light on at 5:30. It should work today and for a few months. But the window from 4:45 to 5:30 will be locked in because of the and 5:30? So what happens in December? Sunrise -30 (6:00 December time) and 5:30. Won't the 5:30 make the logic false? Doesn't the and 5:30 kinda hardwire it in? Thanks so much!

I would like to do some more advanced sunrise/sunset programs. Sunrise/sunset is relative to the earth and the sun, but not really the time of day. Time of day is a constant and sunrise/sunset is variable. With that being said if I want to to turn my porch light on at sunset -30 minutes and off 6 hours later in the month of December it will be different in July. In the winter the light would come on around 4:30 and turn off around 10:30. This is good. However running this is July will turn the lights on around 8:00 and off at 2AM. This is bad. I thought of breaking this down in to 2 separate programs. One to turn on the lights and 1 to turn off the lights. However I don't want them going off at the exit same time every day. Maybe 10 PM plus or minus 30 random minutes. I can't see how to do a plus or minus random number. Every controller I have worked with has had this function. Another issue is the lights in th AM. Lets say I want the lights to come on at sunrise -30 minutes but not before 5:30. Sunrise right now is 5:30. So the lights turn on at 4:45. This is bad. In December the lights would come on at 5:45. This is good. I am new to this device, sorry if this has been asked many times.