Richard

Hi Michael, When I began this thread, I did have the ISY99i configured with a static IP outside my router's DHCP range. But as indicated in my first post, with the static IP, I was not able to configure the Default Gateway and DNS settings in the ISY99i to allow for e-mail notifications and clock synchronization. Perhaps, now that I know a bit more, the problem was that I didn't use upper case when trying to make changes in the ISY99i through telnet. If my router starts bouncing around the IP address with DHCP enabled in the ISY99i, I can give the static address a try once again, using upper case. Richard

Hi Michel, Thanks for taking the time the check out the router manual. I do keep the ISY99i on 24/7. I'll watch to see how stable the IP stays for the controller. If it does jump around, I can look for an alternative router -- or see if one of the open source firmware options for my current router, such as DD-WRT does include DHCP reservation. In the meantime, I believe that everything here now is functioning the way its supposed to function. Perhaps it won't be too long before my low priority requests for some additions to the programming capability of the ISY99i can get done. Then I'd be 100% happy. Best regards, Richard

Hi Michel, Thanks for your suggestion. Now I need to know how to do this in my router. The only thing I can figure might work is the advanced router screen which allows the user to set up a static route between the Router and another network. But the ISY99i isn't a network. Jacques' posting has a link to the manual for my router. Is there anything else in the firmware which would allow me to do what you recommend? By the way, for the first time today I was able to access the ISY99i from my office. I turned on a light from the office -- it was on when I came home. Wow!!! Richard

Yes, Michel, that was the problem. I was using a lower case y, not capital Y. I have finally enabled DHCP on the ISY99i. E-mail notification now works and the clock synchronized over the internet. Now I have to see if I can still access the controller remotely. Thanks, as always. Richard

Jacques, I've downloaded the manual for my router and tried your suggestions. I've configured the router as a DHCP server as per the manual and tried to set the ISY99i to let the router as a DHCP server set it's IP address by accessing the controller through telnet and using the CT command. Even though I reset the IP address at 0.0.0.0 rather than its current static address of 192.168.1.49, and I say yes to being asked whether to enable DHCP, after I reboot it retains the static address. When I look at the client table in the router, the ISY99i is not listed, since the ...49 address is outside the DHCP range I've set. And with the static address I am not able to set the default gateway address in the ISY99i to be the router's address of 192.168.1.1. I will mention that I had trouble gaining access to the ISY99i through a remote internet browser when I first got the controller. Through a series of e-mails with Michel Kohanim, I ended up using the static address and a specified port which I've set to be open on my router. One of the problems I had at that time was the phone adapter which I use for Vonage. It was connected between the router and the internet, causing problems with addressing. I ended up moving the phone adapter to sit behind the router instead of in front of it. That allowed the addressing to work properly. I would think it now shouldn't have any effect on the functioning of the ISY99i. Any further suggestions from you or others will be appreciated. Richard

Hi Jacques, My router, a Linksys WRT54GL, is set to be a DHCP server. but I don't see where in the router's firmware I can create a DHCP entry for my controller. Also, when I try to set the controller to request a DHCP assigned IP address, following the instructions in the ISY Advanced Configuration Guide, it fails to release the static IP address. I'm stumped and my knowledge on how these things work is limited. Will I have to do a factory reset, and if so, will I lose my programs and device links? Further suggestion will be appreciated. Richard

Jacques, Every time I try to change the Default Gateway in the ISY99i through telnet, using the CT command, the change seems to be there initially; but when I run through the CT command again, whether or not I've exited and reentered the controller through telnet, the address reverts to the yy.yy.103.15 address. Why won't it hold the address I'm trying to change to? Would that have anything to do with the difference in the subnet mask address? Richard

I've sorted through a number of issues with great help from the forum and staff of Universal Devices, and I'm very happy with how my ISY99i performs. But I have yet to get my e-mail notifications and internet clock synchronization working. With the clock, I can synchronize with my PC but fail to get a connection with a time server over the internet. When I click to "synchronize now" with the NTP server I get the following error message: [-60001]NTP Server DNS Error[pool.ntp.org]. With e-mail notifications, I've run the test using a gmail account and an account going through another server. I've tried the settings suggested in a couple of threads on the forum, all to no avail. This is the error message I get for this: [-50010]Mail Server DNS error[Null]. I've checked the IP settings on my router and the ISY99i. I don't know if there is a discrepancy which could be the source of the problem. Here are the numbers: Router: IP Address: xx.xxx.89.9 Subnet Mask: 255.255.240.0 Default Gateway: xx.xxx.80.1 DNS 1: yy.yy.103.15 DNS 2: yy.yy.103.16 ISY99i [from telnet access]: IP Address: 192.168.1.zz Subnet Mask: 255.255.255.0 Default Gateway: yy.yy.103.15 DNS Server: yy.yy.103.16 The subnet masks differ, the default gateway on the ISY99i = the DNS1 on the Router, and the DNS Server on the ISY99i = DNS2 on the router. Would appreciate assistance.

I should have said everything ELSE!!!

Everything appears to be working just fine. I guess the device has gone bad. I'll contact Smarthome about a warranty replacement. Thanks Michel.

Michel, I couldn't piggy-back the icon adapter because of a piggy-backed access point, but I did plug it into the same outlet as the PLM is plugged into. I also waited a couple of minutes before plugging it in, Brian. Same error message - [-200000] node not added - failed reading links. While the ISY99 is trying to link this message also pops up: "failed getting engine version - reverting to i1. Any firmer diagnosis? Richard

The other day one of my three Icon applicance adapters stopped responding to on/off commands. It is still plugged in OK. I performed a reboot of the ISY99, then removed the device in the administrative console and tried to relink it. I get this error message: [-200000] node not added - failed reading links [] Has the device gone bad, or is there some kind of test I can do to see?