I repaired all my shelly’s with ai trough the MCP server app. AI can do this really fast and good! you just need to add them manualy.
Did you use matter to connect with it? Because the matter implementation is limited (which is not because of the app).
Hm yeah.. should I do LAN instead?
Yeah, that option has by far the most functionality!
Switched, works a ton better. Thanks a million for the swift response!
Is there any update on when the Shelly Plus Plug UK might be added to the supported devices for the new app?
I’ve seen there was an update to the Shelly Contol app today, but this device isn’t listed among those added yet.
shelly pro2 and shelly wave pro 1PM, when will they be supported?
See FAQ entry 2. Reading seems to be very hard for some…
Just installed https://www.shelly.com/products/shelly-em-2x-50a-clamp-1 this device. It is all working in the Shelly Control app, but not yet in the Homey Shelly Control app.
Sent E-mail to support as well. I guess it will be added somewhere down the line. Please let me know in case I am doing something wrong and this should work.
First of all, thank you so much for all the time you’ve put into developing apps. I love the Shelly support in Homey and recently started testing a migration to Control. To do this, I added 4 Shelly 2 PM Gen 4 Roll Shutters to Control. However, I quickly noticed something. The values for #position and #status aren’t being written reliably. For example, the roller shutters are at the top, but the position value for the “Right Window” roller shutter (kitchen) is still 0.95, and for the “Living Room Window” roller shutter, it’s 0.4. These were positions that were previously reached, but they’re not the current values. Is this a known bug, or is it due to my configuration or settings? I’d appreciate any help.
Name: Right Window Roller Shutter
ID: f77a2xxxxx
Class: windowcoverings
Capabilities:
Capability: windowcoverings_set
Value: 0.95
Unit : %
Last Update: Sun Oct 04 2026 18:54:16 GMT+0000 (Coordinated Universal Time)
Capability: windowcoverings_state
Value: up
Unit: -
Last Update: Mon Oct 05 2026 05:30:17 GMT+0000 (Coordinated Universal Time)
Capability: hidden.input_switch_changed
Value: null
Unit: -
Last Update: -
Please add the Pro 4PM to the new Control app.
Did you email Drenso, as I suggested earlier? That’s the quickest route to ask them to add support for your device.
Yes, I’ve already asked… but if I’m the only one who wants this implementation… I think it’ll be a long time coming.
Hi,
I’m using a Shelly Plus 0-10V Dimmer to control the 0-10V input of my mechanical ventilation (Wtw) unit — a common use case for this device. Because the Homey driver assigns device class light, the device shows up in the Lights tab and always appears as “a light that is on”, even though it’s a ventilation controller.
Shelly’s own documentation notes that the 0-10V dimmer is designed for more than lights: motors, valves and fans. The Homey Apps SDK best practices explicitly state that when a (flush) dim module has use cases other than controlling a light source, the required device class should be socket (they use the Qubino Flush Dimmer 0-10V for bathroom ventilation as the example).
Could you add a second driver (e.g. “Shelly 0-10V Dimmer (Generic) / (Fan)”) with device class socket — or even better, class fan — so users can add the device as a non-light device? Alternatively, a “What’s connected?” setting like sockets have, allowing the user to reclassify it, would solve this.
Thanks for considering!
Hi,
I have a Shelly 1 Mini Gen3 on VLAN 40 (192.168.40.251) and a Homey Pro on VLAN 10 (192.168.10.21).
The Shelly is reachable by IP address. I enabled mDNS repeating between the two VLAN interfaces on the fw and allowed UDP port 5353 from the Shelly VLAN, but Shelly Control v1.2.3 still cannot discover the device. There is no manual IP entry option.
Does device discovery work across routed VLANs, or does the app require broadcast traffic on the same subnet?
Thx!
I think it’s odd there’s no possibility to manually enter an IP address.
To check correct inter-VLAN fw rules: see if Homey can reach the Shelly by adding a Net Scan “TCP Port” device.
App:
https://community.homey.app/t/app-pro-netscan-track-devices-on-your-local-network-using-arp-and-tcp-checks/47454?u=peter_kawa
Thanks Peter!
The Net Scan is able to connet to the shelly device via its IP. But it does not recognize what this is, and the commands are not executed properly.
I’ve just add this device to a home assistant shelly integration sitting in the same vlan as the Homey. The device was added immediately: “Shelly 1 Mini Gen3 (S3SW-001X8EU)”. Maybe the Homey Shelly Control app has a bug.
This may be addressed already but…I noticed most Shelly wave devices aren’t supported in this new shelly control app. Is this a permanent situation? Am I stuck with my shelly wave devices on the old legacy app? Or are there plans to add the wave devices in future updates of the control app?
