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 is installed before using Auto Setup. Early versions of Control4 may not support provisioning correctly or may fail.
- All child drivers must be bound through a Module or Module/Shelly NG driver to operate. Ensure that you have followed the correct procedure to install, as per the Chowmain Shelly installation manual and Quickstart Guide. We recommend following the Cloud Auto Setup Procedure. This will automatically set up drivers correctly
Related Articles
CONTROL4 SHELLY SUITE: Device Compatibility
The following devices have been tested with the Control4 Shelly Suite Driver. Please Note, this list is by no means comprehensive. Due to the design of Shelly Gen 2 (Plus), gen 3 and Gen 4, newly added devices which utilise the same capabilities as ...
Control4 Shelly: Module Reboots Continuously In a Loop
Symptom Module NG is continuously reconnecting, rebooting, and then repeats. This prevents the module from being controlled successfully as it is continuously rebooting Solution This is generally caused by having 2 or more Shelly Module NG drivers ...
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: Driver File Name: Problem Detected This filename for this driver has been renamed ...
CONTROL4 Shelly Suite: Input Connections And Events (Module NG)
Chowmain's Shelly driver provides a wealth of input connections and events. In most cases, most people will use the following two events: Input State X - Push / Release: Generally bound to toggle when using Button Mode. As a button link, this can ...
Control4 Shelly: Programming Changes Incorrectly. Events Fire incorrectly
Problem We have identified an issue with C4 Shelly Module NG drivers where the Events may fire incorrectly (in particular, when the controller is rebooted), or/and the programming appears to have changed to the wrong event / variable in Control4 ...