paws

That's what I feared. Thanks for the quick replies!

I'm in somewhat of the same boat as the OP (of this thread? My 994i may not be dead but it is well into dementia. It has been going downhill for a couple of years but lately it's gone off a cliff: Weird stuff like double-tapping a switch for the basement lights now turns on/off all the nightime yard security lights, and pressing a remote to trigger the I/O Link to add a squirt of water to the birdbath turns on almost all of the shop bay lights. I've changed the power supply with no improvement but I fear that it is way too late to try the SD card since backups take over an hour and generate several error pop-ups so I have no faith in them. So I bought a Polisy and plan to start from absolute zero: reentering the dozens of Insteon devices and recreating the programs that I actually need (in truth this purge is long overdue as the ISY is the result of almost 15 years of adding stuff in a haphazard way). Using some great guides here, e.g., dbwarner5's ISY-to-Polisy migration compilation, I think I have screen-shotted or downloaded every possible setting, program, and node so I am ready to go back to the Dark Ages for a few days as I rebuild. My fear is that some of the old will somehow sneak into the shiny Polisy. Obviously the PLM will get a factory reset. Do I need to do resets on the devices, as well, particularly the switches that were set up as three (or four) way devices by creating scenes, and the EISO8SA's?

I obviously need to be more clever. The two-program thing should work marvelously! Even if sunset went after midnight (that starts roughly 50 miles north of here) you'd only have the problem on night a year: Every summer there would be the day with no sunset at all as the time went from the PM side of midnight to the AM side, but I can live with that because (a) it is once a year, and ( it is someone else's problem! Off the technical topic, the sunset problem we have in Alaska (sorry - I would have mentioned where I live before - I didn't know that my profile edit didn't take) is two-fold: First, there's that pesky DST, which artificially moves it one hour later (yeah, like DST makes any difference up here!). Then there was the bright idea about twenty years ago to change our time zones, going from four (the same number as the entire Lower 48 states) to two, and guess which way we jumped? Now we have the equivalent of double-DST, so a 10 PM sunset, solar time, falls at midnight. More importantly, solar noon is at 2 PM, and I always said that I wasn't getting out of bed before noon once I retired, so now I have to find stuff to do in bed until 2 PM. Nice to have a notebook computer! Thanks for the quick replies! You'll probably hear a lot more form me: After reading the forum I found all sorts of marvelous applications for the ISY that make my few, simple programs look pretty pathetic, so it's time to start experimenting. Who knows what sort of trouble I can get into? Jim

I have a simple, one condition, one action program that turns on my yard lights 20 minutes after sunset. It worked fine for a time, then started working only every other day. Looking at the Program Summary page I found that it wasn't a communication problem, but the scheduling itself: After each run it showed the next one would be two days hence. My assumption is that it is somehow related to the fact that 20 minutes after sunset actually falls on the next calendar day due to my latitude (a bit farther north sunset itself is the next day). Perhaps the ISY-99 will not run a "daily" program more than once a day, so it doesn't even examine it to determine that it really will be run the next day, not twice in the same one? Kind of hard to describe what I'm trying to say here. At any rate, I can certainly do a work-around, like just telling it to execute, say, 10 minutes after sunset (I think our sunset never gets past 11:50 PM), I was just wondering if there is some more elegant way of doing it - might be useful for anyone living a few miles up north of here. Thanks! Jim