Jump to content
C4 Forums | Control4

EA5 needing reboot, losing network connection (to apps)


Recommended Posts

I had an HC300 installed that worked well for over seven years. We just upgraded to the EA5. 

The EA5 requires a reboot nearly weekly. We lost control of lighting a few weeks ago, but rebooted and that issue hasn't come back; however, we are consistently losing connection to the Android app and Alexa every two weeks or so. 

The logs are filled with errors such as:

2017-02-21 21:29:35.342 -0600 ea5-000FFF1C744C [3954] ERROR: Resolve relay address: relay.control4.com Failed: -2
2017-02-21 22:36:41.285 -0600 ea5-000FFF1C744C [3954] ERROR: Resolve relay address: relay.control4.com Failed: -2
2017-02-21 22:37:41.281 -0600 ea5-000FFF1C744C [3954] ERROR: Resolve relay address: relay.control4.com

yet, DNS works just fine (using Google DNS servers at 8.8.8.8). Internet is not an issue for anything else. Network connectivity is fine for everything else. It seems to me if the EA5 can't perform a DNS resolution something is fatally wrong within the software itself. These errors (above) appear about the time the unit stopped responding to the Android App.

Other logs are filled with java exceptions, incorrect casting errors (variables apparently trying to be cast incorrectly), and even references to null variables. 

[Reconnect] WARN: Control4Director] - Disconnecting from . Due to failure? false
2017-02-23 12:08:38,767 -0600 [Reconnect] ERROR: ConnectionBroker] - C4ServiceException: java.net.SocketTimeoutException: Read timed out
2017-02-23 12:08:38,768 -0600 [Reconnect] ERROR: ConnectionBroker] - Unable to connect to My Control4 System(10.0.1.157) - control4_ea5_000FFF1C744C because of network error!
2017-02-23 12:08:38,769 -0600 [Reconnect] ERROR: Control4Director] - Unable to retrieve address


Disconnecting from . Due to failure?

I have been attempting to locate the source of the issue, but so far have had no luck. If I reboot the EA5, it will come back up and work... for a week (or so).  The unit was installed brand new in January 2017.

 

Link to comment
Share on other sites


Called. C4 support as well, but the going has been pretty slow so far (two weeks). Not sure why we haven't yet focused in on the DNS problem, but I don't really know the inner workings of the unit or what its diagnostic capabilities are.

Link to comment
Share on other sites

  • 3 weeks later...

Sorry for the delay... busy time.

The 300 is no longer being used. The 5 is on 2.9.0. 

The only other devices would be Amazon Echo devices which there are four. All of which go offline and pretty much stay offline. I pulled a Watchguard T70 from the network and put in an Araknis unit which doesn't have 1/10 the horsepower of the Watchguard to either troubleshoot or for performance. But, at least I now have an approved device on the network. 

I am beginning to suspect the problem is between the Echo and the EA5, but that is entirely a guess. 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.