GUIDE: Troubleshooting and Diagnostics with Chowmain Control4 Drivers

GUIDE: Troubleshooting and Diagnostics with Chowmain Control4 Drivers

You may need to do these steps on both the affected driver, and any subdrivers or master/agent drivers

Things to Try first

  1. Check the system is running the latest versions of all drivers.

  2. Ensure you're using a supported version of the Control4 OS. The minimum version supported will be listed in the Documentation

  3. Use the "Display Diagnostics" action (if available)

  • In Composer Pro, select Actions, and press "Display Diagnostics".

  • Check the LUA window for diagnostics output

  1. Check the quickstart and full documentation on the Chowmain website and ensure all steps have been correctly followed. Refer to documentation troubleshooting if available

  2. Check Device software / Firmware is a supported version, and upgrade/downgrade if required. Some devices will not function without the latest firmware

  3. Check device is correctly connected to both power/POE and network/serial. Check the correct connections have been made in Composer Pro.

  4. Confirm Network is operating correctly with no IP Conflicts

Capturing Logs

  1. Under the Debug Mode Property, enable "Print" or "Print and Cloud Logging" if available

  2. Set the Debug Level Property to the biggest number available (generally "7 - Debug" or "8 - Trace")

  3. Switch to the Lua tab

  4. Replicate the fault

  5. Copy and Paste the logging information. You can use Ctrl+A to select all logs at once

Submit Supplemental Troubleshooting information (Submit Diagnostics)

  1. Select Actions and use the "Submit Diagnostics" Action (if available)

  2. Switch to the LUA Window and copy the diagnostics ID

Enable Automatic Error Reporting

We only recommend doing this if advised by Support

  1. Modify the Error Reporting Property to Automatic.

Contacting Chowmain Support

Chowmain Support can be contacted via the Chowmain Website.

Please provide the following information:

  1. Detailed fault description, and how to replicate it, and what you expected to occur

  2. Captured logs

  3. Diagnostics ID from Submit Diagnostics (if available)

  4. System MAC Address (which can be obtained from the MAC Address property)

  5. Driver Version

  6. Login credentials for the manufacturers device on the mobile app (if it is controllable via App)

  7. Remote Login Account Name, Email and Password to allow remote access to the Control4 System as per our Remote Access documen


    • Related Articles

    • 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 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 ...

    • GUIDE: Troubleshooting and Diagnostics with Chowmain URC Drivers

      Overview These instructions walk through how to use the URC logging tool built into Accelerator 3. The instructions are written for using a project created in Accelerator 3 using tcm3 modules. Module Configuration Before you connect and look for logs ...

    • CONTROL4 AUTO UPDATE: Troubleshooting 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 ...

    • GUIDE: Beta Testing Chowmain Crestron Home Drivers

      Overview This document covers the manual installation, testing and removal of Crestron Home beta drivers. If you want to replace the driver from the online database, or if it's not currently there, you can manually install the driver. There are a few ...