Control Shelly devices with Homey
App Store Page: Shelly App for Homey | Homey
Changelog: Shelly App for Homey | Homey
Description
This Homey app allows you to control a wide variety of Shelly devices.
Pairing instructions
View the pairing instructions
- Add your Shelly device to the official Shelly smartphone app;
- Update the Shelly to the latest device firmware version by first connecting it to the cloud and then checking for a new firmware version;
- 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.
Generic action event trigger card
Read how to use the generic action event trigger card for devices with inputs.
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 paired 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.
Known issues
- There is a memory leak somewhere in the app that affects a small amount of users. The memory leak results in the app crashing after some time of use (from hours till days). I have been unable to identify the source. Some users have been able to fix their memory by re-pairing their devices and/or checking all their Shelly devices for networking errors.
Troubleshooting your setup
Users often blame the app when thing are not working as expected but most of the time the issue is related to their own actions and/or configuration. These steps help you identify the most common user errors.
1. Timeouts during pairing for gen1 devices on the icon select screen
If you receive a timeout during pairing for gen1 devices, you should have read and followed the pairing instructions. Make sure you update the firmware of your device. You might need to connect your Shelly to the cloud before being able to see the latest available update.
2. Delayed status updates for gen1 devices
If you experience delayed devices status updates for gen1 devices (or no updates / events for battery powered devices at all) there could be multiple causes but all of them are related to the network traffic used for communicating status updates from Shelly devices to Homey. Shelly Gen 1 devices use a networking technique called CoAP. During pairing with Homey it tries to update the Shelly device where it enables CoAP and configures the IP address of Homey to allow communcation. Things to check:
- Make sure CoAP is (still) configured correctly. You can check this through the webinterface of the Shelly device by accessing it over itâs IP address (http://yourshellyiphere) and look under "Internet & Security > Advanced > Enable CoIoT. Make sure it is enabled with the correct IP address of Homey and port 5683.
- Make sure you do not skip a lot of major app version updates (by disabled auto updates). You could break the upgrade path and therefor break CoAP traffic. You will need to re-pair your devices to fix this issue.
- Make sure you have not accidently disabled CoAP communication from the app settings. This is an advanced setting for experienced users only. The tickbox under the app settings should be disabled.
3. No status updates or device is unreachable errors (EHOSTUNREACH) for gen1 devices
If you experience no status updates and devices appearing as offline in Homey while they are accessible through the native Shelly app or the webinterface there are issues with the network traffic between Homey and the Shelly devices. There are various things to check but in the end it could also be Homeyâs own networking stack which has proven to be unstable for some users.
- Make sure Homey and your Shelly device are on the same local network (LAN) or any VLANâs are configured correctly. Using VLANâs could block the network traffic between devices and Homey.
- Make sure your network configuration allows unicast broadcasts which is needed for CoAP traffic. Default network configurations should allow this. Older Shelly firmare versions (< 1.10.x) only allowed multicast broadcast which could give issues on even default configuration but if you followed the previous instructions you have upgraded the firmware of your Shelly device already.
- 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/).
- If you followed all previous steps but still experience delays or no communication check the error message under the device. If itâs something like
EHOSTUNREACHordevice not reachableHomey still cant reach your device. Make sure your WiFi signal of both Homey and your Shellies is stable. Things to check is that your WiFi channel is not set to auto but to a specific channel, for instance 1,6 or 11. You can try and test the network traffic between Homey and your Shelly device with the following flow where you replace the IP address of your Shelly device in the condition card. Devices being unreachable is often a temporary state but if this flow fails consistantly you are 100% sure there are still networking issues. - If none of the above steps solved your issues and your WiFi is stable chances are itâs Homeyâs own network stack which has proven to be unstable for some users. Sometimes this can be fixed by just restarting Homey. If the issue persists or comes back after some time it could be you are out of options. This especially can be the case for users 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 diagnostic 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 diagnostic 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 firmware version, app version, Homey version and Shelly devices you have connected.
4. Delayed status updates for Plus/Pro devices
If you experience delayed devices status updates for Plus/Pro devices (or no updates / events for battery powered devices at all) itâs most likely caused by incorrect configuration of the outbound websocket. Homey opens a websocket server and during pairing configures the Shelly device to report status updates to this websocket server. Sometimes this configuration fails or is altered afterwards causing status updates to fallback on slower polling of the devices. Plus/Pro devices. To fix this:
- Open the webinterface of your Shelly by entering itâs IP address in the browser.
- Go to the
Networkstab andOutbound socketoption. - Make sure itâs enabled and pointing to your Homey IP with port 6113. The address should look similar to
ws://192.168.0.2:6113/but with the IP address of your Homey. For SSL there should be an asteriks (*). - If this configuration is missing either re-pair the device or add it manually here.
5. No status updates or device is unreachable errors (EHOSTUNREACH) for Plus/Pro devices
If you experience no status updates and devices appearing as offline in Homey while they are accessible through the native Shelly app or the webinterface there are issues with the network traffic between Homey and the Shelly devices. There are various things to check but in the end it could also be Homeyâs own networking stack which has proven to be unstable for some users.
- Make sure Homey and your Shelly device are on the same local network (LAN) or any VLANâs are configured correctly. Using VLANâs could block the network traffic between devices and Homey.
- 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/).
- If you followed all previous steps but still experience delays or no communication check the error message under the device. If itâs something like
EHOSTUNREACHordevice not reachableHomey still cant reach your device. Make sure your WiFi signal of both Homey and your Shellies is stable. Things to check is that your WiFi channel is not set to auto but to a specific channel, for instance 1,6 or 11. You can try and test the network traffic between Homey and your Shelly device with the following flow where you replace the IP address of your Shelly device in the condition card. Devices being unreachable is often a temporary state but if this flow fails consistantly you are 100% sure there are still networking issues. - If none of the above steps solved your issues and your WiFi is stable chances are itâs Homeyâs own network stack which has proven to be unstable for some users. Sometimes this can be fixed by just restarting Homey. If the issue persists or comes back after some time it could be you are out of options. This especially can be the case for users 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 diagnostic 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 diagnostic 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 firmware version, app version, Homey version and Shelly devices you have connected.
6. Flow not working but direct control from Homey works fine
If you experience flows not working as expected. Solution is most likely to update your flows as there have been breaking changes in the way the app works which requires you to update your flowcards. This is announced in the changelog but you might have missed that.
