Edge Shelly drivers for Gen1 and Gen2 Devices

Devices & Integrations Device Ideas
, , ,
960

Update: I found a solution (or workaround) for using a Shelly 1PM Mini Gen4 in detached mode with smart bulbs in Smartthings! Here’s what I did:

  1. Create a virtual button in SmartThings Advanced and copy it’s device ID.

  2. Create a token at account.smartthings.com/tokens
    Select all permissions under “Devices”.

  3. Access the Shelly 1PM Mini Gen4 page in your browser (192.168.1.xxx) and create a script:

let ST_TOKEN = “Paste_Your_Token_Here”;
let DEVICE_ID = “Paste_Your_Virtual_Button_DeviceID_Here”;
let flip_flop = false;

print(“Listening for the switch…”);

Shelly.addEventHandler(function(event) {
if (event.component === “input:0” && typeof event.info.state !== “undefined”) {
print(“▶ CLICK DETECTED! Sending order to Smartthings…”);

flip_flop = !flip_flop;
let command_to_send = flip_flop ? “on” : “off”;

let payload = JSON.stringify({
“commands”:[{
“component”: “main”,
“capability”: “switch”,
“command”: command_to_send
}]
});

Shelly.call(
“HTTP.Request”,
{
method: “POST”,
url: “https://api.smartthings.com/v1/devices/” + DEVICE_ID + “/commands”,
headers: {
“Authorization”: "Bearer " + ST_TOKEN,
“Content-Type”: “application/json”
},
body: payload
},
function(result, error_code, error_msg) {
if (error_code === 0 && result !== null) {
if (result.code === 200) {
print("✅ SUCCESS! " + command_to_send);
} else {
print("❌ Smartthings ERROR: Code " + result.code + " → " + result.body);
}
} else {
print("❌ NETWORK ERROR: " + error_msg);
}
}
);

}
});

  1. Click on Save and Start, and then on Run on startup.

  2. Create the Routine in the SmartThings App, Ex.:

    IF: Device Status Virtual Button is On/Off (or other conditions/pre-conditions)

    THEN: Control Smart Bulbs → Toggle On/Off or set brightness/color temp

  3. And that’s it! ENJOY

Thank you all for your help (especially @TapioX and @mocelet for your quick replies).

961

Mind that won’t work tomorrow, tokens are limited to 24 hours now.

962

:man_facepalming:

Back to scratch?! Maybe use LAN Device Trigger via LAN Trigger Multi V1.0 edge driver?

963

Note this

This driver requires that a forwarding bridge server is running on the LAN. This bridge server can be obtained from this repository: GitHub - toddaustin07/edgebridge: Forwarding Bridge Server for SmartThings Edge drivers · GitHub

MQTT Broker is better solution

OAuth-In app is other solution

Here are @orangebucket instructions

If you can get OAuth working using Shelly’s script, you can you share the script with me.

964

@TAustin First of all, thank you so much for your amazing work on the SmartThings Edge drivers. Your drivers have been a lifesaver for the community!

I am reaching out because I recently purchased several new Shelly 1PM Mini Gen4 and found out matter does not expose the input state in detached mode, just the main relay button. So I’m trying to integrate them locally using your Shelly Gen 2/3 Device Driver V1.7 or the Shelly Device Driver V1.9.

I have a SmartThings Hub Aeotec Smart Home 2 v4.

My goal is to use the Shelly in “Detached” mode (with a standard physical wall switch) to trigger SmartThings routines and control my smart bulbs without cutting their physical power. However, because this is a Gen4 device, the driver doesn’t seem to recognize the hardware properly, and I can’t get the "Input” state (the detached switch) to be exposed in the SmartThings app. Can you help me?

I extracted the device info and DM you.

Would it be possible to include support for this Gen4 model in your driver so that the detached input state gets exposed to be used as a trigger in ST routines for my smart bulbs?

Please let me know if you need me to run any specific tests, capture logs, or provide any further information. I would be more than happy to be a beta tester for this.

Thank you so much for your time and for everything you do for the ST community! :folded_hands:

965

Workaround Solution: Shelly 1PM Mini Gen4 with Smart Bulbs (Bypassing 24h PAT limits & Detached Mode issues!) :grin:

Hi everyone,

I wanted to share an update and a final solution to a problem I asked about a few days ago regarding my Shelly 1PM Mini Gen4 and Smart bulbs. My goal was simple: I wanted to use my physical wall switch to control my smart bulbs via SmartThings, without ever cutting the physical power to the bulbs. Initially, I set the Shelly to “Detached” mode. Since Matter and the official Cloud integration currently hide the detached input for Gen4 devices, I tried using a Shelly script with a SmartThings Personal Access Token (PAT) to trigger a virtual switch via the API. It worked perfectly… but PATs expire after 24H! Updating the token in the script every single day was driving me crazy.

I also tried using local Edge Drivers (like TAustin’s amazing LAN triggers), but to no success, since the drivers don’t fully support the Gen4 fingerprint yet.

So, until Shelly releases a firmware update to fix this, I decided to drop the code and fix it with a simple hardware workaround (a quick DIY/bricolage fix). It took me 5 minutes, cost almost nothing, and works flawlessly. Here is how I did it:

Instead of relying on the software “Detached” mode, I bypassed the relay using a 3-way Wago connector:

Hardware:

  1. Turn off the breaker

  2. Remove the load wire (the one going up to the bulbs) from the Shelly’s O (Output) terminal.

  3. Use a Wago connector to splice 3 wires together: The main Live/Phase wire coming from the wall, the Load wire (going to the bulbs), and a small new pigtail wire, that connects into the Shelly’s L (Live) terminal to power the Shelly.

  4. Leave the Shelly’s O (Output) terminal empty.

  5. The physical switch remains wired to the SW terminal as usual.

Software:

  1. In the Shelly Web UI, set the Input Mode to Switch and the Output to Edge.

  2. Create the Routine in smartthings.

And that’s it!

(At least until we have an edge driver solution or a shelly firmware update).

I hope this helps anyone struggling with Gen4 Shellys, Matter limitations, or the 24h PAT token rules. Sometimes, a 50cent Wago connector beats weeks of coding and API debugging! :grin:

Cheers!

966

Do you still need this?

967

Hello - Sorry you didn’t get a response to your question earlier. Please let me know if you are still around and are looking for this device to be supported. It looks like this is a Gen2 device, correct? It also looks like one of the more complex ones, as it supports multiple ‘profiles’ (modes of operation). From your description, it sounds like you may be running yours in the ‘light’ profile as opposed to the other options of rgb and rgbw. Let me know…

968

Hello Patrick - Sorry for the long delay in responding. If you’re still around and needing this device supported, please let me know.

969

GEN2/3 DRIVER UPDATE NOTICE

Driver Name: Shelly Gen2/3 Device Driver V1.8

Driver ID: f3258c1d-b6e9-424d-8b3f-b1e8fe51c4ca

Date/Timestamp: 2026-04-23T21:59:45.613203436

Greetings driver users. I am pushing out a driver update for the GEN2/3 driver that includes the following updates:

  • Addition of Gen2 Shelly Plus Wall Dimmer (@Buds_Smart_Home )
  • Addition of Gen4 Shell 1PM Mini (@BFS )

You’ll note this is the first time I’ve added support for a Gen4 device. Although the more recent devices can be now be supported via the native SmartThings Matter support, some users still have unique needs that can be supported by my driver, so I’m happy to provide that. If I add any more Gen4 devices, I’ll probably start referring to this driver as the Gen2+ driver, since it is capable of supporting any Gen2-4 devices.

Thanks to @BFS and @Buds_Smart_Home for testing these updates.

One other item to be aware of: I’m now putting this driver out on my regular Shared Projects channel instead of the Test channel, which was long overdue for this driver. So if you don’t want this update for whatever reason, and you are not subscribed to my Shared Projects channel, no action is needed. But if you want to make sure you get this and all future updates, please ensure you are subscribed to my Shared Projects channel.

Let me know here if there are any problems/questions.

970

Hi @TAustin,

Thank you so much for all your hard work on this new driver version and for adding support for the Gen4 Shelly 1PM Mini!

This driver is working 100% flawlessly. The new features you implemented, especially the custom voltage reporting thresholds, the minimum voltage reporting intervals, the support for authentication password protection and the full support for detached switch inputs, massively improve the functionality of this Gen4 device in SmartThings, especially when using it with smart bulbs in ST automations.

As you mentioned, while native Matter support is okay for basic stuff, your driver gives us the advanced flexibility, local speed, and granular control that users, like me, really need. It completely solved the limitations of the official integration.

I am incredibly grateful for your time, patience, and dedication in getting this to work.

Thanks again for everything!

971

Hi @TAustin

Thank you very much for all the hard work you do for the community. I really appreciate it.

I wanted to ask if it would be possible to add one more feature. I’m currently using the driver (see attached image) for the Shelly 2PM Pro Gen 2 shutter device (I am using driver shelly gen2/3 and I also have an old devices with v1.9 driver)

The Gen2 device dont work properly on driver v1.9 so I installed gen2/3 driver

Screenshot_20260425_094700_SmartThings
Screenshot_20260425_094700_SmartThings1440×3120 135 KB

Screenshot_20260424_193414_SmartThings
Screenshot_20260424_193414_SmartThings1440×3120 133 KB

Would it be possible to update your driver so that when I add the device to Favorites, I can expand it into a large tile (as shown in the attached image)? This is something that works in the Shelly Device Driver v1.9.

20260425_094035
20260425_0940351920×1440 379 KB

Additionally, when I use the physical wall switch for the shutter, the percentage position does not update correctly to reflect the actual state. For example, if someone opens or closes the shutter manually, the percentage shown in the app is not accurate. This behavior worked correctly in the previous driver I mentioned. Is there a possible solution for this?

Thanks again for everything!

972

How did you make the tile large with the Gen1 driver? I may need to go back and look, because I don’t remember implementing anything specific for that. In fact, from what I remember (it’s been a while), large tiles have to be defined by the driver’s device profiles and presentation definitions. So it’s possible to do with some work, I’m just surprised you could do it with the Gen1 driver…

This must either be a bug in the code or for some reason the device isn’t reporting it. If you know how to use the CLI to get driver logs, we may need to do some inspection to see what is going on. Direct message me and we can pursue that if you’d want.

973

Thanks for your fast reply.

@TAustin

I sent you a private message with the details and some screenshots.

Let me know if you need something more or you have any solution.

Liran.

974

Hi @TAustin

This is the answer from Gemini to my logs:

I’m using your Shelly Gen2/3 Device Driver V1.7 with a Shelly Plus 2PM for my roller shutters.

I’ve encountered an issue where the device status in SmartThings gets stuck on “Opening” and the percentage doesn’t update when using the mechanical wall switch or when the shutter stops at a partial position.

Looking at the Edge logs, I found a specific Lua error occurring whenever the device reports a stopped state at a partial position. It seems the driver is trying to emit a state value that SmartThings doesn’t recognize (missing space or incorrect string).

Here is the relevant snippet from the log:

2026-04-25T21:13:43.585289402Z DEBUG Shelly Gen2/3 Device Driver V1.7  WS Receive TEXT frame payload:   {"src":"shellyplus2pm-c049ef8d24d0","dst":"EdgeDriver","method":"NotifyStatus","params":{"ts":1777151623.57,"cover:0":{"apower":0,"current":0,"current_pos":13,"move_started_at":null,"move_timeout":null,"pf":0,"source":"timeout","state":"stopped","target_pos":null}}}

2026-04-25T21:13:43.592168319Z WARN Shelly Gen2/3 Device Driver V1.7  unnamed handler on driver thread encountered error: [string "st/capabilities/aware.lua"]:242: Invalid value for Window Shade.windowShade value: {value="partiallyopen"} error: Given partiallyopen for OpenableState. Incorrect string given

The issue: The driver receives the correct position (13%) via Websockets, but when it attempts to emit the windowShade event, it uses the string "partiallyopen". SmartThings throws an error because it expects "partially open" (with a space) or a valid capability state, causing the update to fail and the UI to remain stuck on “Opening”.

Thanks for your great work on these drivers!

975

AI can be pretty useful when it’s not hallucinating!

That’s an easy fix, and I’ve already applied it. However, make sure you subscribe to my shared projects channel to make sure you are getting the up-to-date driver, which is now version 1.8, with driver date/time stamp of 2026-04-25T21:47:05.467028158.

I will respond to your direct messages.

976

@TAustin

Thank you very much for your quick response.
I’ve subscribed to your new channel.
I replaced the drivers, and now I can see the percentage both when opening the shutter from the physical switch, and I can also expand the button in the SmartThings app like before.
Thank you, thank you, thank you!

One more question: does your driver also work with Gen 4 shutter modules? I have two of these that I’ll need to connect soon.

977

Hi @TAustin

Thanks for the amazing work, is it possible to add support for the shelly1 mini gen4 device?

Sadly the current version doesn’t let me add my shelly mini with scan nearby, to be precise it founds it but it uses the smartthings default matter driver, and I can’t change them in the device setting(no driver found).

Same situation as @BFS shelly mini to smart bulbs so I need the detached mode set in the shelly settings and control over the logical relay in smarthings, atm my only workaround is use the shelly in edge mode with an auto-on timer set to 400ms(so the smart bulb condenser still hasn’t discharged), the routine in smarthings comprehend a virtual switch tied to the status change of the shelly.

Thanks in advance

978

I’m not sure what devices you are referring to; can you provide the model name?

There’s only 2 Gen4 device I’ve added so far, since it seems most people would be using the matter support for the newer devices. If there is some feature or field that you can’t get using the matter interface, I could consider adding it to my driver.

979

Yes and done: it’s in the latest driver update:

Shelly Gen2/3 Device Driver V1.8

Driver ID: f3258c1d-b6e9-424d-8b3f-b1e8fe51c4ca

Version: 2026-04-28T21:53:38.854905037

Be sure you are subscribed to my Shared Projects channel.