[APP] Shelly Control - Smart home automation is that easy!

Apps
, ,
42

Hi,

I’m having an issue with the Shelly Control app on my Homey Pro.

I recently added:

  • 3 × Shelly Presence Gen4
  • 1 × Shelly Multicolor Bulb E27 Gen3

The devices are successfully added to Homey, but they become unavailable shortly after. They don’t update their status and can’t be controlled from Homey.

Some additional information:

  • Homey Pro is on my main LAN (192.168.10.x).
  • All Shelly devices are on a dedicated IoT network (192.168.68.x).
  • There are no firewall rules blocking communication between the two networks.
  • Every Shelly has a fixed DHCP reservation.
  • The devices are fully reachable from the network and work perfectly in the Shelly Smart Control app.
  • I have around 80 Shelly devices, and all the older ones continue to work correctly through the legacy Shelly app in Homey.
  • The problem only affects these newer devices added through the Shelly Control app. Also, this new ones dont seem to update automaticly websocket when homey pro 2023 changes from the ethernet to wifi

Has anyone experienced the same issue with Presence Gen4 or the Multicolor Bulb Gen3?

Is there anything I should check, such as:

  • Local vs Cloud connection mode?
  • CoIoT or WebSocket settings?
  • RPC configuration?
  • Any known compatibility issues with devices on a different subnet?
  • Any debug logs that would help identify the problem?

I’d appreciate any suggestions or troubleshooting steps.

Thank you!

43

I am having trouble understanding the input/value card for Shelly Control and looking to see if anyone can provide some guidance.

Running a retractive center toggle switch with a Dimmer Gen4 in detached mode.

Sw1 is wired to the “up” input ad Sw2 is wired to the “down” input.

When I pull up the Shelly Control input/value card in Homey, it presents me with these options for both inputs up + down:

homey shelly image
homey shelly image310×293 16.7 KB

How can input “down” have a value for firing “button up” and vice versa? What am I not understanding?

These are wired to Wiz controlled ceiling lights so I want the up input to control turning lights on and dimming up. I want the down input turning lights off and dimming down.

44

Hi there

I’m pretty much sure this is coincidence but since upgrading Shelly Control to 0.8.x, The Pill dropping DS18B20, even in the native Shelly app. Before the upgrade yesterday it was all fine 100%.

I’ll try Shelly too see what they can suggest

45

Quick update: after resetting pill and reattaching all cables it has stabilised in native Shelly app but I can’t re-add it back into Shelly Control. Just getting error “No devices found”

Cheers

46

Anybody has any ideas on how to fix this?

47

Hello

A few days ago, I had a problem where the Shelly Control app crashed. I couldn’t register any Shelly devices via the app, even after restarting it. I had to uninstall and reinstall the app. Of course, I also had to reconfigure all the devices and flows.

Another issue I’m having is that I can’t register the Shelly 1PM Gen4 as a Zigbee device.

Is anyone else experiencing these problems?

A few days ago, I contacted the Shelly helpline regarding support for the Blu Motion ZB on Homey. They told me that the Shelly App is developed by Athom, not by Shelly.

48

I have also been experiencing this problem recently. Some time ago, I connected a 1PM via Zigbee without any issues. A few days ago, I was unable to connect a second one.

49

I feel exactly the same way

50

Just a quick update re my Shelly The Pill issues. Everything resolved by itself after few days. All issues disappeared while I was trying to find the reproducible flow causing the issue in the first place. At some point I even bought another probe to see if original has broken down. But by the time the replacement probe has arrived the issue has disappeared. So I’m puzzled.

Different topic question. I have Shelly Flood Gen4 connected over the Matter which works great and much better than over the Zigbee. However for some reason I don’t get battery level over Matter. Can this be exposed in the next app update? I have other devices like IKEA thermometer connected over the matter and those do report battery levels. So it must be Shelly Control app limitation?

51

All Matter implementations are fully managed by Athom, the only thing an app can do for Matter is providing its icon and a pairing description. You will be better off by using the direct WiFi connectivity offered by the Shelly app, and not use Matter.

Not sure why the Zigbee connectivity didn’t work for you, but usually that is due to a bad network (signal strength, interference from other radios or misbehaving other devices), and sometimes Honey itself (the amount of devices simply being too large for it to be able to handle).

52

Hi @drenso,

I found a few issues with Shelly The Pill in Shelly Control 0.11.0 on my Homey Pro. I did quite a lot of testing and wanted to share my findings.

Setup:

  • Homey Pro
  • Shelly Control 0.11.0
  • Shelly The Pill
  • Firmware: 1.8.99-pillprod0 (fw_id: 20251030-160520/g0e480cb)
  • DHT22 connected
  • ABUS reed contact connected to Input 201

Problem 1 - Pairing

Most of the time I cannot add the device to Homey. Homey immediately says:

“No devices found”

The strange thing is that the Shelly logs clearly show Homey is communicating with the device. I see RPC calls like:

  • Shelly.GetDeviceInfo
  • Shelly.GetComponents

So Homey can reach the device, but still says no devices were found.

After trying many times it finally paired once, but I honestly have no idea why. I didn’t change any settings.

Problem 2 - Digital input

Temperature and humidity work correctly.

The digital input does not.

The API returns the correct state:

{
“id”: 201,
“state”: true
}

And GetComponents also shows:

  • key: input:201
  • state: true
  • type: switch

In Homey I can even see the updated name “Switch input Garage sensor”, so the configuration is being read.

However, the value always stays at:

“Last value: Unknown”

The state never changes in Homey, even though the API immediately changes between true and false when I open or close the reed contact.

Problem 3 - Device unavailable

After using “Repair” in Homey, the device became unavailable.

Restarting the Shelly Control app made it available again, and it even picked up the new input name, but the input state is still never updated.

Log message

I also often see this in the Shelly logs:

duplicate id 'Homey'

I don’t know if this is related, but I wanted to mention it.

I hope this helps. If you need more logs or if I can test anything else, I’d be happy to help.

Thanks!

53

We’ve only seen the “duplicate id ‘Homey’” notice once before, and that was on a very old Homey (2018). Which Homey are you using?

But, and I cannot stress this enough, please send your feedback to our support email address (combined with an app diagnostics report id): that way you get assigned a ticket number we can use to keep track of any issues that arise!

54

Thanks for your response. I did try to mail to the e-mail address located at the app but got an automated reply " Unfortunately, your email message to GitLab could not be processed Gitlab::email::InvalidIssueError"

I’m using the Homey Pro (Early 2019)

55

Try the e-mail linked to in the first post:

IMG_2859
IMG_28591544×982 171 KB

56

@drenso: Should I want to migrate my Shelly devices from the ‘old’ app to this new app, can the devices be (temporarily) paired with both apps in WiFi mode? Or can a device be connected to only one app at a time (in WiFi mode) and hence I need to remove it first from the old app?

57

Both support links work fine btw:

Screenshot_20260730_222936_Ecosia
Screenshot_20260730_222936_Ecosia1080×1503 132 KB

58

You most probably composed an email without a subject: Gitlab cannot handle that unfortunately.

The one in the store is obviously the same address :wink:

While technically you can add your devices using both apps, you will experience update issues as both apps try to configure a different outgoing web socket address. In other words, don’t do it, and remove them from the old app first.

But, if the old apps works for you, there is no direct reason to migrate. You can keep using the old app for the foreseeable future.

59

Thanks for clarifying. Since I have one Gen1 device (the Shelly Flood sensor, which was on sale until recently) I would need to keep using the old app anyway for that single device.

The reason I was asking about the potential move to the new app: I have several Gen4 Power Stips. I am using them in WiFi mode, as up to now the Zigbee mode was not working well and offers less capabilities.

I recently updated to the new 2.0.0. Shelly firmware. I noted that I cannot send multiple commands at the same time to the Power Strips anymore, e.g. to switch on three of the four sockets. I need to send those commands in series, otherwise only one is or none are executed.

I was wondering whether that is related to just the new firmware, or to the combination of the old Shelly app for Homey and the new firmware. Do you know whether the new Shelly app handles this better or does it control the Power Strip in the same manner as the old app?

60

It seems you assume everyone knows.

In many years of forum activity, it strikes me how few (seem to) know there’s app support links available @ app store pages in general;
Same goes for forum links (if provided for by the developer)

61

In this case you should try to migrate the powerstrip to the new app (as you have an issue); it uses a completely different method for its main communication, namely a persistent socket connection, so it can very well be the case that your issue is solved directly.

The Zigbee implementation in both app versions is however very similar. While we are aware that with firmware 2.0.0 a lot of improvements have been pushed with regards to Zigbee, I can already say that the LAN integration will most certainly remain the more complete one.