Control4 Shelly: Module Reboots Continuously In a Loop

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   
  1. The Display Device Directory Action in Shelly Agent can be used to help identify if 2 drivers have the same ID
  2. 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
  3. Check IP addresses in drivers are unique
  4. Ensure there are no IP conflicts on the network 
  5. We recommend using static IP's for modules and/or Cloud+LAN discovery