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 Detective Suite. This issue affects any installation of the driver which was initially installed with a driver which is older than 20251027.
Shelly 20260129 and Later Module NG drivers will show "Old / Legacy" in the Event Engine Property if the patch has not been applied. If the system is not affected, Event Engine will display "New / Enhanced"
Logs will likely not not show these events / Variable changes firing (and will possibly only show the conflicting Event / Variable).
This is due to an undocumented conflict where Events and Variables may use the same ID range, causing unpredictable behavior (such as single / double click events firing on i4 during controller reboot).
Solution
We have introduced a patch in version 20251028 (which ensures the ID's do not conflict). This patch is only applied to new installs where the first version installed was 20251028 or later. It is not applied retrospectively as doing so would break all programming (including those where the issue may not be a problem in practice). Control4 also does not provide us with the capability to move the existing programming to new variable ID's.
To implement the patch:
1. Ensure your composer has the latest version. Drivers => Add
or Update Driver or Agent. This would also upgrade the driver on the
controller.. You may need to migrate the licence to Chowmain Marketplace if your existing driver in the project is 20240807 or older
2. Delete the current Module NG drivers/devices (or the affected ones) from the Control4 project
3. Re-add the affected Module NG driver. The first version installed MUST be 20251028. Whilst the Variables and bindings will look the same as previously, the ID's will not clash
Related Articles
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 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: Driver shows (Unbound) In Name and unable to configure / Not bound to Shelly Module Device
Problem After adding Shelly Driver, it shows "(Unbound) in the name and can't be configured, and there is no control. Diagnostics may display a problem that the module is unbound Solution Ensure that latest Shelly driver has been installed from ...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 Shelly: IP Address Property keeps changing to the wrong IP
Symptom After manually changing an IP address for a Module in Composer, it reverts to the wrong address after controller reboot or an unspecified amount of time Solution This problem is caused generally because Shelly Agent is not correctly ...