Control4: Diagnostics shows "Filename is Correct: Problem detected"

Symptoms

When a driver has been renamed incorrectly and then added to Control4, when running Chowmain diagnostics, you may get a diagnostic which looks like: 

Filename Is Correct: Problem Detected
  This filename for this driver has been renamed incorrectly which may affect auto-updates and driver operation. No Support is available for renamed drivers and it is recommended to remove the devices and reinstall with the correct filename. The Driver Name Should Be: chowmain_elk_m1_v2.c4z. The Detected Name is: chowmain_elk_m1_v2 (2).c4z

This issue may cause a wide variety of issues including:

1. Drivers which use a master/agent driver may not operate reliably, as drivers in some circumstances
   
2. Drivers which use a "Device selection" action / command / Property may not see the affected drivers 
3. If Chowmain/Project Agent was incorrectly named, drivers will not see Chowmain Agent and will pick-up 0 drivers. 
4. Auto Update for affected drivers will not work at all, and upgrades will not work  
   

Due to the wide range of issues which are caused by this issue, Chowmain is unable to provide technical support for drivers which have had the filename renamed

Causes

This is caused by renaming the driver filename before adding it to the project. Most commonly, by accidentally copying it in windows (chowmain_driver (2).c4z) or explicitly in the past, someone has renamed the driver with a version, or a project name. 

 

Solution

Unfortunately, Control4 does not provide a way to fix a driver filename once added to the project without removing the broken drivers and reprogramming. The recommended course of action is to:

1. Check your local Control4 drivers directory to ensure that the driver with the incorrect filename isn't in there. This is generally found in: C:\Users\USERNAME\Documents\Control4\Drivers. If so, remove the driver to prevent it being added accidentally to new projects 
2. Backup the project
   
3. Ensure you have a copy of all the programming, and bindings. You can use Detective Suite to assist
   
4. Remove the bad device from the project
   
5. Install a copy of the driver which uses the correct filename
   
6. Reprogram 
   
7. You may also need to migrate to Chowmain Licencing: https://help.chowmain.software/portal/en/kb/articles/how-to-drivercentral-licence-migration

• Related Articles

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

• Control4 Govee: Some Cloud Lighting/Outlet Devices are not being detected / Discovered

  Some Devices (in particular, many light bulbs including the H600D) require an upgrade to our Govee V3 Driver to operate. V1/V2 will not detect many modern devices. Govee V3 utilises the "Awesome New API" (sic) from Govee and is a free upgrade for ...

• Control4 Hisense VIDAA - Device Management Menu does not show

  If the Device Management menu doesn't show, take the following troubleshooting steps Ensure the TV firmware is up to date. The Device Management menu may not be available on older firmware versions. Version 9 or later is required (Under About, ...

• Control4 TP-Link: Unable to Control Device

  General Issues If you are using Control4 4.0.0 or later , you must be using version 20250721 minimum for full support in all drivers. In particular, Versions older than 20241209 will not operate in X4 at all due to changes in Control4, and must be ...

• Control4 ELK M1: Zone status does not correctly respond properly or Realtime status is not correct

  Ensure you are using the latest version of our ELK M1 V2 driver. You can identify this by right clicking on the device in System Design on Composer, and pressing Get Info. The filename must say chowmain_elk_m1_v2.c4z. If the original filename of the ...