[Edge] IKEA RODRET, SOMRIG and SYMFONISK Gen 2 Button Edge Driver

While they both allow to increase / decrease brightness (I still can’t understand why that’s not a stock feature of SmartThings in 2025 :see_no_evil_monkey:), the approaches are different.

Mc driver replaces the driver of the Zigbee light so it adds more commands and features, like the β€œsteps”. Try that first, if it works with your light I’d probably choose that option. Unfortunately the driver is no longer maintained.

The virtual dimmer works with any light because it is an additional auxiliary device but it doesn’t really know the actual brightness of the light, it keeps a internal dimmer level and copies its value to the light with an automation. As long as you only use the virtual dimmer to control the brightness, it will work as expected when you β€œincrease 10%” for instance. If you change the light by other means, the levels of the dimmer and the light won’t be in sync so the β€œincrease 10%” may not match what you expect.

Thanks! The MC driver works fine for me, though it’s a bit choppy!

Thanks again for your help! :slightly_smiling_face:

Hi, I enrolled your driver. The Somrig button is discovered, but it doesn’t send any actions. I checked it with Home Assistant and Zigbee2MQTT, and it works there. Any suggestions?

If it’s already discovered (not as ZigBee Thing but as SOMRIG Button) and using my driver, try pairing it again, no need to remove it. Just put it in pairing mode, place it very close to the hub and, a second or two after, scan for devices. That works for me every time.

If that still doesn’t work then I’d be curious about the firmware version of the button and the logs of the driver when pairing.

Maintenance update.

When in Rome, do as the Romans do. SmartThings added recently a change to every zigbee driver so I’ll follow suit :slight_smile: Apparently improves latency and saves memory. I’ve not noticed anything after a day so seems good.

───────────────────────────────────────────────────
 Driver Id    ddc4c655-053a-4a52-b882-6d31e28a1ffa
 Name         Ikea Button Tweaks
 Package Key  ikea-button-tweaks
 Version      2025-07-03T13:35:47.852153462
───────────────────────────────────────────────────

───────────────────────────────────────────────────
 Driver Id    649094f7-4c84-4085-ab95-6b8c2c2be04d
 Name         Styrbar Button Tweaks
 Package Key  styrbar-button-tweaks
 Version      2025-07-03T13:36:00.824640681
───────────────────────────────────────────────────

TL;DR: health_check = false in driver template.

Yep, the health_check = false was anticipated last year, trying to know what that actually does takes a long read though. Mariano said it was useless for battery powered devices since they would deep sleep and would not reply to the pings anyway. And looks like SmartThings now believes it’s not needed either.

Got a new RODRET, made in 2025, and… it was recognized as Zigbee Thing :see_no_evil_monkey:. Turns out they have changed the fingerprint! :face_with_steam_from_nose: Now the device model is RODRET wireless dimmer instead of RODRET Dimmer.

Anyway, I’ve updated the drivers to account for that, I believe everything’s fine, the fingerprint is in many places for the extra tweaks but I’ve tested multitap, auto-repeat held and toggled-up on release.

───────────────────────────────────────────────────
 Driver Id    ddc4c655-053a-4a52-b882-6d31e28a1ffa
 Name         Ikea Button Tweaks
 Package Key  ikea-button-tweaks
 Version      2025-07-09T09:40:24.139204669
───────────────────────────────────────────────────

Fun fact, the model name printed on the back of the RODRET has always been RODRET wireless dimmer, even when it identified as RODRET Dimmer! :exploding_head: I hope renaming model identifiers (i.e. changing the fingerprint) to match the labels doesn’t become a trend :sweat_smile:

I’ve just realized the new RODRET I got recently, made in 2025, isn’t loud, in fact it feels exactly like the SOMRIG. They’re probably using the same hardware now or at least the same microswitches.

I’ve been updating the firmware of my buttons with a DIRIGERA and can confirm this driver works with the latest versions available today. So you don’t need to go hunting for buttons manufactured before certain date because it wasn’t tested with new versions :rofl: .

The warning of the first post is now just an information message. Same goes for the STYRBAR although that one has its own thread.

Edit: There’s actually a small issue with the battery reading in old TRADFRI buttons with new firmware versions (24.x) but since SmartThings can’t update the firmware I guess nobody is using them. The battery reading will be double than real. It’s not the driver’s fault since I check for the firmware version but SmartThings seems to no longer provide the firmware version information to drivers.

New update. No action is needed since the default behaviour is the same.

──────────────────────────────────────────────────
Driver Id ddc4c655-053a-4a52-b882-6d31e28a1ffa
Name Ikea Button Tweaks
Package Key ikea-button-tweaks
Version 2025-09-21T18:38:32.401834734
───────────────────────────────────────────────────

Automatic battery type fill-in

Actually I’ve had this implemented for months but never released it to the public because SmartThings had a bug when adding that information. They fixed it and has been working fine since. It adds this little arrow to the battery percentage and you can check the battery type and quantity.

Setting for old TRADFRI with new 24.x firmwares

In the rare case you have old TRADFRI remotes with new firmwares (24.x), highly improbable since you had to update them in another platform, I’ve added a new setting to fix the battery reporting. Used to be automatic but SmartThings broke firmware version reporting to drivers as stated in previous comment so now you have to tell the driver manually or it will display double the battery :man_facepalming:.

Small update to the wording of auto-repeat settings. Version 2025-10-03.

Main reason being it always said auto-repeat Hold but the event in SmartThings is called Held and was driving me mad :sweat_smile:.

Somehow I feel this will be the final update, all the custom features that I felt worth adding are already there, it works with current firmware versions of the buttons and next IKEA buttons like the BILRESA will be Matter over Thread which should work out of the box in SmartThings. I know I’ll get them and also know I’ll miss the custom features so… :face_with_hand_over_mouth::shushing_face:

It’s happening, IKEA Zigbee buttons are already discontinued in some countries, sometimes with nice 50% discounts so might be an opportunity to grab some for the last time.

So far the only known Matter successor is the BILRESA which is basically a RODRET/SOMRIG but there’s no word about larger ones like the STYRBAR or SYMFONISK gen2, both quite nice for wall mounting or having lots of actions available.

I can’t comment for the newer buttons but if you have an Ikea hub configured into ST as a matter bridge with buttons/blinds/air quality sensors configured to it they are exposed to ST without issue - may be the same for the newer buttons?

New buttons are Matter over Thread, they don’t need bridges nor custom drivers to work in SmartThings, at least for the basic single / double / long press events.

One of the best things of Matter is that it standardizes button presses. In Zigbee they were not really buttons but dimmers so there was no concept of β€œbutton pressed”. Instead, the driver had to behave like a light and when it received the β€œon” command for instance then map that to a button in SmartThings.

There’s space for custom drivers for buttons though, like custom labels, multitap emulation, auto-repeat Held, exposing events not present in SmartThings like the long press release, etc. To be honest I don’t know if people use those features or not, I certainly do :rofl: .

I’m having an issue where, after using your driver, I cannot do anything – the device does not respond to any and all button presses.

I’ve got a pair of the original 5 button (with the grey outer housing) Tradfri remotes. Using the stock driver ST provides, I was only able to get battery and β€œConnected” status after the original pairing. Switching to your driver (without re-pairing) I was able to see all the buttons at least. Making a routine (When center button is short pressed, turn on Ikea light). I do this and no matter what button I press, while I get a red light on the remote blinking after press, nothing happens. I don’t even see the key press in the ST log for the device.

Is this anything you’ve encountered? I know I have an Ikea hub, but I really want these things in ST and ultimately Home Assistant.

If it didn’t work with stock drivers you can’t just switch the driver.

Now that you’re using my driver you can re-pair it. Put it into pairing mode and scan for devices. That should fix the missing bindings so it receives the button events.

By the way, if the firmware version is less than 24.x it should work with stock drivers too. If it’s 24.x remember to tick the setting so the battery reading is correct.

Remove the device? I’ve tried to put it in pairing mode, and search for nearby devices under add a device - nothing. I’ve tried to put the device in pairing mode and add an Ikea button, and nothing. It’s as if it’s not going into pairing mode at all.

I’m at software version 24040005, so 24.x?

These IKEA buttons can be tricky to pair. Try holding the pairing button while scanning for devices, and keep pressing the buttons occasionally to prevent the device from going to sleep.

And yes, you have to delete the device first in the SmartThings app.