arskiracer

Okay, makes sense. Yeah, a Not() would be great here. A separate program will get me by though. I'll know tomorrow if the way I set it up works. Thanks for the help.

So I programmed this up, and now that it's October, it is keeping the lights off for the entire month, instead of just on the 31st. I'm not sure what I did wrong, seems to be the nested AND should make it respond to month and day both. What am I doing wrong?

That would work too, but personally I don't like to create programs I know are going to stop working at some point, when I could spend slightly more time and have them be more robust. Especially because I like to set up my stuff and forget it for many years. That's the main reason I went with the isy, because the reliability is amazing and I don't have to ever mess with it. It just works, unlike my Asus router, which I have to reboot on a monthly basis, and am therefore going to replace it with a much more expensive setup from Ubiquiti, all because I want to set it and forget it. It wasn't so bad before I had kids, but now it's tough to find 15 minutes to configure anything without kids climbing all over me and pushing buttons on my keyboard. That's why it took me 2 months from when I posted this question to finally implement the 10 minute solution.

I got it working by just setting a variable for month and another for day, then in my program that turns front lights on at sunset, i just have it not run if both of those variables are 10 and 31. What I was missing previously was the little play button that changes the things you can set variables to. Didn't know about that. And I just figure if I'm home, I'll turn on the lights when I'm ready for trick-or-treaters, which will likely be before sunset anyway. I just don't like when I'm away trick-or-treating with my own kids and realize my front lights came on an hour ago and people are probably lining up at my house. Thanks everyone!

I have the latest version of the isy firmware, 5.0.16A. Thanks, I'll look into these methods when I have a sec.

I'm looking for a way to set an annual date on Oct31 to keep the front porch lights from coming on at sunset. There doesn't seem to be a way to set one day per year, regardless of the year. I have it working for the next 5 years by using a bunch of "or" arguments, but that is messy. Is there a way to have an action based on one day per year, without having to set the year?

Good point. 2413S ordered.

I have a 2413UH with the USB connection instead of Ethernet, is there an easy way to adapt it to work with the ISY994i? Maybe with the mini USB connector?

Got it. I thought it read somewhere that the 2412 was also compatible, but I must be remembering wrong. I'll try the 2413, thanks

I've never used a Universal Devices product before, but from all of the reviews I read, the ISY994i seems like it's supposed to be very reliable. I've been having trouble with my browser sometimes not connecting to the ISY Administrative Console and I'll have to power cycle the ISY. When the console does work, I can't seem to add any Insteon devices. I'm following the instructions in the manual, but when I click on the "Start Linking" button with the two arrows, there is no pop-up window as stated in the manual and nothing appears to happen. When I go to "Link Management > New Insteon Device" and manually enter an Insteon address and name, I get the error message: "Could not open file [/CONF/INSTENG.OPT] could not open config file to read [/CONF/INSTENG.OPT]" Is the config file it's complaining about located in the ISY or in the Insteon 2412N PLM? I've used the 2412N before and so it does not have the default settings, is that a problem? One more thing to note is that the TX and memory LEDs blink a little during boot-up, but RX LED comes on right away and remains on indefinitely. Is that normal behavior? Does it sound like this thing is defective and I should return it for another one? Thanks, Adrian