You can achieve color changes using this driver with scene switcher
Thanks, glad it’s useful. Indeed, button drivers expose the button events but they do not directly control devices, they trigger SmartThings routines. The actions you can assign are the ones the device and its driver supports in SmartThings.
For instance, this driver can repeat the long press event automatically while the button is held, but that’s only useful if the driver of your lights supports an action like “increase brightness by 10%” (spoiler: SmartThings stock drivers do not support it).
As for colour switching, Milan already linked to the Virtual Scene Switcher, a driver I made to facilitate cycling through scenes or colours. The very first example is precisely switching four colours with just one button. As long as you change the colours with the switcher it will keep track of the current one so the “Next” and “Previous” action will work as expected.
Thanks @mocelet and @milandjurovic71 for both the suggestion and the actual Virtual Switch. Once I figured out how to set it up, it works a treat and has exactly what I needed and more.
Cheers
Juan
Absolutely amazing, thank you so much for making this!
I’ve been going nuts trying to pair the Styrbar to my ST hub and NOTHING was working until I found this absolute magic you made
No problem, glad it’s working!
Actually Styrbar is becoming my favourite button for walls and I bought more. I also have a Symfonisk Gen 2 on the desk to control all my Matter stuff locally, I was tired of grabbing the phone or asking the voice assistant to “turn on the fan” or “turn on the backlight”. Buttons are amazing.
Firstly, I apologise for any newbie questions. I’ve just tried to install the Styrbar remote and didn’t do my homework… the Tadfri bulbs I installed were easy to add to Smartthings and I was expecting the same for my new purchase. I’ve installed the drivers for both the Strybar and also the Rodret devices etc and then followed the pairing instructions without any luck.
I can’t see what the firmware level of the remote is on the box or on the device itself.
If I do manage to get the Styrbar working, can it co-exist with the control of the bulbs I’ve already installed directly to my Aerotec Hub and associated routines that use the same bulbs?
Press the reset button harder than you might think. While pairing, press one of the buttons every few seconds, because the button tends to fall asleep easily. Took some time when I added my first IKEA button and I thought that it’s probably broken. The next five buttons (STYRBAR and RODRET) were easy.
The manufacturing code is 2419, that’s week 19 of 2024 meaning May 2024.
That’s a problem… they released a new firmware that week IKEA STYRBAR with FW 2.4.11 needs a new quirk · Issue #3135 · zigpy/zha-device-handlers · GitHub , had issues and had to release a update two months later Reddit - Dive into anything
I would recommend you to return it and get one with a 23xx code (mine are 2339 or later but less than 2400).
Still, it should at least pair, but since SmartThings cannot update the firmware you may experience more issues later.
Edit: While we still don’t know the firmware included in this unit, 2.4.11 contained critical bugs. The issues with Home Assistant linked earlier don’t affect this Edge driver since I don’t do that fingerprinting. Actually I believe the driver should work with new versions too, it’s just that this particular unit may have the buggy firmware or be a bad unit.
Edit 2: It turned out to be a 2.4.5 firmware, which is perfectly compatible, but given the issues with 2.4.11 are real and it’s unknown if that one is included in the box, it’s better to avoid them.
Thanks for your rapid response. I pressed harder on the reset button and kept pressing a button every few seconds but no joy. Each time I do get a rapid 2 flashes, almost as if the pairing had worked but I just get a spinning wheel on the ‘searching for devices page’. I’d also cleared out any drivers currently not in use in case any conflict.
I’ll try returning the device for a 23xx firmware version but this was an online purchase so I’m pretty sure that wont happen.
I think I’ll look for another Zigbee remote
Thanks again.
IKEA has this bad habit of making breaking changes in firmwares, after all they don’t support ZigBee integrations in other hubs but their own and theirs update the firmware automatically so they have freedom.
Their official way to support buttons in SmartThings is Matter bridging, but you would require a Dirigera hub for that.
It’s a pity most buttons “compatible with Matter” require a bridge nowadays. There are some Matter over Thread buttons on the way but not released yet.
Edit: I’ve edited the first post with a warning, thanks for reporting the issue @MarkCuk
I am trying to setup a new styrbar using the driver Styrbar Button tweaks
Manufacture code 2345
Firmware 2.4.5
I can see the device correctly, it is reporting battery, no error message but not reporting any button press.
I have a second one that is working fine
Manufacture code 2414
Firmware 1.0024
@mocelet, if you can help.
Did it pair with my driver and get the name “STYRBAR Button”? I would delete it and try again. Check there are no other drivers for styrbar.
That’s strange, the code is recent (year 2024) but the firmware is years old (year 2021/2022), sounds like it came in the wrong box or someone replaced it?
Yes both are using your driver styrbar button tweaks
The one that is working came package with a bulb.
I see, unfortunately I don’t have any advice other than putting it again into pairing mode and scan devices, which is what I do when a button seems to not pair correctly. Maybe a timing thing?
I’ve deleted one of my styrbars and added it again just in case there was an issue with the hub firmware (I’m using 54.10), paired at first time and buttons work. I believe mine was made just few weeks before yours so must be the same.
I used SmartThings several years ago without a hub when Stringify was killed off and it wasn’t a practical replacement so I gave up. Only came back very recently and straight into the post-IDE world. I had hopes that the days of multiple hubs/bridges and lack of brand interconnection would be simpler and much more PnP…. a little naive of me it now seems Early days for Matter and Thread but I wasn’t expecting the bridge requirement for ‘compatible with Matter’ point you make. This is not a moan about ST.
The positive I take from my Styrbar issue is the community knowledge pool and people such as yourself willing to help.
Yeah, Matter is a common language so there are two options, either the device “can speak Matter” or cannot. If it can’t, it needs a translator which is the (usually proprietary) bridge. While that’s great to integrate old devices you already have into Matter, it’s probably slowering the release of actual Matter devices since vendors still want to have their own hub-centric ecosystem.
Back on track, I’ve been looking for the impact of new IKEA firmwares in other ecosystems like Hubitat or Home Assistant. First, we don’t really know if yours has a new one because it doesn’t even pair, maybe SmartThings didn’t even load the driver! Second, I actually believe it should work, or at least pair since the fingerprint is the same. But, at the same time, I’ve read that May 2024 firmware had many bugs so maybe the pairing issue is a firmware bug.
Can you try to pair it again? Sometimes SmartThings takes time to “realize” there’s a new driver installed. Although in that case it would show up as a Zigbee Thing I guess. Weird.
And, even better, if you knew how to use the SmartThings CLI you could send me some logs of the setup, I’m curious if the driver is even being called.
I followed your advice, deleted the device and readded it. I redid the pairing while the device was still listed and it started to work.
Thanks again @mocelet
Great, glad it worked! Sometimes they’re tough to pair correctly, if the bindings are not successful it pairs but buttons won’t generate events.
I deleted the ‘Styrbar Button Tweaks’ driver and anything else Ikea related. I then re-started my Aeotec Smart Hub and tried to pair the unit again without success.
Afraid I don’t know hiow to use the CLI but happy to try it if you want to give me some pointers for the CLI itself and then the specifics for the logs.