Matter: IKEA BILRESA Dual Button exposes no device triggers, only a generic event entity

[MstrDC]

The problem

The IKEA BILRESA Dual Button (productId 0x8001 / 32769) paired via Matter over Thread
does not expose any device triggers in Home Assistant.

Instead, the device creates a generic event.* entity:

event.bilresa_dual_button_knop_1

This entity changes its state (timestamp string), while the actual button press
type appears only inside the attributes. Example:

event_types:
  - multi_press_1
  - multi_press_2
  - long_press
  - long_release
event_type: multi_press_1

Home Assistant is therefore unable to show standard device triggers like:

• “Button 1 pressed”
• “Button 1 double pressed”
• “Button 1 long pressed”
• “Button 2 pressed”
• etc.

This behavior is inconsistent with how other Matter remotes/buttons work in Home Assistant,
which correctly expose device triggers using the Switch/Scenes/Actions clusters.

Expected behavior

• Home Assistant should expose the BILRESA Dual Button as a Matter button device.
• Button interactions (single press, multi-press, long press, long release) should appear as
  device triggers in the Automation UI.
• The device should not require a fallback event. entity.

What actually happens

• HA creates a generic entity: event.bilresa_dual_button_knop_1
• Button presses update the entity state (timestamp string)
• Press type is only reflected in attributes.event_type
• No device triggers appear in the UI
• Automations must use state-based matching on an opaque event entity

Event example

event_type: state_changed
data:
  entity_id: event.bilresa_dual_button_knop_1
  new_state.attributes.event_type: multi_press_1
  new_state.attributes.event_types:
    - multi_press_1
    - multi_press_2
    - long_press
    - long_release

Device info (from UI)

• Name: IKEA BILRESA Dual Button
• Product ID: 32769
• Firmware: 1.8.5
• Hardware: P2.0
• Network: Matter over Thread (sleepy end device)
• Integration: Matter (native HA integration)

Home Assistant version

2025.12 (HA OS)

Matter Server version

8.1.0

Additional information

This appears to be a mapping gap in Home Assistant’s Matter integration:
HA detects the button as a generic Matter device and falls back to creating an event entity,
instead of creating proper triggers.

Other Matter remotes using Switch / Scenes / Actions clusters do expose their triggers
properly.

If additional diagnostics or cluster info is needed, I can provide full Matter dumps.

What version of Home Assistant Core has the issue?

core-2025.12.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

event_type: state_changed
data:
  entity_id: event.bilresa_dual_button_knop_2
  old_state:
    entity_id: event.bilresa_dual_button_knop_2
    state: "2025-12-12T11:47:44.073+00:00"
    attributes:
      event_types:
        - multi_press_1
        - multi_press_2
        - long_press
        - long_release
      event_type: multi_press_1
      previousPosition: 1
      totalNumberOfPressesCounted: 1
      device_class: button
      friendly_name: "Off"
    last_changed: "2025-12-12T11:47:44.073741+00:00"
    last_reported: "2025-12-12T11:47:44.073741+00:00"
    last_updated: "2025-12-12T11:47:44.073741+00:00"
    context:
      id: 01KC966TT963QZHFDCDWVNRZ6Q
      parent_id: null
      user_id: null
  new_state:
    entity_id: event.bilresa_dual_button_knop_2
    state: "2025-12-12T12:11:54.214+00:00"
    attributes:
      event_types:
        - multi_press_1
        - multi_press_2
        - long_press
        - long_release
      event_type: multi_press_1
      previousPosition: 1
      totalNumberOfPressesCounted: 1
      device_class: button
      friendly_name: "Off"
    last_changed: "2025-12-12T12:11:54.214235+00:00"
    last_reported: "2025-12-12T12:11:54.214235+00:00"
    last_updated: "2025-12-12T12:11:54.214235+00:00"
    context:
      id: 01KC97K2Z60QDMCEN6TWSW2Z93
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2025-12-12T12:11:54.214235+00:00"
context:
  id: 01KC97K2Z60QDMCEN6TWSW2Z93
  parent_id: null
  user_id: null

Anything in the logs that might be useful for us?

Additional information

No response

[rvrignaud]

I have the same problem with the BILRESA scroll wheel device (same Matter over Thread). It doesn't expose neither click button nor wheel scroll as a trigger.
In that case as well, using the wheel and button is only reflected as an event

[MikeKMiller]

Same here with a couple Dual Buttons

[home-assistant]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign matter Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

matter documentation
matter source
_{^{(message by IssueLinks)}}

[markdinh]

Thanks for filing this. I'm triggering my automation, for now, through an event trigger but it's very clunky (you have to filter out the unknown and unavailable event activities) and I don't distinguish btw single, double or long press but it works for now. Hopefully this gets addressed in HA soon :-). No issues in Apple Home or Ikea with trigger on presses...

Update: This blueprint does work for "generic matter" 2 button: https://community.home-assistant.io/t/lifx-matter-switch-button-automations/928611 but does through this error in the trace: Error in describing trigger: Cannot read properties of undefined (reading 'includes')

[MartinHjelmare]

Note that device triggers are in maintenance mode in Home Assistant.

We're aiming at adding purpose-specific triggers and conditions for event entities which will make it easier to consume their features.

I'll close here since you should only file an issue if you found a bug. Feature and enhancement requests should be created in the Feature Requests discussion board. Thanks!

[MikeKMiller]

I might be mistaken but this certainly seems like a bug. i.e.. a buttun that is not functioning as a button

[vef445]

@MartinHjelmare it's ambiguous to recognize as a feature request the fact that a standard Matter device (button) isn't recognized/interpreted as such by HA.

[MartinHjelmare]

I'm confused when you say it isn't recognized as a button in Home Assistant. In Home Assistant we use event entities to represent buttons.

https://developers.home-assistant.io/docs/core/entity/event

[MstrDC]

Well, yes, you see entity button 1 (named "On") and button 2 (named "Off"), but you cant select their actions/events (multi_press_1, multi_press_2, long_press, long_release) in an automation.

[MartinHjelmare]

Yes, we are aware of this. Again, device triggers are in maintenence mode and won't be extended. We are replacing them with purpose-specific triggers and conditions.

You can read more about that ongoing project here:
https://www.home-assistant.io/blog/2025/12/03/release-202512/#purpose-specific-triggers-and-conditions

[MikeKMiller]

Yes, we are aware of this. Again, device triggers are in maintenence mode and won't be extended. We are replacing them with purpose-specific triggers and conditions.

You can read more about that ongoing project here: https://www.home-assistant.io/blog/2025/12/03/release-202512/#purpose-specific-triggers-and-conditions

I have that 'feature' on, and this button is not recognized as a 'button' with any triggers or conditions.

[MartinHjelmare]

We haven't added a trigger for event entities yet. As I wrote above, we're planning to do this and the purpose-specific triggers and conditions is an ongoing project.

I'll lock this thread now, since I'm mostly repeating myself.