Troubleshooting controllers
The following table lists troubleshooting problems on Control4 system controllers.
Symptom |
Possible problems and solutions |
The controller has N/A for IP address |
1. The controller has no network connection. Plug in your Ethernet cable. After a few moments, the addresses should appear. 2. The power cable is not plugged in. Plug in your power cable. 3. No DHCP on the network. Ensure that DHCP is operational. |
The controller has a blank front display |
1. Either your cables are unplugged, or they are not connected. If both are connected, unplug them and connect the Ethernet cable before connecting the power cord. 2. The controller is not connected to a cable/modem/switch/ using DHCP. 3. Ensure that the Reset button is not jammed behind the plastic cover (older controllers only). |
The controller doesn't come back up after a power outage |
To receive a notification of the controller going down and coming back up, set up an Email Notification agent to alert you when the project is loaded and the controller comes back up. When you create the alert, place the alert on the project (Device Events top level). See "Using the Email Notification agent.” |