GUIDE: Troubleshooting and Diagnostics with Chowmain Control4 Drivers
Things to Try first
Check the system is running the latest versions of all drivers.
Ensure you're using a supported version of the Control4 OS. The minimum version supported will be listed in the Documentation
Use the "Display Diagnostics" action (if available)
In Composer Pro, select Actions, and press "Display Diagnostics".
Check the LUA window for diagnostics output
Check the quickstart and full documentation on the and ensure all steps have been correctly followed. Refer to documentation troubleshooting if available
Check Device software / Firmware is a supported version, and upgrade/downgrade if required. Some devices will not function without the latest firmware
Check device is correctly connected to both power/POE and network/serial. Check the correct connections have been made in Composer Pro.
Confirm Network is operating correctly with no IP Conflicts
Capturing Logs
Under the Debug Mode Property, enable "Print" or "Print and Cloud Logging" if available
Set the Debug Level Property to the biggest number available (generally "7 - Debug" or "8 - Trace")
Switch to the Lua tab
Replicate the fault
Copy and Paste the logging information. You can use Ctrl+A to select all logs at once
Submit Supplemental Troubleshooting information (Submit Diagnostics)
Select Actions and use the "Submit Diagnostics" Action (if available)
Switch to the LUA Window and copy the diagnostics ID
Enable Automatic Error Reporting
We only recommend doing this if advised by Support
Modify the Error Reporting Property to Automatic.
Contacting Chowmain Support
Chowmain Support can be contacted via the .
Please provide the following information:
Detailed fault description, and how to replicate it, and what you expected to occur
Captured logs
Diagnostics ID from Submit Diagnostics (if available)
System MAC Address (which can be obtained from the MAC Address property)
Driver Version
Login credentials for the manufacturers device on the mobile app (if it is controllable via App)
Related Articles
GUIDE: Troubleshooting and Diagnostics with Chowmain RTI Drivers
How to Fetch Logs for RTI To fetch the logs we need to do a little bit of config for the drivers first. Driver Config For each driver you want to log, go to the Driver Properties and look for the Debug Settings section at the bottom. To Enable the ...Control4 Govee: Enable Local Network Control and Troubleshooting Local Lights
Not all Govee lights Support LAN control (an example is that many of their GU10's only support cloud). Some lights may also offer the LAN control setting, however, the protocol may be broken. To confirm full LAN control is supported, use: ...GUIDE: Troubleshooting Control4 Driver Auto Updates
Control4 driver auto-updates rely on the Chowmain Agent being installed and running within the Control4 project. The agent manages update communication between your Control4 system and the Chowmainsoft Marketplace servers. If the agent is not ...TROUBLESHOOTING: Control4 Chowmain Project Agent: Licenced / Unlicenced / Unknown shows 0/0/0 and project does not show any drivers
Problem No devices show in portal for the project, and there are 0 devices/drivers listed on the system Display Diagnostics may show: Driver File Name [Problem Detected] Solution If the Chowmain Agent filename has been changed incorrectly before ...TROUBLESHOOTING: Control4 Memory Usage: Warning
Diagnostics show the following Memory Usage: Warning Driver Memory Consumption is higher than expected. This may be normal on some drivers. Cause This is for internal troubleshooting only and indicates that the driver may be using more memory than ...