I’m using the blueprint “IKEA Bilresa – Unified 3-Layer Controller” as it was the first I found in English. I’m having issues with the automation triggering randomly and turning on the lights in the middle of the night. It seems the remote reconnects and sends the events below, which trigger the automation. Is this handled better in a different blueprint?
Thanks for any help.
give it a try
@rnsalinero , @tyxcho an update is available letting you choose to use volume step percentage for instant mode as well
Thank you very much!!!
I hava paired the device bilresa via zigbee (zigbee2mqtt) (8 clicks on the reset) I did not get this blueprint to work though. Any tips?
This blueprint is developed for Matter/Thread binding only.
(Technically you could check the trigger section of the blueprint and check which events and data are fired for z2mqtt binding and try to adapt accordingly. To see which event(s) are actually fired for which button action you can use the HA developer tools and capture the information. As I use Matter here I have no idea if it is easy or not and cannot give further advice.)
As I understand, we have to wait the next version of z2m because the scrollweel is not well implemented yet.
Just in case anyone else comes across the same issue I did: If the media volume down is working fine, but media volume up is not working on Channel 1, check your remote name does not end in “1”, e.g. “Remote 1”. Changing the name of the remote to “Remote one” resulted in the volume changes working fine both ways.
This is amazing! I thought the scroll wheel was doomed until Matter had better support for scrolling, and IKEA exposed the groups in a better way.
Mind blown!! Thank you!!
Thanks for the amazing blueprint!
I was wondering, when scrolling fast in instant mode, it seems to take a lot of scrolls to reduce the brightness to minimum. However, when going slowly, it will correctly reduce it by X% each notch. Is there a way to change this, or is it by design?
Thanks!
I guess it’s related to Ikea Bilresa scroll wheel blueprint - #38 by devzor
Not sure if this can be improved somehow with the current approach.
Hi guys. great job, but the wheel is still not working right? I am trying it both with yamaha media.player volume controlling and aqara t2 dimming but both times it fails with the wheel. Any chance someone had defined user action to handle it better?
about scroll speed, I tested with user defined scroll wheel action
action: system_log.write
metadata: {}
data:
level: error
message: >-
{{ 'queue:' ~ this.attributes.current ~ ' / scroll clicks:' ~ scroll_clicks
~ ' ' ~ scroll_direction }}
and looked into the logs:
2026-01-17 20:11:42.735 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:43.241 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:43.735 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:44.400 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:44.898 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:45.398 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:45.900 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:47.004 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:47.498 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:48.004 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 right
2026-01-17 20:11:53.862 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:54.350 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:54.847 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:55.346 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:56.398 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:56.909 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:57.980 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:58.494 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:11:58.985 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:12:00.034 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
2026-01-17 20:12:00.524 ERROR (MainThread) [homeassistant.components.system_log.external] queue:0 / scroll clicks:1 left
I was not able to get more than about 2 clicks per second 
, so the scroll speed is limited to that for now
I have a very strange behavior with this script.
Only the relax mode works and
Everything works then when the remote goes in sleep mode , it is not detectable.
If i set up the Ikea app in same time on another layer , the Ikea side works perfectly
But the home assistant side it stop detecting after a while.
Then it can randomly reconenect when Ikea app still see it and see actions without issues.
Home assistant works as well since other opjects connected still works strangely.
Edit: blueprint is not compatible with the dirigera i see, sad.
Hi everyone, I am sure that this is a really simple question. I have the blueprint working and it is controlling a set of lights, but how do I change the channel of the wheel? The wheel has the first led on which I assume means it is in channel 1. Thanks
It’s relatively simple. Just press the spot where the three LEDs are located. The first LED should light up when you press it for the first time, and then you can switch between the LEDs and thus also the channel with each subsequent press. For me, the button sometimes doesn’t respond to the first press and the LED doesn’t light up. I then press it repeatedly until the LED lights up. I don’t know what causes this yet, but it may happen to others as well.
Does anyone have a solution for the volume control on my Amazon Echo?
I currently have the volume control set to Instant Mode, which works with Stepup. Unfortunately, the Echo only jumps in 10% increments, which is too much for the button to respond to.
For some reason my bilresa won’t show up when I try to select a device. Anyone that knows of a fix?
Did you pair your device with Matter over Thread?
What do you see in the device dialog, should be similar to
