How to properly trigger an automation with Aqara Wall Switch V1 via Matter?

[mensa84]

Hi everyone,

I recently added some Aqara Wall Switch V1 switches to my Home Assistant setup. They are connected locally via the Aqara Hub M3 using Matter.

The devices show up fine, and I can see the button presses perfectly inside the Home Assistant logbook / device activity history (it registers the clicks immediately).

However, I am struggling to find the "best practice" way to use these button presses as a trigger for my automations. Since it is an event entity via Matter, it doesn't have a simple on/off state.

What is the most simple, reliable, and native way to set up a trigger for "Button 2 pressed" in the visual automation editor? Should I use a state trigger, an event trigger, or something else?

Any help or a quick example (UI prefered) would be greatly appreciated!

Thanks in advance!

[ShadowFist]

@mensa84

Should I use a state trigger, an event trigger, or something else?

I think this would be a potential candidate for trying out the new purpose-specific triggers.

These are currently available if you enable them in the Home Assistant Labs section, but should be released in Core with Wednesday's 2026.7 release.

Note that I do not have that switch nor use Matter, so not sure if Matter events are covered by the new triggers. I suggest you enable the feature from Labs or hop on to the current beta & have a play with them.

[mensa84]

Thank you. So it will be out of beta already on Wednesday?

[ShadowFist]

Yep, monthly releases are always on the first Wednesday of the month.

[Didgeridrew]

Voice PE button press event is frustrating

That's only kind-of correct... the state was changed, but a trigger focused on the attribute event_type wouldn't fire, because that attribute didn't change. Instead, use a state-focused State trigger for the event entity, so that the state change fires the trigger. Then add a condition to filter for the press type: triggers: - trigger: state entity_id: event.home_assistant_voice_[...]_button_press not_to: unavailable conditions: - condition: template value_template: "{{ trigg…

HA Docs - Event Integration

@mensa84

... a quick example (UI prefered) ...

Sharing screenshots of the UI isn't "quick"... it's slow, cumbersome, and error-prone. Nearly every exchange requires both you and us to duplicate the effort of making the edits in the UI, taking one or more screenshots, then uploading them. We share YAML because it is editable, fast, complete, and portable... in most cases it can be pasted directly into the UI editor.

For some "advanced" options you may need to use the Automation or Script editor's "Edit in YAML" option... then, once you save it, you can easily switch back to the Visual editor.

[mensa84]

That makes total sense, and I completely agree with you. I honestly expected that a simple wall switch triggering a basic automation would be something I could easily click together entirely within the GUI.

It feels a bit counterintuitive that such a standard real-world task immediately requires diving into YAML or tracking down specific attributes like newPosition just because the device uses Matter under the hood.

I understand why the community prefers sharing YAML here since it avoids all those UI translation quirks, but it’s definitely a bit of a hurdle when you just want to set up a quick, native automation using the visual editor!