IKEA Bilresa Scrollwheel (Matter) – Ultimate Light Controller (Atomic Edition)

Blueprints Exchange
,
1

This blueprint is designed to unlock the full potential of the IKEA Bilresa Smart Scroll Wheel when used via Matter/Thread to control your Smart Lights.

(Note: This blueprint is optimized for Lights only. It does not support Media Player/Volume control in this version.)

Many users experience lag or “jumpy” behavior when using this device via Matter. This blueprint solves that by using a custom Hybrid Engine dedicated to smooth lighting adjustments.

:rocket: Key Features

  • :zap: Hybrid Engine:
    • Scrolling uses Sensors directly for butter-smooth Dimming, Color Temperature, or RGB changes.
    • Buttons use Events for reliable switching.
  • :atom_symbol: Atomic Control:
    • Total freedom! You don’t just assign a mode to the whole remote.
    • You can configure each of the 3 Scroll Zones independently (Brightness, Kelvin, RGB, or Presets).
    • You can configure each of the 3 Buttons independently, with separate actions for Double Click and Hold (e.g. set specific Colors or Warm/Cold white).
  • :rainbow: RGB & Kelvin Support: Full support for color changing (Rainbow scroll) and temperature control.

:clipboard: Requirements (Crucial!)

Because this device exposes many entities via Matter, you must enable/disable specific ones in Home Assistant for this blueprint to work correctly.

  1. ENABLE these Sensors:
  • Look for entities ending in (1), (2) (Zone 1)
  • Look for entities ending in (4), (5) (Zone 2)
  • Look for entities ending in (7), (8) (Zone 3)
  1. ENABLE these Events:
  • Look for event entities ending in (3), (6), and (9).
  1. DISABLE these Sensors:
  • Sensors ending in (3), (6), and (9) are not needed and should be disabled to reduce Thread network traffic.

:bulb: Setup Tip regarding Lights

If you want to control multiple lights at once (e.g., a chandelier or a room), please create a Helper Group (Light Group) in Home Assistant and select that group in the blueprint. Targeting multiple individual entities directly via the blueprint may cause synchronization issues (“Popcorn effect”).

:inbox_tray: Import Blueprint

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint URL pre-filled.

Or import manually using this URL: IKEA Bilresa Scrollwheel (Matter) - Ultimate Hybrid Controller Blueprint (V1.0 Atomic Edition) · GitHub

:gear: Mapping Guide (How to find your entities)

When configuring the blueprint, look at the number in parentheses at the end of your entity names:

  • Scroll Zone 1: Select sensors ending in (1) and (2).
  • Scroll Zone 2: Select sensors ending in (4) and (5).
  • Scroll Zone 3: Select sensors ending in (7) and (8).
  • Button 1 (Left/Top): Select the event ending in (3).
  • Button 2 (Middle): Select the event ending in (6).
  • Button 3 (Right/Bottom): Select the event ending in (9).

Version History

  • V1.0: Initial Release (Atomic Edition). Dedicated Light Control with optimized direction detection.

🇩🇪 Klicke hier für die Deutsche Beschreibung

Deutsche Beschreibung

Dieser Blueprint holt das Maximum aus dem IKEA Bilresa Smart Scrollrad heraus, wenn es über Matter/Thread genutzt wird, um deine Beleuchtung zu steuern.

(Hinweis: Dieser Blueprint ist rein auf Lichtsteuerung optimiert. Er unterstützt in dieser Version keine Media Player / Lautstärke.)

Viele Nutzer haben bei diesem Gerät über Matter mit Verzögerungen oder “ruckeligem” Verhalten zu kämpfen. Dieser Blueprint löst das Problem mit einer speziellen Hybrid Engine.

:rocket: Die Highlights

  • :zap: Hybrid Engine:
    • Scrollen: Nutzt direkt die Sensoren. Das garantiert butterweiches Dimmen oder Farbwechsel ohne Netzwerk-Lag.
    • Tasten: Nutzen Events. Das garantiert, dass jeder Klick (Einzel, Doppel, Halten) zuverlässig erkannt wird.
  • :atom_symbol: Atomic Control (Totale Freiheit):
    • Du legst nicht einen Modus für die ganze Fernbedienung fest.
    • Du kannst jeden der 3 Scroll-Bereiche einzeln belegen (Helligkeit, Kelvin, RGB oder Presets).
    • Du kannst jede der 3 Tasten einzeln konfigurieren, mit eigenen Aktionen für Doppelklick und Halten.
  • :rainbow: RGB & Kelvin: Volle Unterstützung für Farbwechsel (Regenbogen-Scrollen) und Farbtemperatur.

:clipboard: Voraussetzungen (Wichtig!)

Da das Gerät über Matter extrem viele Entitäten bereitstellt, musst du in Home Assistant die richtigen aktivieren bzw. deaktivieren, damit der Blueprint funktioniert:

  1. AKTIVIEREN (Sensoren):
    • Sensoren mit Endung (1), (2) (Zone 1)
    • Sensoren mit Endung (4), (5) (Zone 2)
    • Sensoren mit Endung (7), (8) (Zone 3)
  2. AKTIVIEREN (Events):
    • Event-Entitäten mit Endung (3), (6) und (9).
  3. DEAKTIVIEREN (Sensoren):
    • Die Sensoren mit Endung (3), (6) und (9) werden nicht benötigt und sollten deaktiviert bleiben, um das Thread-Netzwerk zu schonen.

:bulb: Wichtiger Tipp für Lampen

Wenn du mehrere Lampen gleichzeitig steuern willst (z.B. eine Gruppe im Wohnzimmer), erstelle bitte unbedingt eine Helfer-Gruppe (Light Group) in Home Assistant und wähle diese im Blueprint aus.
Wenn du im Blueprint mehrere einzelne Lampen direkt anwählst, kann es zu Synchronisationsfehlern (“Popcorn-Effekt”) kommen.

:gear: Zuordnungshilfe (Mapping Guide)

Achte bei der Auswahl im Blueprint auf die Zahl in der Klammer am Ende des Entitäts-Namens:

  • Scroll Zone 1: Sensoren (1) und (2).
  • Scroll Zone 2: Sensoren (4) und (5).
  • Scroll Zone 3: Sensoren (7) und (8).
  • Taste 1 (Links/Oben): Event (3).
  • Taste 2 (Mitte): Event (6).
  • Taste 3 (Rechts/Unten): Event (9).
4 Likes
2

Bilresa_Scrollrad
Bilresa_Scrollrad1920×2805 170 KB

3

Hi @stone13,
I have just created this account to comment on your blueprint! I feels pretty solid, setup was pretty easy for a HA starter like me. Sadly, I am getting double triggers for dimming and color temperature. (e.g. 5% steps will not be 5% → 10% but 5% → 10% → 15%). For dimming I can easily reduce the percentage per step, but 200K instead of 100k is unacceptable according to my wife :wink:

Am I doing something wrong in my setup?

Lennart

4

Welcome Lennart, and thank you so much for the feedback!

You were absolutely right—this is a classic “switch bouncing” issue where the hardware sends two events very quickly. I have just updated the Blueprint to Version 1.0.1 to fix this.

The Fix: I changed the automation mode to single and added a small debounce delay (150ms) at the end of the actions. This forces the automation to ignore the second “ghost” trigger that was causing the double jumps.

Please try re-importing the blueprint and let me know if the dimming is smooth for you now!

5

Wow, thanks for the quick reply, works like a charm. I have just further reduced the 100K steps to 50 in yaml, now both parts of our household are happy :wink:

6

Well, it’s important that everyone is satisfied. :wink:
Have a nice day!

7

Thanks for the nice blueprint :slight_smile:

Can you explain what this exactly means. I am in the scroll wheel settings page and there is events, configuration, diagnostic…
How do i enable the sensors? Do I need to set something in diagnostics?

image
image1412×2086 312 KB

I am not sure what to do, I can see that there are events coming in, but there is the problem that my RGB light seems to dim down but never gets brighter again, but stays very dim. Maybe you can give a more clear instruction on how to do the three settings.

8

Under Events you will find the entities like event.xxx_1 and under Diagnostics you have to open the hidden entities section. Here you should enable the entities named like sensor.xxx_1 etc.

9

Hi jihol-byte, thanks for the hint, so if I understand correctly:

  1. ENABLE these Sensors:
  • Look for entities ending in (1), (2) (Zone 1)
  • Look for entities ending in (4), (5) (Zone 2)
  • Look for entities ending in (7), (8) (Zone 3)

I need to open the hidden “Diagnostic” section and click on the items 1,2,4,5,7,8 and then choose “activate” each time?

for

  1. ENABLE these Events:
  • Look for event entities ending in (3), (6), and (9).

I don’t need to do anything because they are enable by default?

and for

  1. DISABLE these Sensors:
  • Sensors ending in (3), (6), and (9) are not needed and should be
    disabled to reduce Thread network traffic.

I also don’t need to do anything in “Diagnostics” because they are disabled by default?

Maybe I am just not getting it, or do I need to make these settings somewhere else where the names in the description do fit? :slight_smile:

10

yes, exactly

11

Thank you very much — that’s great!

Just one question: could you add either:

  • a “no action” option for sensor capabilities, or
  • support for 2 more lamps?

I need to control 2 rooms, so I’d like to use 2 channels for that. I think adding support for multiple lamps (one per channel) would be a great idea and would make the blueprint more flexible.

Thanks again!

12

Is it just me or is this just as laggy as other bilresa blueprints? Is it just matter that is this laggy and slow compared to zigbee?

1 Like
13

The protocol has nothing to do, it’s the way the device reports the scrolling.

The device reports the first notch you scroll almost instantly, but then it waits around 500 ms, half a second, before reporting more notches scrolled to avoid flooding the network, allow time for the smooth transitions to finish, etc.

Unless you scroll just one notch for a very slight adjustment, you have a response time of at least half a second, plus the transition time of the light if you want it smooth. That’s why the scroll is perceived as laggy.

The lag that can be improved but it’s not possible in Home Assistant yet is the on/off toggling by pressing the button. Home Assistant does not expose the initial_press or short_release events to blueprints so they cannot use it to toggle the light fast (when using multi_press_1 it waits for a potential double press).

Edit: Lag vs Scrolling speed

It’s worth remarking this comment was about the lag: you scroll and you don’t see the changes until 500+ milliseconds later. That’s unavoidable unless IKEA reduces the timings.

How fast you can scroll the wheel is another story. Right now the hidden sensors tell you each 500 ms that you’re still scrolling, but you don’t know how many notches have been scrolled to change the brightness proportionally. That’s why in current blueprints, for the same amount scrolled, if you go slow it changes the brightness more than if you go fast. The multipress_ongoing events will fix that when they are available in HA. They are also separated 500 ms though: you’ll be able to get the expected result regardless of the scrolling speed but the lag will not improve.

2 Likes
14

Have you tested these on ikea? I could swear I didn’t notice a 500ms delay in the demo setup there. I was really dissapointed when I got home and realized how useless they are in my HA setup :frowning:

15

If you mean the remotes with lights at stores, they probably have the BILRESA directly bound to the light without hub, using Zigbee Touchlink. DIRIGERA running its automation with Matter events is also laggy.

The way the device works in Zigbee and Matter is quite different, even in behaviour. In Zigbee it controls the absolute brightness and a small scroll means a low brightness instead of a small change. I guess the time between commands is lower too.

16

Yeah that could be. So then it boils down to Matter beeing the issue?

17

The issue is not Matter but the reporting interval they chose when integrated via Matter. Matter does not impose those 500 ms, they could have gone for 100 ms or 200 ms or a different strategy to report the notches so it feels more instant.