Shelly Pro Device Configuration

SHELLY DEVICES CONFIGURATION

Setup your Shelly devices as instructed by the Shelly User Manual.  Pay attention as each device is configured differently. The driver uses UDP multicasting.  Make sure your router / switches support it.  If you have VLANS, make sure VLANS can pass UDP and multicasting to different segments.

For Lighting Devices:

• For Gen-1 devices Make sure that each lighting device has CoIot enabled and set to “mcast”.  Gen-2 Devices do not have this option.
• The Driver will auto provision Gen2 devices.  If they are not discovered or not responding correctly, click on Provision UDP.

For Sensors Gen 1 Devices

• All other devices including sensors please following the following instructions: Manually enter a multicast address with a port. 
  • Go to settings under Internet / Security à Advanced – Developer Settings
  • Enable CoIot
  • Set the Remote address to 224.0.1.187:5683
  • Hit Save, then Reboot the Device —> Settings —> Reboot (You must reboot the for changes to take effect)

• To Enable CoIot, we recommend using the web interface for each device rather than use the Shelly mobile app.  As of the release date of this driver, the manufacturer recommends using the web interface of the app to configure the devices rather than the mobile application.  The mobile application is undergoing a revamp according the manufacturer.
• To use the web interface of the device.
  • If the device has not been setup using the Shelly app, after powering the device, go to your Wi-Fi setup and connect directly to the Shelly Device.  Usually, it will show up as a Wi-Fi AP node with the name of Shellyxxx-xxxx.
  • Once connected, using a web browser navigate to http://192.168.33.1
  • Note:  If the device is battery powered such as most sensors, you have three minutes from when the device is put into AP mode to complete the task.  You can always put the sensor back in online mode by triggering AP mode for another three minutes.  To trigger the device, see its user manual as each device has a different way of triggering.

Special Note on Sensor Reporting

The Driver has a new feature that creates a listen socket to the multicast address and to the controller’s own IP address simultaneously.  This vastly improves sensor reliability.  It is recommended that if a sensor is not reporting reliably that you switch its CoIot address to that of the Elan Controller.  The one caveat is if you have other devices listening for Shelly multicast packets, they will not receive it as packets will only be point to point from the Shelly device to the Elan controller.

If some sensors are not reporting after going through the common issues, follow these steps:

Change the CoIot Remote address to the Elan Controller’s IP address with :5683 at the end.  Example:  192.168.0.5:5683.  Hit Save, the Reboot the sensor.

For Sensors Gen 2 Devices

For Gen2 Devices, enable RPC over UDP.  Enter the Destination Address as 224.0.1.187:5683 and the Listening Port as 5683.