ben-smith

Thanks, these posts were helpful to get my 'every other' day schedule running.

Maybe I just haven't had enough coffee yet, trying to figure out a watering schedule for my in-laws property. He'd like the zones watered 20 minutes each, every other day. I've got the zone timings OK, just trying to figure out how to have the program evaluate running 'every other' day. Thanks,

Maybe I just haven't had enough coffee yet, trying to figure out a watering schedule for my in-laws property. He'd like the zones watered 20 minutes each, every other day. I've got the zone timings OK, just trying to figure out how to have the program evaluate running 'every other' day. Thanks,

Try TLS, and on port 587.

I wonder if your ISY is having a DNS issue? Try 76.13.12.104 for the SMTP server address and see what it does.

Try smtp.sbcglobal.yahoo.com instead. Leave everything else the same...

Anyone else having trouble with a V2 thermostat adapter since this update? 2.8.10 went on just fine, but there is a '101001' icon next to the thermostat entries. It seems to be receiving feedback from the thermostat adapter since the correct temperature and setbacks are shown in ISY, I just cannot adjust them, it says 'request failed'. All other insteon devices are working normally. I had a similar issue when updating to 2.8.9, but it corrected itself mysteriously.

Currently, the ISY cannot determine a WAN IP address. As mentioned in other threads, UDI would likely have to set up a contract / royalty payment arrangement with a third party that returns your WAN IP address from a HTTP request. Router manufacturers don't need to involve third parties because their device (the router) is directly connected to the WAN, and therefore no outside 'what is my IP' inquiry is needed. Your workaround sounds feasible. You could also make sure that your ISY is set to run that particular program on system startup, so you don't need to wait for the specific time slot to roll around. You could also put your DSL router on a small UPS. Even the smallest entry level units would hold a DSL modem a LONG time in a power outage. Then you're not likely to get a new IP. I had to replace a DSL modem for a client recently, they have Verizon / Frontier, whatever it's called now. We used an ActionTec GT704-WG, and that had DDNS built in. I bought it for $20 off ebay. EDIT: GT-704-WG doesn't do DDNS, I must have been thinking of another device... How about getting just a plain/jane DSL modem, and piggy back that to a wireless router of your choice?

I set up my Windows machines to 'sleep' the system after x amount of inactivity. (From the Control Panel). In addition to that, you can also set up a scheduled task on the Windows machine to shut down at a certain time. (shutdown.exe -s -t 1 -f)

Thanks for the post, GPG. I was originally considering the GC-100's, but those probably have more functionality than I really need. So, I'm thinking that these iTach devices will work out just fine.

I used to work at a Mountain Mikes - they didn't offer delivery, though, liability was too expensive.

Here's something I noticed about the networking module... I was setting up a couple of Wake On Lan configurations, and couldn't get it to work. Then I finally realized that the broadcast address still had a .0 subnet as it comes out of the box. (My subnet is 192.168.5.x) So, changing that to a 5 took care of it. There's probably no need or high demand to automate that value based on the subnet the ISY is on. This is more of just a heads up for those that want to use WOL.

Thanks for the replies, I'll probably just have to clam up for now, wait till my ISY arrives, and go from there. Kingwr: Good question, why would I need to do that? I was probably just more curious than anything else. I suppose that a fast on to turn on ALL outside lights from any of the 4 keypads would be convenient, easy, and sufficient. Probably less load on the ISY, less code to chew on.

Yeah, the latter is what I need... (Check for the next OFF light, and switch it on). Probably best to wait until I get the ISY installed and start playing. Can you nest additional if/then statements like so? : If Control 'NorthLights' is switched Fast On Then ( If Status 'SouthLights' is Off and If Status 'EastLights' is Off and If Status 'WestLights' is Off ) Then set 'SouthLights' On Else

Hello, ISY newb here, long time lurker, still waiting for my ISY to arrive. I've been reading the archives to get a handle on how some of my programs will work. My system is going to start with 4 SWL's, each with a load that controls an outside light. (N, S, E, and W). I want to set them up so that if I operate a SWL 'fast on', it will turn on the next 'off' light of the group, but not all 4. In this example, this would switch them ALL on on a Fast On command. But in reality, I'd want it to break the routine once it turns on the first Off device. (Does that make sense?) If Control 'NorthLights' is switched Fast On Then Set 'NorthLights' On Set 'SouthLights' On Set 'EastLights' On Set 'WestLights' On Else