that’s the exact case in #18 / #19 you would miss then…
and how to handle the battery vs. switch case #63?
Do you have an example of some entity names that would trip it up?
I might be missing something obvious. What is the purpose of the .* at the end?
My interpretation of the issue, incorrect matches based on entity names: (fictional names)
see my previous comment please (actually to find out what could go wrong is part of the exercise 
)
This blueprint has worked great for me so I really appreciate it. But I do want to mention one weird issue. With my first scroll wheel I noticed no issues. But with my 2nd and 3rd I realized I couldn’t use the scroll wheel to dim the light that I was targeting. But I could make it brighter.
But then I decided to try channel 2 and it worked for both. I also tried channel 3 for both and they worked just fine. So for some reason only channel 1 is affected.
Not a big deal though. Just wanted to point it out.
please see the troubleshooting section in the description, it’s for sure that the entity names don’t comply with what is expected in the blueprint (and no, I don’t have a solution for this)
1 Like
Thanks, I’ll look into it.
Hi,
Recently the hold state returns an error:
Define variables m_1, m_2, m_3, s_1, s_2, s_3, l_1, l_2, l_3, tr_1, tr_2, tr_3, action_kanal_id, event_attr, ticks, action_event_type, curr_mode, base_sens, step_val, transition_ms, transition_s, curr_target_obj, curr_target_list, and curr_target
Executed: August 3, 2026 at 09:19:58
Error: ValueError: Template error: int got invalid input 'None' when rendering template '{{ event_attr.get('totalNumberOfPressesCounted') | default(1) | int }}' but no default was specified
What am I doing wrong and what other information would you need form me to help looking into this?
Excellent blueprint - thanks
you are using a different blueprint … the screenshot and these variable names don’t fit to my blueprint
my would look like this:
Sorry, I didn’t notice this was the wrong thread
Hey. Thanks for making this. Really excited to use the Bilresa for things around the home. I ran into some issues using the scroll bar. I’m not sure if it’s already been addressed, but I (well, a coding agent) had to tune up the regexp’s to match the entity ID suffixes more reliably. WDYT?
Regex bug in trigger_variables — _N.*$ matches too broadly
The 15 regex_findall patterns use _N.*$ (e.g. ^event\..+[a-zA-Z]_1.*$). The .* before $ allows the regex to match _1 anywhere in the entity_id, not just at the end. For example, event.ikea_scroll_wheel_1_button_9 contains _1 inside wheel_1 — so _1.*$ matches all 9 event entities. Every trigger_variable resolves to a concatenated string of entity IDs, and no state_changed event ever matches.
Fix: change _N.*$ → _N$ in all 15 patterns. After the fix each pattern matches exactly one entity (e.g. _1$ → only event.xxx_button_1).
Before:
regex_findall(find='^event\..+[a-zA-Z]_1.*$')
After:
regex_findall(find='^event\..+[a-zA-Z]_1$')