RobT

I am having the same problem as Big Moose except that I have not replaced my PLM. Test notifications work as programmed 100% of the time but an actual line of code that turns a switch on under a specified condition (verified that the action completes) followed by a line of code that should send a notification fails. It used to send with no errors.

This is a great question. I can think of a few devices, a repeater especially, that might possibly be serving an address. It should be in a different range but worth a check.

Teken, Your recap is essentially correct. To clarify, the router was still reserving, say, 110 for the ISY but the router's attached devices table was showing that the router was serving the ISY at 111 and that there were no devices attached at 110. The configuration page on the ISY was showing 111. MWareman, Your explanation makes sense. I had not thought of it. The only downside I see is that we have to assume that the ISY rebooted somewhere along the way. So far as I know, there is no way to confirm this. It would not be a power failure. The ISY and router are on a UPS the logs of which show only two brief failures during the period in question. Power would have been 100%, well regulated and filtered. Might the ISY have renewed it's DHCP lease somewhere along the way? If so, why did it renew at a different address?

Problem found! Even though the router had reserved one fixed IP address based on the MAC address of the ISY but the local IP in the ISY configuration was different. The router's reservation was still in place but the ISY was now showing up with a different IP on the table of unreserved attached devices. I confirmed that I had left the DHCP on in the ISY. I have now turned ISY's DHCP off. I have not seen this before (it should not happen). It is even more puzzling that the change took place one day after six straight months of unremarkable with no intervening changes or reboots, etc. If the addresses change again, we will know we have some kind of firmware glitch on one side or the other. Thanks to everyone for their help.

Teken, The AV program is going to vary with the particular workstation and I have none on the iPad or smart phone. I'm going to verify that the port forwarding and internal IPs still line up. I'll report back. On the certificate, I would like to learn how to install one. Six months ago, I added the standard "trust this non-certificated URL" exceptions to Chrome and Firefox. Since I sync browsers fully across client machines, I only had to add the exceptions once per brand. Recall, though, that these non-certificated exceptions were working fine for six months. In addition, I am not getting the typical "certificate" warnings on any of the browsers. I get the "not found" and unable to connect" messages, depending on the browser. It is also possible that browsers change their rules without notice but the chance that Chrome and Firefox would do it on the same day is slim and, in addition, my other trust this URL exceptions are still working fine (I have cameras, remote storage, etc. on the same LAN and router). . . . just the ISY in the crowd.

PaulBates -- I mean WAN or LAN. I can access and control normally using the UDA Console locally.

Correct on the reservation. This is the only device no longer getting in. I have the ISY white-listed on the windows client firewalls but no such options on the AV and none have inquired for an exception. In addition, recall that all remote clients are failing, including iOS, Android, and Windows. When I get in front of the ISY, I'm going to toggle DHCP off, remove and replace the router reservation (maybe changing the IP at the same time), reboot all ans see how that goes. It is a bit unusual. I thought perhaps the issue had shown up for someone else. Any other suggestions? Thanks!

I think I left the ISY DHCP. I'll check but I have the router locked to serving it a fixed IP.

For the first six months after installing the ISY-994i, remote web access and control worked perfectly. I had it configured on my iPad, smart phone, and remote computers. One morning, access was no longer possible on any client. Nothing has changed in any configuration (ISY, clients, router, ISP, bandwidth, traffic, addresses, etc.) and all other remote access devices are working via the same router and analogous configurations exactly the same as before. I have rebooted the ISY a couple of times and tried toggling the "Enable/Disable Internet Access" a few times. No joy. Just today, I upgraded the ISY firmware to the latest version. No change in behavior. I also checked to ensure that the ISY retained the correct configurations. It had. Suggestions? Thanks.