@bogus good idea as well!
To make your approach work (as hint for other users):
- you have to go to Bilresa device settings and enable the 9 hidden sensor entities
- in German HA the sensors are named like:
sensor.*_aktuelle_schalterstellung_1, so your regex in the blueprint won’t find the scroll entities (see also the discussion about second device with same name above)
Background info:
Current Matter implementation seems to expose two different kind of entities for the scroll wheel: event (left/right), sensor (left/right).
- the
eventis fired after a scroll action with information of “how far” you scrolled (a number between 1 and 8), this is what I use in my blueprint - the
sensorchanges while scrolling between 0 and 1, this is what @bogus blueprint uses
It depends a little bit on the use case. If you have to control actions which have low latency the sensor approach will feel snappier, while for actions with larger latency the event approach (which accumulates sensor changes actually) might be more suitable. Best would be to make the behavior configurable, though I am not sure if this can be easily done.