Is your feature request related to a problem? Please describe.
When migrating devices from Zigbee to Matter over Thread (specifically IKEA devices like SOMRIG to BILRESA), action formats change from Zigbee2MQTT payloads to Home Assistant event states.
Describe the solution you'd like
A generic event handler that can process standard Home Assistant event entities and their state triggers.
For example, with Zigbee2MQTT vs Matter events:
Old (Zigbee2MQTT):
Device info SOMRIG shortcut button (E2213) by IKEA
Connected via [Zigbee2MQTT Bridge Firmware: 1.0.21
event.bathroom_remote_action -> 2_short_release
*New (Matter):
Device info BILRESA dual button (32769) by IKEA of Sweden
Firmware: 1.9.15 Hardware: P2.0
event.bilresa_dual_button_taste_1 -> Pressed once
event.bilresa_dual_button_taste_2-> Pressed twice
Additional context
I fully understand that implementing a generic handler might require significant underlying architectural changes. This is mainly intended as an idea/feature request to keep managing all switches and buttons conveniently in one central place.
Is your feature request related to a problem? Please describe.
When migrating devices from Zigbee to Matter over Thread (specifically IKEA devices like SOMRIG to BILRESA), action formats change from Zigbee2MQTT payloads to Home Assistant event states.
Describe the solution you'd like
A generic event handler that can process standard Home Assistant
evententities and their state triggers.For example, with Zigbee2MQTT vs Matter events:
Old (Zigbee2MQTT):
event.bathroom_remote_action->2_short_release*New (Matter):
event.bilresa_dual_button_taste_1->Pressed onceevent.bilresa_dual_button_taste_2->Pressed twiceAdditional context
I fully understand that implementing a generic handler might require significant underlying architectural changes. This is mainly intended as an idea/feature request to keep managing all switches and buttons conveniently in one central place.