[APP][Pro&Cloud] Shelly


{"type":"SHSW-25","mac":"ECFABCC4C76B","auth":true,"fw":"20220209-093016/v1.11.8-g8c7bb8d","discoverable":true,"num_outputs":2, "num_meters":2, "num_rollers":1}
1 Like

Hi there,

Often the app gets pauzed by homey due to high memory usage.

Is this fixable?


You are the first to report this. The log does not contain any information. I did receive a crash report earlier today which might be related if it came from your Homey. It’s indicating networking issues which you would have to solve yourself. Are the devices below yours?

[err] 2022-07-06 12:30:43 [ManagerDrivers] [Driver:shellyi3] [Device:9f642d93-9281-49cc-a5e1-63d4b0e18323] FetchError: request to failed, reason: connect ECONNREFUSED
[err] 2022-07-06 12:30:46 [ManagerDrivers] [Driver:shelly1] [Device:a52b77ed-2d2d-4328-924d-5870a0c78229] FetchError: request to failed, reason: connect EHOSTUNREACH
[err] 2022-07-06 12:30:46 [ManagerDrivers] [Driver:shelly25] [Device:6daf1be5-317c-4cc2-9dac-9ce822b03aba] FetchError: request to failed, reason: connect EHOSTUNREACH
[err] 2022-07-06 12:30:46 [ManagerDrivers] [Driver:shellyi3] [Device:27b62dd5-1fe9-4901-967c-e52de6b749ac] FetchError: request to failed, reason: connect EHOSTUNREACH
[err] 2022-07-06 12:30:46 [ManagerDrivers] [Driver:shellyi3] [Device:6a10e692-426e-4ab4-960a-305afd323bfb] FetchError: request to failed, reason: connect EHOSTUNREACH
Error: bind EADDRINUSE
    at node:dgram:351:20
    at /opt/homey-client/system/manager/ManagerApps/AppProcess/bootstrap.js:1:1796
    at IPCSocket._handleMessage (/opt/homey-client/system/lib/IPCSocket.js:1:800)
    at process.emit (node:events:526:28)
    at emit (node:internal/child_process:938:14)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)
Emitted 'error' event on CoAPServer instance at:
    at Socket. (/node_modules/coap/dist/lib/server.js:277:18)
    at Socket.emit (node:events:538:35)
    at node:dgram:353:14
    at /opt/homey-client/system/manager/ManagerApps/AppProcess/bootstrap.js:1:1796
    [... lines matching original stack trace ...]
    at processTicksAndRejections (node:internal/process/task_queues:84:21) {
  errno: -98,
  code: 'EADDRINUSE',
  syscall: 'bind',
  address: '',
  port: 5683

No that’s not mine unfortunatly. But thanks for looking into it! I guess ill have to contact athoms for this than

Good luck with that, they will say the developer of the app will need to fix it.

There is a big update underway, perhaps that might make a difference. How many Shelly devices do you have connected?

v3.10.1 - test

  • Important message: this release contains some non-breaking but fundamental changes. All previous device drivers have been deprecated for both Homey Pro and Homey Cloud. They have been replaced by a single unified driver for all Shelly devices. Your already paired devices will continu to function but new devices should be paired with this new driver. This will make adding future devices to the ever growing collection of Shelly devices a lot easier.

  • Add total energy consumption for Shelly 3EM for Homey Pro and Cloud

  • Add total power consumption for Shelly RGBW2 for Homey Pro and Cloud

  • Fix for Shelly TRV target temperature being out of bounds and causing an app crash

  • Various minor code improvements for both Homey Pro and Cloud

I’m sure the deprecation of currently used device drivers will raise concerns, especially since user will see a message about this in the Homey app. No worries, your devices will continu to function normally within Homey until I decide to fully remove the driver. For a lot of long lived drivers I will probably not remove them at all and no action is required, just ignore the message. I do intend to remove the more recently added drivers for all Plus/Pro devices at some point to reduce the apps footprint. With over 75+ drivers the Shelly app has grown huge. It’s hard to maintain and I’m worried this is starting to impact performance. If you have paired any Plus/Pro devices with Homey you are encouraged to re-pair them using the new driver. I will probably remove the current drivers after the summer to give users some time to fix their flows.

Looking for testers

Version 3.10.1 has now been pushed to the test channel. I’m looking for users that are willing to test this version to make sure it does not impact any currently paired devices. You can install the test version through the link below and validate that your devices are still working and switch back to the current app store version (3.9.12) without any issues. All I’m asking is a little of your free time to make sure stuff doesnt break when I push this version to the app store.

1 Like

Not able to add a Shelly Button 1, as every time it asks for the icon file or use default, it hangs.
Unable to upload a file, or use default.

Homey 2016 running 8.02 firmware.


Read the instructions from the first post. The answer is in there.

There is no option given on the app to allow me to sync with the cloud and update the latest firmware.
I have done this before with two other shelly products.
Only the I/O Option dropdown works, but nothing else.
I have now been through the exercise four times, reseting each time, but same result.
Can not log on the the my.shelly.cloud either, even though i know the login data is 100% correct.
Is there a problem with the cloud ?

You are looking in the official smartphone app from Shelly right, under the device settings?

The same one I used to register and update the two other shelly devices last week.


Finally got it to update firmware, but through the desktop web app, and only on edge.
Finally added to Homey, but no functions available other than battery voltage actions.

Read the instructions from the first post. There is a generic trigger action card available under the app instead of the device.


Hi @Phuturist,

Just installed the test version of the app.
All my 14 Shelly Devices keep working.
I have Dimmer2, Plugs, 1L and 1 Shelly devices installed in different setups.
Some control the lights directly (dumb bulbs) and some control Hue Bulbs.

I will keep the test version installed.
If you want me to test something specific, let me know!


Looks good for my shellies, I only dislike the warning, understand why, but …

DIagnostic report: 00b7752d-9f22-468d-8b8c-540c3c9a1028

When I go to my Shelly I3 device in homey app popup shows up which says that This type of device might not be supported in the future.

Is support going to be removed for these?

1 Like

See [APP][Pro&Cloud] Shelly - #2883 by Phuturist



I am a brand new user and I just bought my first Shelly 1. After reading the instructions, I followed the steps closely to add the device to my home network and the app, but it’s not sccessful.

Now it is located under “hidden devices” as Offline / Pending connection.

This device is brand new from the store and has never been connected to a network before.

This happened the first time also so I have reset the device (5 times on/off sw) once before.

Now I need some help because I just can’t get any further.

It’s a 2.4 GHz network, I find the device and connect to it through the app. Then the AP network shows up on my wifi and I connect to that also. That is basically where I am at now.


Hi Phuturist, I’m happy to do some tests with my Shelly Plus 1 PM’s. I’m planning to buy a few more Shelly devices… I like your app and support you provide :+1:

One question. On my Homey Pro I don’t see the power changing. It shows the value of 3 days ago. The Shelly app does show the correct value…