New ISP -> Notifications & Climate Suddenly Dead

[cdneh]

I'm totally stuck.

 

Long time ISY user (ISY 994irPRO f/w v4.2.30). I have dozens of notifications set up -- using Gmail SMTP/TLS -- which have been happily running for a few years.  

 

We changed Cdn ISPs (from Rogers to Teksavvy, both over cable) on June 23 and suddenly notifications went dead. Test messages elicit error messages in the form:

                 "Mail Server DNS Error / [[sMTP_ERRORS-smtp.gmail.com]]"

 

For timeouts below 10,000, I'm also seeing:

                 "TCP client DNS error / [api.areisapi.com]

 

My initial thought was the ISP was the culprit but I've been back and forth with them trying different DNS targets without change. Then it dawned on me that my Synology NAS also sends notifications utilizing exactly the same Gmail SMTP service and credentials. It continues to function perfectly.

 

I've also tried an alternative -- i.e., not Gmail -- SMTP server with exactly the same error results.

 

Finally, I just realized my climate module is also dead and will not connect to any of the multiple local and remote sources I've tried. However, I cannot be sure that the climate module failure began with the ISP change or arose subsequent to my update to 4.2.30 a few days ago.

 

 

So, apart from concluding that at least part of the problem is the ISY, I'm completely stumped.  Ideas anyone? 

 

Thanks,

 

- Chris

 

[Michel Kohanim]

Hi Chris,

 

If you have configured your ISY with a static IP address, please revert to DHCP and retry. I suspect your new router does not like DHCP relay when you have a static IP address.

 

With kind regards,

Michel

[cdneh]

Michel,

 

Brilliant. Problem solved by having ISY use DHCP and having router assign a predetermined IP. Not sure why it works, but happy it does.

 

Thanks for the super quick response.

 

- Chris