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 with the same IP in the project. When each driver connect, it sees that the configuration is set differently to what it expects, and changes the configuration. Once the driver reboots however and the other driver connects, the process will be repeated by the other driver
- The Display Device Directory Action in Shelly Agent can be used to help identify if 2 drivers have the same ID
- Ensure that the module ID is different for all drivers when using Shelly Agent. If duplicate module ID's are used in different drivers, this causes the IP addresses to duplicate
- Check IP addresses in drivers are unique
- Ensure there are no IP conflicts on the network
- We recommend using static IP's for modules and/or Cloud+LAN discovery
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: Shelly Best Practices
Security and Authentication We strongly recommend against combining customer systems into the same Shelly Cloud email login account, particularly for Control4 setups using Shelly Cloud Authentication. This may affect security of all systems, and if ...
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: 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 ...
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 ...