I am having trouble communicating w/EZ Rain through Izy, whereas I was able to a month ago. There has been chages yo my setup so I am not surprised but confused to diagnose and fix the issue.

 

I have changed ISP so my IP addresses have changed and I edited all that

 

When I first go to the admin console and sign on I am getting several Cannot Communicate with Name and Address Please check connections. Those devices also have an "!"next to them on the My Lighting list. If I OK through all the warning pop ups and try to "restore" any of the "!" devices I get a system busy progress bar where the program goes through every device, not just the one picked and list an error message Socket open failed, Java.Net.Socket Timeout Exception.

 

If I go to manual control of the listed devices I can controll all but E-Z-Rain. The scheduled or daylight event based programs except irrigate works.

 

I am not sure how to proceed with an orderly diagnosis. Is there a way to poll an individual device and try to see if there is communication?

Hello Dogan Bora,

 

The first thing is that you should not Restore devices if you cannot communicate with them. If my suspicions are correct, you now have a green 01010 icon next to your irrigation zones. Is this the case?

 

If so, the problem is that for some reason the signals are not getting from the PLM to EZRain. Is it possible to move EZRain closer to the PLM and retry. Please note that if you have green 01010 icons, the first thing you have to do (after your bring EZRain closer to the PLM) is to Right Mouse Click on any of the Zones and then choose Write pending updates ...

 

 

With kind regards,

Michel

You are correct w/ the Grn 01010, the distance to the plm has only changed vertically, EZ Rain and the pc/nETHub PLM was connected to was 30 feet accross the kitchen now it is 30 ft plus the 10 ft to get to the office.

 

I will try these and report.

 

Thanks

Physical distance sometimes can be deceiving.

If the present location is on a different circuit than where it was.

There is a possibility of communications issues.