I’ve developed source code that works for the color modes of the Shelly RGBW2 controller and probably the Shelly RGBW PM controller. I will make the source code available in the next few weeks along with instructions on how to install it on a Smartthings hub. It’s free to modify if it doesn’t meet your needs. I’m new to the Smartthings Community, so I hope my post is okay.
Hi @TAustin,
I have a Shelly Pro 3EM and I’d like to request its inclusion in your Edge Driver, as the current version for the classic 3EM doesn’t seem to support this Gen2 model.
Here is the JSON from my device’s GetConfig to help you with the integration:
{“ble”:{“enable”:false,“rpc”:{“enable”:true}},“bthome”:{},“cloud”:{“enable”:true,“server”:“shelly-69-eu.shelly.cloud:6022/jrpc”},“em:0”:{“id”:0,“name”:null,“blink_mode_selector”:“active_energy”,“phase_selector”:“all”,“monitor_phase_sequence”:false,“ct_type”:“120A”,“reverse”:{}},“emdata:0”:{},“eth”:{“enable”:true,“server_mode”:false,“ipv4mode”:“dhcp”,“ip”:null,“netmask”:null,“gw”:null,“nameserver”:null},“modbus”:{“enable”:true},“mqtt”:{“enable”:false,“server”:null,“client_id”:“shellypro3em-c8f09e82fc74”,“user”:null,“ssl_ca”:null,“topic_prefix”:“shellypro3em-c8f09e82fc74”,“rpc_ntf”:true,“status_ntf”:false,“use_client_cert”:false,“enable_rpc”:true,“enable_control”:true},“sys”:{“device”:{“name”:null,“mac”:“C8F09E82FC74”,“fw_id”:“20250924-062749/1.7.1-gd336f31”,“discoverable”:true,“eco_mode”:true,“profile”:“triphase”,“addon_type”:null,“sys_btn_toggle”:true},“location”:{“tz”:“America/Sao_Paulo”,“lat”:-,“lon”:-},“debug”:{“level”:2,“file_level”:null,“mqtt”:{“enable”:false},“websocket”:{“enable”:false},“udp”:{“addr”:null}},“ui_data”:{},“rpc_udp”:{“dst_addr”:null,“listen_port”:null},“sntp”:{“server”:“time.cloudflare.com”},“cfg_rev”:43},“temperature:0”:{“id”:0, “name”:null, “report_thr_C”: 5.0, “offset_C”: 0.0},“wifi”:{“ap”:{“ssid”:“ShellyPro3EM-C8F09E82FC74”,“is_open”:true, “enable”:false, “range_extender”: {“enable”:false}},“sta”:{“ssid”:“casainteligente”,“is_open”:true, “enable”:false, “ipv4mode”:“dhcp”,“ip”:null,“netmask”:null,“gw”:null,“nameserver”:null},“sta1”:{“ssid”:null,“is_open”:true, “enable”:false, “ipv4mode”:“dhcp”,“ip”:null,“netmask”:null,“gw”:null,“nameserver”:null},“roam”:{“rssi_thr”:-80,“interval”:60}},“ws”:{“enable”:false,“server”:null,“ssl_ca”:“ca.pem”}}
Thank you for your amazing work on these drivers!
witam
Korzystam z twojego sterownika dla liczników shelly PM mini (te białe małe kosteczki) zauważyłem że sterownik czasami rozłącza się z urządzeniem i potem go już nie odnajduje, jest problem z resetowaniem licznika całkowitego kwh z poziomu procedury nie działa trzeba to robić zapytaniem get https. Chciałbym żebyś ogarnął osobny sterownik taki naprawdę ekstra do tych małych białych kostek bo raczej nie doczekamy się na matter do nich. mnie osobiście wkurza jak dodaje licznik a tu mi wskakuje milion shelly które mam podłączone po mater.
???
Coincidence with another action, like re-adding the device or finally installing the correct driver…
I’ve run into a specific hurdle regarding discovery and the ‘Shelly Device Creator’ tool,
My Setup:
- Hub: SmartThings v2 Hub.
- Device: Shelly Plus Wall Dimmer (functioning perfectly in the Shelly App).
- Driver: Shelly Gen2/3 Device Driver V1.7.
The Situation: I successfully installed the V1.7 driver, but ‘Scan Nearby’ fails to find the dimmer. I noticed the ‘Shelly Device Creator’ tile only appeared after I installed the Shelly Device Driver V1.9 (Gen 1). However, that Creator tool only seems to list Gen 1 devices (like the Dimmer 2), and attempting to swap that Creator tile’s driver over to V1.7 didn’t unlock any Gen 2 options.
My Questions for the Experts:
- Is the Shelly Plus Wall Dimmer intended to be found via Auto-Discovery only in the V1.7 driver?
- Since manual creation via a ‘Creator’ tile seems to be legacy for Gen 1, what are the best practices if ‘Scan Nearby’ fails?
- Does the Plus Wall Dimmer require a specific Outbound WebSocket setting (e.g.,
ws://[Hub_IP]:8081) to ‘force’ discovery, or should mDNS alone be sufficient? - I’d prefer to bypass the Shelly Cloud link entirely. If I get the Edge driver working, can I safely delete the cloud integration to keep things 100% local? Any advice appreciated.
I am using this driver for the Shelly 3EM energy monitor and although it works quite well, it would be great if you could include the below with the driver to enhance its functionallity
-
Enable the 3EM so that it is included in the Smartthings Energy Monitor.
-
Change the icon to be the standard smartthings energy meter icon (lighting bolt) rather than the switch icon or have the ability to choose the icon.
-
Ability to hide a specific power meter within the app. For example, I only have 2 of the clamps installed so it would be great if you could hide the 3rd one for within the device view app.
-
Ability to change the names of the power meter. At the moment they are only labelled as Main, Meter 1, 2, 3 etc. however it would be good to be able to label these as Consumption (Main), Import/Export (Meter 2) Generation (Meter 3)
-
Lastly, it would be good to have a graph for the energy meter and all other data points.
Most features are not possible due to SmartThings limitations, a driver can only do so much.
For instance, to appear in SmartThings Energy is a business decision of ST, typically based on some partnership with the vendor.
Component labels can’t be edited by the user. That’s been an issue with smart buttons forever because you see Button 5 and can’t change it to a meaningful name.
Hiding components is a pain, that’s also something that the SmartThings app should handle, not a driver.
Graphs depend on if SmartThings decided to add graphs to a capability, some have, some do not. Some had graphs like battery level and then they were removed.
Can you share a picture of this device’s Detail View.
Hi, do you mean the app screen pics?
TapioX <notifications@smartthings.discoursemail.com> escreveu (segunda, 9/02/2026 à(s) 15:50):
Hi
Yes .I mean the image that opens when someone presses the device in ST App.
TapioX <notifications@smartthings.discoursemail.com> escreveu (segunda, 9/02/2026 à(s) 16:32):
Thanks @Bruno_Almeida
The Shelly Add-On is connected to several 18B20 sensors.
The driver apparently supports at least 3 sensors (or 5 sensors).
Hello everyone.
I want to control a Shelly Plus RGBW PM to dim four lights using my Aeotec Hub v3 with SmartThings. Ideally, without using a cloud service.
I assume I need a driver for this, but this Shelly isn’t listed in either the Gen1 or Gen2 driver lists. Am I looking for the wrong driver, or which one should I choose?
I’ve already tried several, and SmartThings recognizes at least one device when I use the Shelly Device Driver V1.9. However, it doesn’t recognize the correct port, so I can’t turn any of the Plus RGBW PM’s channels on/off or dim them.
Do you have any suggestions?
Thank you in advance.
Best regards, Zwen
Hello everyone! Thanks for the excellent work and shares! It’s been super useful! I need help, I recently bought 2 Shelly 1PM Mini Gen4 and I’m having a hard time using them with SmartThings, either via Matter or via shelly cloud. They are connected to wall switches that control smart bulbs (Ikea kajplats). The bulbs should always remain with power, and for that I use Shelly in detached mode. So when I toggle my wall switch, the Shelly detects the change of input (physical input) but does not cut the power to the bulbs. The plan was to use that input state change in an automation in smartthings to turn on/off the smart bulbs and control the intensity and temperature of the lights according to the time of day they are switched on. But my plan didn’t work, because the state of the input is not exposed in SmartThings, either via shelly cloud or via Matter, it only exposes the main power (relay) button, and that’s no good for smart bulbs. I tried the @mocelet Matter Playground and @TAustin Edge drivers Gen2/3 v1.7 and even the v1.9, but I couldn’t get it to work. I managed to create a Shelly Relay 1 (with v1.9) that exposes the input state, but I couldn’t “link it” to my real shelly (when inserting the correct IP) or didn’t know how to do it. @TAustin do you think it’s possible to add support for these new 1PM Mini Gen4 and expose the input state? 
Does anyone have any ideias how to do this automation work? Thank you once again.
Use MQTT Devices driver
Thank you so much @TapioX
But I am very new to this. But I am very new to this. I confess I don’t know how to do that. But I want to learn. Can you help me? I intall the MQTT Devices v1.9 driver? And then add a new device from search nearby devices. And then select switch? Do I have to add 2 switch devices for each Shelly I have? Can you guide what to do? Thanks
@TAustin has made excellent instructions
GitHub - toddaustin07/MQTTDevices: SmartThings driver for creating MQTT-connected devices · GitHub
Hi everyone, so I reached out to Shelly Support team, and they were great. Here’s there answer:
“Thank you for the detailed explanation!
This is a known limitation at the moment. The input state in Detached mode is not currently exposed via Matter.
Our development team is already working on this, and support for exposing the input is planned for a future firmware update (possibly around version 1.8), but we do not have an official ETA yet.
At this time, there is unfortunately no workaround within SmartThings.
You can follow upcoming changes here:
https://shelly-api-docs.shelly.cloud/gen2/changelog/
We appreciate your feedback and apologize for the inconvenience.
Best Regards,
Shelly Support Team”
So good news! We can expect a new update to Shelly 1PM Mini Gen4 soon, to allow exposing the “input state” via matter in SmartThings.