I believe I was able to reproduce what you described. It took a couple of hours with Codex. I found the thread on the forum regarding how to create rules, but when I tried to implement the toggle rule in the app, the lights went crazy, flashing on and off while I changed the brightness.
The responsiveness is currently far from what I experience with old devices and Zigbee groups. I’m not sure if this is a hardware or software issue, so I’m going to try switching the dimmer to Zigbee mode to see if that improves the performance.
@veonua Not sure what scenario you’re working with or what lights or drivers are you using, this video I linked a couple comments before is how the scroll to control brightness works with a Matter light using that JSON rule.
There should be no flashing on/off while changing the brightness, what you can expect is half a second latency which is the reporting interval of the scroll. The brightness change is proportional to the scroll, with a full scroll meaning 100% brightness change.
Since you were also using the Swipe Left and Swipe Right events, make sure you don’t have BOTH automations enabled. If you use the JSON rule don’t use the Swipe events and viceversa, otherwise they are fighting each other and could explain your weird behaviour.
I would start over, it sounds like there are many automations running due to testing or even, if you use AI (why?) there might be potential hallucinations.
On a side note, sometimes when changing the driver of the buttons, either to this driver or back to stock, I’ve seen a “Can’t connect to the device. Check device and try again”. The device is fine and automations keep working, it’s just the app: if you close the app and open it again it loads fine. Must be something related to the different profiles or capabilities.
The dual button does not support triple press natively, only double press.
The driver implements a hack to give you a triple press option but you have to enable it in the settings and, as explained in the first post, it’s not 100% reliable given the button does not actually report the third press.
Is there a way to use the scroll wheel to control a group of Ikea Fyrtur blinds using @veonua Ikea Window 1.1 driver. I have created a @TapioX Virtual Dimmer device, and I can control the dimmer level using the scroll wheel. But the Smart lighting Sync with switch doesn’t control the blinds. Any suggestions how to get this to work?
If the blind uses the windowShadeLevel capability I guess you can use a Rule in the advanced website to sync the virtual dimmer with the blind shadeLevel. Although won’t be an actual sync, if you change the shade level by other means the virtual dimmer won’t have the correct value.
Maybe you can ask the driver developer to add a relative step function or, better yet, implement the new statelessSwitchLevelStep capability.
Just a quick follow up to my post. A big Thank You to @veonua for adding the StatelesSwitchLevelStep capability to his driver. The Ikea Blinds driver now supports the new capability and works with the Bilresa scroll wheel.
Finally, with the most recent app update, Rules API are no longer needed in many cases to enjoy the advanced dimming with BILRESA scroll, now it’s piece of cake to set it up with the Control devices by options!
Check if you can create the automation with the app and, if so, just delete or disable the rules and the Swipe left / right actions since they’re no longer needed for dimming.
Stock drivers only support control by rotating, Matter Playground also supports pressing and rotating. You can also change the rotation sensitivity in settings (Level step per notch).
Also remember in bulbs using Matter Playground you can change the transition time for the dimming steps, by default is 0 seconds since that works better in some bulbs (WiZ), in Nanoleaf 0.1 seconds is better and for KAJPLATS 0.3 seconds looks good. Stock driver uses 0.3 and cannot be changed.
If your lights are not elegible for the nice user interface you’ll have to set the Rules like in the comment about dimming or go for the basic Swipe Left and Swipe Right actions.
The wheel is so slippery that sometimes you cannot even rotate the wheel on purpose! That’s definitely not an issue.
The issue is the hardware defects, some units will not register correctly the double click or the triple click (you hear the clicks but the physical switch did not make contact).
I just learned to forget about the double/triple click in the scroll wheel, also because I use the short release event which has less latency to toggle lights than the standard single press. So I’m fine with press to toggle, scroll for brightness, press+scroll for colour temperature and toggled up (long press release) for a secondary action.
I would miss the two I have if I didn’t have them since the scroll is sometimes quite handy but I’m lowkey waiting for something with an actual knob and a couple buttons more instead of a rotating surface. In fact I don’t even use the multi-group feature now because I prefer not having to look which one is the active group.
I mean, it’s reliable when you find a good use case for it, didn’t want to bash them . Adjusting the brightness and temperature with the scroll is enjoyable, sometimes I even change the brightness just for fun like if it was a fidget toy
But yeah, there’s a bit of everything in the motivation. I do have a good background in research and development that makes things easier plus the technical curiosity for how things work and how to make them better, especially if they are new like Matter.
So I’m using yours and switched to stock to see if I see a difference. Perhaps one day the wheel will work as intended. It’s legit all over the place and not reliable for dimming no matter what driver used.
Just curious, in what sense is not reliable for dimming? It has latency because of the way it reports the rotation (it waits around half a second) and if you have many lights you’ll have the typical popcorn effect, but if you scroll, let’s say, 30% of the wheel, the brightness changes a 30% which is the intended.
The dimming part of the device in stock and my driver work the same, the device tells you how much you rotated and that’s passed to the light as a brightness percent step.
That was a little hack to reuse a custom capability to control the brightness proportionally to the scroll before SmartThings added support for rotary knobs. The preferred way now, also compatible with stock drivers, is the “Control devices by rotating” action in the app or, if you use Rules API, the knob capability.
I have mixed feelings about the native handler since they hardcoded the transition time to 0.3 seconds and that’s fine for some knobs and some lights but not for others. I’ll have to check how it behaves.
It won’t be smoother though, only will have less popcorn effect when controlling multiple lights. The main source of latency in the scroll wheel comes from the 500 ms the scroll waits to report the rotation.
Edit: Wrote a comment in the PR and got a response, the transition time for the step will be configurable eventually
.
That’s definitely not an issue.
. Adjusting the brightness and temperature with the scroll is enjoyable, sometimes I even change the brightness just for fun like if it was a fidget toy 
By this time nobody should be using these but just letting you know I’m going to remove the deprecated options in the next update.
