Control4: Driver File Name: Problem detected

Control4: Driver File Name: 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: 
Quote
Driver File Name: 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 Shelly: Driver shows (Unbound) In Name and

      Problem After adding Shelly Driver, it shows "(Unbound) in the name and can't be configured Solution Ensure that latest Shelly driver has been installed from Chowmain website. Licence Migration may be required Ensure that Control4 OS 3.4.3 or later ...

    • Control4: Driver Licencing: Problem Detected

      Driver diagnostics shows Driver Licencing: Problem Detected Driver Licencing is Invalid: CM: XXXXXXXX Cause This indicates the trial has expired and there is no valid licence for the driver. Solution If a driver has been purchased, it can take up to ...

    • Control4 TP-Link: Logs Show Unable to fetch device info: -1. Unable to control device

      Problem Description In some cases (in particular the KP303), it may be detected during autosetup, the KLAP device is added and the device says Connected Successfully. However, the properties say unknown, and when logs are set to print, and DEBUG ...

    • 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: Driver Anomalies: Warning

      Driver Diagnostics shows Driver Anomalies: Warning Driver Anomaly Detected. If undesired behavior is experienced, please Submit Diagnostics (located in the Actions Tab) and reach out to Chowmain Support with the Diagnostics ID and description of the ...