paauto

Good news and bad news. I was able to get the ISY to wake the computer from a hibernate state (sleep) with the current configuratin I have (i.e. the ISY is hooked up to a second wireless router that serves as an access point and the PC I am waking up is connected to my main router - the one that assigns IP addresses). It does not appear that my network card allows the computer to be turned on when it is in a shut off state. Bummer b/c my objective was to be able to power it up remotely after the power went out and I was travelling. I do a lot of remoting in and need the thing on. The good news is that in messing around with the Bios I found an option to have the machine power up on certain days at a specific time. I set it to power up everyday at 8 AM, thinking if there is a power outage and I am out of town, the worse case scenario is I will have to wait until the next day for the thing to power up so I can remote in. Now I'm wondering what will happen when it trys to power up if it's already on. Tell you tomorrow!! Anyway, on to irrigation next...

By the way, when I say I have several routers what I really have is one primary router (that distributes IP address) and two linskys wireless routers that are essentially access points (i.e. they are plugged into the primary router via an ethernet cable via a WAN port).

When I have some time later today I will hook up a switch at my PC and see if that fixes the issue. That said, I did submit a ticket to UD and they are now informing me that WOL will not start up a computer that has been completely shut off and that it only works for computers that are hibernating. That was the point of this thread in the first place - how can I turn on my computer remotely after a power outage? I know that I can set a switch in Bios to turn the computer on after a power outage, but my issue is I have a UPS which shuts the computer off in a controlled fashion once a power outage occurs, so that won't work. Thoughts anyone? Is it true that WOL will not start a completly shut down computer? I can see a light on the NIC when the computer is off, so it is getting some type of power.

I don't think you need to worry about port forwarding so long as the initiating computer is on the same LAN as the ISY, but perhaps someone more knowlegable can advise... I think my issue (I have many, ha ha) has to do with the fact that my ISY is connected to a router (router 2) which in turn is connected to anothe router (router 1). The PC I am trying to wake up is connected to router 1. So, if Tom is correct, the WOC packet would need to pass thru 2 routers to get to the PC, which appears to be the issue. I am going to add a network switch at the PC I am trying to wake, and will move the ISY to that network switch. I'll report back to see if it works.

I think you got it. I have several wireless routers in my house. The ISY is connected to a different router than the PC I am attempting to wake. I will replace the router with a switch that I have laying around to see if that fixes it. I'll let you know...

Maybe I'm missing something in teh ISY's basic configuration. Do I need to enable Internet Access?

Check out this link - this is where I made the changes. Maybe that's my problem? I will reverse all of these except the BIOS and Network card. http://windows7-issues.blogspot.com/201 ... -easy.html

Thanks. Just posted a ticket. Also, can confirm that it is not a firewall issue b/c it still doesn't work when I turn off the Windows firewall. One last question - did you open a port on your router?

Thanks, will do.

Yes, it does that when I hit test.

Nothing seems to happen when I hit "Test" Confirming I did save. Just to make sure I entereed things correctly: MAC Address: entered MAC address of NIC IP Addresss: entered IP address of NIC (192.168.1.156 - which is static) Subnet: populated automatically with 255.255.255.0 Password: I didn't enter anything - should I? Calculate: populated automatically with 192.168.1.255

Thanks. I can confirm i did in fact use dashes and all caps.

No such luck. A couple of other things - BTW I am running Windows 7 Professional: I did ensure that in "Device Manager" that "Wake on Magic Packet" is enabled for the network card and in "Power Management" I confirmed all the boxes were checked (i.e. "Allow this devices to wake the computer" and "Only allow a magic packet to wake the computer" In "Programs and Features" I installed "Simple TCPIP Services" and enabled it to run in Services. Lastly, I opended UDP port 9 in Windows Firewall. I did not port forward port 9 in my router though. Do I need to becuase the ISY is on the network? Looking forward to getting this working!!

Ok - I purchased and installed the Network Module and also confirmed my computer can WOL (went to Bios settings and confirmed in Power Managment that the ability to remotely wake up is enabled). From the PC I am trying to wake remotely, I accessed the ISY and entered the machine's ethernet card MAC Address and IP address. I saved the changes and then shut down the machine. Then, I went to another PC and accessed the ISY and clicked the "Test" button and but the WOL command doesn't seem to work. Interseitng, when I access the "Resource Editor" to see the settings the IP address of the target PC is changed to the IP address of second computer. What am I missing?

Excellent - will purchase this weekend!

So, do I need to purchase the "Network Module" to trigger Wake on Lan on my PC? If so, how difficult is it to program the WOL functionality on the ISY?

Anyone have any solution as to how to turn on a computer remotely after the power fails? It seems to never fail me that when I travel on business or vacation, my house experiences a power outage and my PC (Dell Inspiron) powers down (I have a UPS, but it only provides about 20 minutes of power before shutting the PC down). I like to remote in to the PC when I’m away. I was thinking about attaching a solenoid type switch to the front of the Dell that would allow me to turn it on remotely. I was thinking of using an I/O Linc to send a pulsed “on†signal to the switch. Any thoughts?

Can I use my ISY's PLM temporarily?

Glad I asked. So, do I need to have another PLM up and running all the time to accomplish the zone 8 configuration, or is it only a one time thing?

Thanks Lee. I have a Toro Rain Sensor that I plan to adapt by wiring it into the common on the valves. Aside from that, all I want is to be able to set watering days, times and lenght of watering per zone. I also have a "master valve" (which is essentially another zone). So I can create programs within my existing ISY software to accomplish this?

What do I need to add a 6 zone irrigation program to my system? Best I can tell the EZFlora Controller and the Weatherbug module. Is that correct?

Lee I’m still having problems with my “morning timers†program (which is similar to your Start2 example above). My program starts at 6 AM and turns on a couple of lights in my kitchen for 45 minutes, then sends an off command (in the THEN statement). My power went off again sometime this morning, because at 12:30 PM I received an “ISY Reboot†e-mail. I checked the log and the THEN statement in the “morning timers†program ran, with the lights coming on then being switched off 45 minutes later. Based on our postings over the weekend, I had de-selected “Run at Startup†in the Summary tab of the programs. Interestingly, my “exterior lights†program, which runs from sunset to sunrise, never sent an OFF command to the exterior lights. Through the log, I can see the program ran properly last night, turning the lights on. When the power came on, the ISY ran a query on all devices and the Exterior Lights were in the OFF state. I can only surmise that the power went off before sunrise and when it came on the program knew the lights should be OFF. That said, I thought Insteon devices remained in the state they were in prior to a power failure when the power comes back on.

Thank you - very helfpul and I now understand.

Brian H - yes, "Catchup" was checked in the Configuration tab. Lee - I think I understand. Start2 ran becuase the IF condition had been met (ie True) whereas with Start2 the condition was not (ie False) Question - when you enable "Run at Startup", did the lights on Start1 come on? I wouldn't think so b/c the status was False. Agree on the garage sensor - they take a lot of fiddling and I did reverse things. I'll look closer at it. Thanks guys.

I'm still having issues with "Run at Startup". Our power went out today at 1 PM and came on at 1:45 PM. I have a "morning timer" program that initiates at 6 AM and turns on a few lights (sequentially over the course of a half hour) and then sends an off command in the Then statment at the end to turn them Off. They were off well before the power failed. I have the "Run at Startup" option on. When the power came on, the "morning timer" program began to execute the Then statment, turning on the lights. I also have an "evening timer" program that turns the outside lights on at dusk and off at dawn. "Run at Startup" is enabled and the lights did not come on when the power was restored. Lastly, I have a "Garage Status" program that in the IF statement queries the status of the sensor and, if open, sends me an e-mail. "Run at Startup" is not enabled. I received an e-mail at 1:45 when the power was restored. I can't seem to figure out why some programs are executing both with and without "Run at Startup" enabled?