App Store Page: https://homey.app/a/cloud.shelly/
This Homey app allows you to control Shelly devices over WiFi.
I enjoy creating apps for Homey and try to support them as best as I can. But if you enjoy using my apps a donation in return for the time I put into this is much appreciated.
First add your device to the official Shelly smartphone app, then pair your Shelly device in Homey. The Shelly app for Homey uses mDNS discovery for finding your Shelly device(s) on your network. If you are unable to find your Shelly device using discovery even though it’s connected to your network you can try to manually pair it using it’s IP address. If you have configured a username and password you are asked to enter these as well during pairing. After confirmation your Shelly device is paired and you are good to go.
The update from version 1.x to 3.x is a major update. The app has pretty much been rewritten and includes a lot of breaking changes. This paragraph will give some pointers to help you update.
- Start with updating the firmware on your Shelly devices as well. Some problems are related to outdated firmware versions.
- First review the entire v3.x changelog to see what changed and what you might need to fix.
- Fix any broken flows, some flow cards have changed or been replaced.
- If you are using the action event URL’s, try triggering them. The action event URL which needed to be manually set previously have been replaced by direct messages from Shelly to Homey. By triggering an action event the v3.x version of my app will remove the deprecated action event URL’s from your Shelly devices.
- If you have issues receiving device status updates (after the initial update) please review the troubleshooting section below.
A lot of Shelly devices are capable of notifying Homey when a specific action has taken place like a short- or longpress of a switch. If you have a supported device and you want to use this functionality you can find the “Action Event” trigger card under the app flow cards and not under any specific Shelly device (so search for Shelly when adding the card in the flow). When you added the card to a flow you can select which device and what action should trigger your flow.
- Some users experience flows not working as expected. Solution is most likely to update your flows as recently there have been some breaking changes which requires you to update your flowcards.
- Some networks are misconfigured for using multicast CoAP protocol which is used for device updates on lower firmware versions. As a result the status of Shelly devices are not updated frequently even though you are able to control devices through Homey (which uses HTTP). To solve this update the firmware of your Shelly devices to at least version 1.10.x which allows for unicast CoAP communication which will work even on networks that do not support multicast CoAP communication.
- Some users experience networking issues where devices do not respond to commands and/or show as unreachable devices (indicated by a red triangle). See the troubleshooting network communication guide below.
Some users experience networking issues where devices are unreachable or commands give timeouts. This can be caused by many things, this troubleshooting guide is the first thing to try.
- Make sure the firmware of your Shelly device is up to date.
- Make sure you assign static IP addresses for your Shelly devices in your router. Check if the IP address of your Shelly still corresponds with the IP address under the device settings in Homey. Also make sure you can access the webinterface of your Shelly devices under that IP address (http://yourshellyip/).
- Make sure there is nothing blocking the network traffic between Homey and your Shelly device, like a firewall or seperated VLAN. You could test this by using the “send a webrequest” logica action card within a flow and try to request the status page of your Shelly at http://yourshellyip/status.
- Make sure your WiFi signal of both Homey and your Shellies is stable. Check for instance your WiFi network channel is not set to auto but set to a specific channel, for instance 1,6 or 11.
- If you have done all of the above and your issue persists it could be that the network stack of Homey itself is not working properly. Try rebooting Homey. If the problem persists or comes back after some time it could there is not much else to do. This especially can be the case for user that have a lot of WiFi devices connected to Homey. You could look into reducing the number of devices to see if that helps. Feel free to send me a crash report from the app settings. Based on this I can at least confirm it’s indeed network issues. Do this by restarting the app, wait until the devices show as unreachable in Homey and send the crash report from the device settings. Afterwards post the crash report ID in the support topic here together with extra information about your issue, like the router you are using and how Homey and the Shellies are connected to it.
Allterco Robotics, the company behind the Shelly devices, is releasing new products very often. If you want a device added to this app which is currently missing you have three options:
- If you own the device you can send me the output of http://yourshellyip/status and http://yourshellyip/settings. This tells me the capabilities and the way the API is implemented for that device.
- Wait for the API documentation to be updated. Based on the documentation I can add the device. Allterco Robotics is slow in updating their API documentation however.
- Donate me money so I can buy the device or send me the device itself so I can add support using the actual device.