Solution: The Control4 technical representative was in the area and came out to see if he could figure out what was going on with the connectivity issue. He went through the system and was not able to identify any one item that was causing the issue. He did notice that the temperature of the processor was higher than recommended, but not at a critical level. He was about to conclude that the hardware should be replaced (not under warranty) when he decided to take a long shot action of upgrading the OS to the latest level. He did not see anything in the update that would affect this issue. However in the process of upgrading the OS, he noticed an EA1 in the project which physically did not exist. This EA1 was taken out of the rack, quite some time ago, but was not removed from the project. After the upgrade, he removed the EA1 from the project and the connectivity returned. He could not explain why this blocked connectivity. The EA1 was removed long before the connectivity issue appeared. No further explanation was available.
Thank you all for your support to resolve this issue.
