Control4 Shelly Suite: Shelly Incorrectly Shows All Customers Devices
For Shelly Agent to differentiate different systems correctly, Customers must use a different Shelly cloud email login for Shelly Cloud. If customers have multiple Control4 systems, it is also generally recommended to have a different account login for each installation to ensure only devices which exist in the installation are shown to the user.
If Customers have been incorrectly added to the same account, it is recommended to either split the devices into a separate account or rely on Local discovery only (keep in mind that there may be limitations to local discovery which affect reliability)

Using Cloud authentication in Shelly Agent for accounts which are shared between multiple customers may enable technical customers who have obtained the API key incorrectly, to control other customers devices.
Related Articles
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: Obtaining An API Key
Benefits of Shelly Cloud To facilitate Setup of Shelly, it is recommended to use our Shelly Agent and setup Shelly Cloud. This provides fast setup of devices, IP self-healing and better handling of sleepy devices. Chowmain's Shelly Driver suite will ...
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: 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 ...