Shelly Pro Known Issues

COMMON ISSUES

Wait 15 seconds after Apply

• Driver not Activated. 
  • Wait 15 seconds after Apply
• Driver not discovering devices.
  • Try discovery again.  Make sure broadcasting / Multicast is enabled on the network
• Driver not controlling light but it’s working from Shelly.
  • Make sure the IP address didn’t change. Assign DHCP reservations for the devices.
• Scenes are slow to execute
  • If a device, most likely, a light bulb is a part of a scene and the device is offline, there will be a 3 second delay for every device that’s in the scene that’s offline.  This is normal.
• Shelly Sensors are not discovered.
  • Set the driver to 60 Minutes, Hit Apply, Hit Install. Trigger Sensors. 
• Shelly Button Not Triggering
  • Switch to TCP mode
  • Recycle TCP Socket
  • Connect the Button to a constant Power Source while configuring
• Shelly Motion Sensor not triggering or discovering.
  • Shake the Shelly Motion instead of just waving in front of the sensor.
• Shelly sensor is not reporting. 
  • Make sure the sensor is sending information.  Manually trigger it (each device is triggered differently, follow the manufacturer user guide), look at the last reported field and see if the values have changed.  If this is the case, it means the sensor itself is not waking up and reporting, troubleshoot it according to the manufacturer user guide.
  • Check that the sensor didn’t change IP address.  This can happen even if it’s assigned a static IP address in its Settings Page.  The best practice is to use router DHCP reservation.

KNOW ISSUES

• The lighting driver will not display the proper name of the Shelly device but instead it will show the device type and it’s MAC address.  To work around this, rename the device in the driver after discovery is finished.
• Gen2 Devices are not discovered.  Reboot all Gen2 devices.  Rediscover