JWBDolphins

Thanks @Geddy @Techman and @paulbates. The next run time/dates look correct, and its been running fine since my initial post! If I see any more issues, I'll dig into it deeper and create a ticket if I need to. I very much enjoy the EISY - need to see what I can make it do next!

I'm seeing the same issue and I'm running 12-hour format. I switched from ISY (where it ran perfectly) to EISY two days ago, and now some of my From/To using Sunset/Sunrise (next day) programs appear to not be running correctly. The port went great, I have a new PLM (replaced a bad one a couple weeks ago) and all my scenes, etc look to be correct. I'm betting (hoping) there's a bug somewhere with this on the EISY. I need to go back and pay more attention while running some tests, but I swear that during the "Then" time of day, if I run the program Run If - the Then doesn't trip. It Does appear that the Else portion Is running when the time period expires - its just the Then portion that doesn't seem to trip correctly. I have several programs running for different locations - front porch light, coach lights, low-voltage landscaping lights, and they All don't turn ON (then portion) but when I turn them on by hand, they do turn OFF correctly (else portion.) I HOPE what I said here makes sense!

In Admin Console when you Disable a device, does it actually WRITE anything to the device? In other words, does the device need to be plugged in?, or does it just flag it in Admin Console (and possibly write it to the PLM) to not look for that device on Admin Console startup? I've searched for this but haven't found anything. The issue is around the holidays I normally add a lot of devices to control lights and then take them down and pack them up for next year. And I inevitably Forget to disable them from Admin Console. Every time I open Admin Console I get the list of dialogs saying it can't find device X, etc. It comes down to, can I just Disable them in Admin Console, or do I physically need to have the devices plugged in at that time too? I'm Guessing its the former. Thanks!

That makes perfect sense - Thank You! Once it <Clicked> in my head, it clicked. It just took way too long to click than I want to admit!

Maybe stating it this way might be useful - this is what was confusing me. For this type of program: IF Control device x is switched on And Control device x is not switched off The Switched On made perfect sense to me, and the Not Switched Off I took literally. I thought a Fade Up would mean the "Switched On" would fail while the "Not Switched Off" (because it was a Fade Up) would succeed. The combination AND'd would fail, so the Else path would run. But that's not what it does - a "Fade Up" would never cause this program to run in the first place - That's the part I was missing. The Only Control messages being looked for to trigger this program are "On" and "Off", and then the "is" and "is not" are evaluated as part of the IF. As apostolakisl said:

Excellent thread! Stusview's Post #12 finally snapped in my head! I've been wondering for way too long why so many examples have the added condition "And Control 'devicel' is not switched Off" added to them, to the point that I've been adding it to my programs "just because". There are a lot of posts that touch on this, but that post Finally explicitly makes sense to me - thank you! And I should add, apostolakisl's post (#13) containing the previous post and an excellent explanation would be something I would consider making sticky as far as "how to program the ISY". I've bookmarked this discussion. Maybe I'm just dense, but up until now I never really got it.

Thanks Teken! - I can see where that would be a lot of work keeping up with all the option changes between versions in all the devices. Like I said, it hasn't been a problem, but I was wondering about that.

I have a curiosity question about certain Insteon device options that don't appear in the ISY. An example of this would be Load Sense on the Outdoor On/Off module. I can turn Load Sense on or off directly on the Outdoor module, but I don't see an option to set this from the ISY. Is this because some devices don't expose some options that could be changed programmatically? Are there too many "tweaks" that can change between hardware versions within a device line to keep up with (for example, LampLincs no longer support Load Sense - which will be a another question I'll post shortly) so just the most common ones are available? I suspect the answer is probably a combination of these and maybe other factors. This has never been a problem, but I've been curious.

I (to date myself) have been messing around with X10 since back in my jr high and high school days when they first came out in the '70s. (I have an original brown BSR Lamp Module that still works today.) Last year I moved into Insteon and bought an ISY - an Amazing piece of technology. What really kick-started my understand of how to program the ISY is the Leak Sensor program package that Belias so kindly posted: http://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/ First of all, if you have a Leak Sensor, this set of programs is indispensable. But beyond that, this set of programs touches just about every aspect of ISY programming from variables to control messages to notifications to start-up processes, etc. as well as being nice and concise. I tweaked a lot of things in these programs just to see what would happen. Once you understand all of the subtleties in each of these programs, you will be well on your way to knowing how to program the ISY.