ok, so most likely there isn’t more information sent over Zigbee.
That’s sadly a little bit limitating, as you get an value update on each rotation “click” as long as you’re within the the limits.
But if you’re at the end of the value scala, you will only get a repeated end-value ever second or so (regardless how fast you rotate the wheel).
So even if you use some tricky logic to detect rotations after hitting the end of the value range, it will feel different to the user.
As long as you’re ok to map your end device directly to the selected value that might be fine.
But I wanted to use it for music volume.
If someone lowers the volume to let’s say 10% using the mobile phone and later turns louder on the the ikea device that was set to 70% the last time it was used:
Might be shocking to go from 10% to something around 80% in a single click. ![]()
So I might have to use the trick described above, which will lead to very fast volume chances while the device is within the value range, but very slow changes ones you reached the end (which the end user isn’t aware of, as he won’t see this value anywhere).
Not sure if this also happens on Matter, or if this is caused by the not-so-polished (as not advertised) Zigbee implementation.